Skip to content

What's New 🚀🚀


Next-release

2026-11-13

ASPM

Boostignore

  • Ignored Files Are No Longer Downloaded

    Boostignore is now applied before the repository is checked out: the files it matches are never downloaded to the runner that performs the scan. The set of scanned files is unchanged, but scans download less and use less disk space, often far less on pull request scans and on sub-repository scans. Ignoring large generated or binary directories now also lightens every scan of the repository. This applies to every scan run by the Boost Security scanner, through Zero Touch Provisioning (ZTP) or in your own pipeline. A pipeline pinned to an older version of the scanner gets it once you update the pin.

Monorepository Management

  • Root-Only Boostignore and ZTP-Only Exclusion of Sub-repository Paths

    Sub-repository scans apply the .boostignore and .boostinclude files at the repository root, or the Global Boostignore when the repository has none; a .boostignore file in the directory of a sub-repository isn't read. The exclusion of sub-repository paths from the parent repository's scans applies to ZTP scans: a scan you run with the Boost Security scanner in your own pipeline, or one run by a ZTP pipeline from an older template, still covers the whole repository until you select Update Template.

Findings

  • Violation Date in the API and the CSV Export

    Every finding group that is a violation now carries the date and time at which it most recently became one, so you can measure how long violations stay open for your own SLA reporting. It's available as the violationSince field and filter of the finding groups GraphQL API, see Filtering Finding Groups by Violation Date, and as a new violation_since column at the end of the Findings CSV export, after the Jira ticket columns. The dashboard doesn't show it.

    Violations that already existed before this release have no violation date until their asset is scanned again or their policy is re-evaluated. They then get the time of that evaluation.

Fix with AI Through an LLM Gateway

  • Route the Boost Advisor's LLM Calls Through Your Own Gateway

    The Boost advisor that runs Fix with AI can now call the LLM through your own OpenAI-compatible gateway instead of calling the provider directly. The gateway can require OAuth2 client credentials, an API key sent in a header of your choice, or both. You set it up with a few BOOST_LLM_* secrets or variables in the pipeline that already runs the advisor, on GitHub, GitLab, Bitbucket, Azure DevOps and Harness, with no change in the dashboard. On GitHub and Azure DevOps, update the Run boost-advisor step from the template so it maps the new variables. Advisor pipelines that set none of the new variables keep calling the LLM provider directly with BOOST_LLM_KEY.

Manual Tags

  • Find Assets with No Manual Tag

    On Asset Management, the Manual Tags filter has a new No Tags option, next to Match any and Match all. It lists only the assets that carry no manual tag, so you can check that every asset is tagged, then select the untagged ones and tag them with Actions → Assign Manual Tags. Archived assets with no manual tag count as untagged. No Tags is available on Asset Management only. For direct API users, the AssetManagementFilter input of the asset inventory GraphQL API has a new withoutAssetTags field. Set it to true to get only the assets with no manual tag. It can't be combined with assetTagId or assetTagIds.

Endpoint Protection

AI Tools

  • See the AI Tools on Your Developers' Endpoints

    The new AI Tools page, under Endpoint Protection, lists the AI coding agents and chat apps found on developer endpoints, such as Claude Code, Codex, Cursor, ChatGPT Desktop and Claude Desktop. For each AI tool, it shows the LLM providers and models it uses, its MCP servers and skills, and the developers and devices it runs on. Search, filter and pivot the list by AI tool, provider or model, and open a developer to see every AI tool on their device.

2026-10-30

ASPM

SCA Reachability

  • Reachability Verdicts on Boost Security SCA Findings

    The Boost Security SCA scanner can now determine whether the vulnerable code of each CVE it reports is reached from your code. The verdict, Reachable, Unreachable or Unknown, appears in the Vulnerable Code Reached field of the finding details, and works with the existing Vulnerable Code Reached findings filter and policy action. Jira tickets created from a finding state Reachable: Yes or Reachable: No.

    Reachability analysis is opt-in: every Boost Security SCA scanner, new or existing, keeps scanning exactly as before until you turn it on with the Vulnerability Reachability Analysis setting of the provisioning wizard, or with BOOST_SCA_REACHABILITY=true in pipelines you maintain yourself. Once enabled, it runs on default branch scans only, never on pull requests, and adds roughly one second per CVE to the scan.

    Boost Security SCA now requires Boost CLI 1.0.193 or later, whether or not reachability analysis is enabled. Pipelines pinned to 1.0.192 or earlier must upgrade; pipelines on the major version channel (BOOST_CLI_VERSION=1) are already compatible.

Integrating with Code-To-Cloud Context Providers

  • Upwind Integration Available to All Accounts

    The Upwind integration is now available to every account, from the CSPM category of the Integrations page. Connect it with an Upwind API client to bring your Kubernetes clusters, the container images they run, and the services exposed to the public internet into Boost Security. See Integrating Upwind to Boost Security for the setup and what is discovered.

Bitbucket Integration

  • Connect Bitbucket With an Atlassian API Token

    The Bitbucket integration now connects with an Atlassian API token instead of a Bitbucket workspace app, so you no longer need development mode or development apps on your workspace. Create the token with Create API token with scopes for the Bitbucket app, then enter your Atlassian email and the token in the New Bitbucket Integration dialog. When the token expires, replace it with Update Personal Access Token.

    Zero Touch Provisioning for Bitbucket now runs through a three-step wizard. On its last step, you approve the BoostSecurity CI Provisioning Atlassian app, and nothing is installed from the Bitbucket Marketplace. See Zero Touch Provisioning for Bitbucket.

Boost Advisor on Azure DevOps

  • Service Principal Authentication Option for the Boost Advisor Pipeline

    The Boost advisor pipeline on Azure DevOps can now authenticate with a Microsoft Entra ID service principal as an alternative to a personal access token. A service principal isn't tied to a user account, and a single one works across every Azure DevOps organization connected to your tenant. You can reuse the app registration of your ADO Account Integration when it uses the App Registration method, or create one dedicated to the advisor. The updated boost-advisor.yml template supports both: it uses BOOST_SCM_TOKEN when that variable is defined in the boostsecurityio variable group, and otherwise requests an Azure DevOps access token on each run from AZURE_TENANT_ID, AZURE_CLIENT_ID and AZURE_CLIENT_SECRET. Existing personal access token setups keep working unchanged; to switch to a service principal, update your boost-advisor.yml from the template, add the three variables and delete BOOST_SCM_TOKEN.

    You can also keep the pipeline definition at any path of the boost repository by registering the pipeline yourself under the exact name boostsecurityio.boost-advisor.

Fix with AI on Harness

  • Fix with AI for Repositories Scanned by Harness

    Fix with AI now works for repositories scanned by the Harness Zero Touch Provisioning pipeline. Boost Security triggers a boostsecurity_advisor pipeline that you create once in your Harness project: the advisor runs on your own Harness compute and opens the fix pull request in the target repository, for every SCM the project scans (Azure DevOps, Bitbucket, GitHub and GitLab). See Enabling Boost advisor for the pipeline sample and the secrets and variable it needs.

Monorepository Management

  • Parent Repository Scans Exclude Sub-repository Paths

    The scans of a monorepo's parent repository and the scans of its sub-repositories are now mutually exclusive: the parent repository's scans skip the paths of its sub-repositories, which their own scanners cover. You can therefore provision the same scanners on the parent repository and on its sub-repositories without duplicate findings, and files added outside the declared sub-repositories, such as a new project directory not yet declared, are still scanned by the parent repository. Declaring a sub-repository removes its path from the parent repository's scans, so provision scanners on each new sub-repository.

Azure DevOps Integration

  • New Projects Discovered Within 15 Minutes

    Boost Security now checks your SCM integrations for new projects about every 15 minutes instead of once a day. A new Azure DevOps project, or a new GitLab group under a root integration, appears in Boost Security on its own within about 15 minutes, with webhooks installed and scanning on, and you no longer need to click Rediscover assets. Projects the integration can no longer see are removed on the next check. Discovery still finds only the projects the integration's credentials can read: in Azure DevOps, add the Boost Security service principal or the PAT's user to each new project.

Manual Tags

  • Match Any or Match All Manual Tags

    Manual tag filters now carry a Match any / Match all selector above the tag list, on every view that offers one. Match any is the default and shows the items carrying at least one selected tag. Match all narrows the results to the items carrying every selected tag, for example the assets tagged both critical and non-prod, and the applied filter in the Search For bar shows Match all before the selected tags. The page URL keeps the mode, so a shared link opens with it.

    On Asset Management and Scanner Coverage, several manual tags used to combine as if Match all were selected, unlike every other view. Both now default to Match any like the rest, so a saved or shared link to either view with several manual tags now shows the items carrying any of them. Select Match all to get the previous results. Saved views and shared links to the other views return the same results as before.

Endpoint Protection

Alert Categories

  • Compromised eMudhra Certificate Authorities

    Endpoint scans now flag the devices whose trust stores still trust the eMudhra certificate authorities, which are known to be compromised, under the new Weak eMudhra CA Keys Still Trusted alert category, with a Critical severity. Each alert gives the details of the affected trust store. Requires the endpoint CLI 1.6.5 or later.

Endpoint Protection Policy

  • Save or Discard Policy Changes

    Changes on the policy page are now staged before they apply. The page header counts the unsaved changes. Save opens the Review Policy Changes dialog, which lists each change before you apply them all at once with Confirm And Save; Discard drops them. Nothing changes for your developer endpoints until you save.

Improvements and Fixes

  • More reliable user detection. Users are now detected from the owner of each home folder. This fixes Linux devices that reported no user or alias even when a git configuration was set. Endpoint CLI 1.6.6.
  • Faster scans. User and host details are read once per scan instead of once per collector. Endpoint CLI 1.6.4.
  • Browser extension names. Browser extensions show their display names again, instead of their internal IDs. Endpoint CLI 1.6.4.
  • npm tarball downloads. Through Package Management Protection, npm tarball requests that lost the /npm/ prefix are routed correctly again.

2026-09-30

ASPM

Scanner Policies

  • Safe Deletion of Scanner Policies

    The Scanner Policies list now reports how many scanners each policy is assigned to, in a new Assigned Scanners column. While that count is above zero the Delete action is greyed out and names what has to happen first, instead of failing with an unclear error after the deletion is confirmed.

    The count links straight to the Scanner Coverage page filtered to that policy, so the scanners to deprovision are one click away. Scanner Coverage carries a matching Scanner Policy filter under More.

Jira Integration

  • Per-Project Auto-Close Settings

    Auto-close is now configured on each Jira project rather than once per connection. Every project carries its own Auto-close toggle and its own Closed status, chosen from the statuses that project actually defines in Jira, so a status from one project can no longer be applied to another. Each row is saved on its own, and picking an issue type is now staged behind that same Save instead of applying as soon as it is selected. The connection-wide auto-close toggle and its status dialog are gone.

    A project added from now on starts with auto-close Off and no closed status, instead of copying both from the account's default project. Turn it on for each new project you want it on. Existing projects keep the settings they have.

    Boost Security checks a status against the project's Jira workflow before saving it, and flags a stored status that Jira no longer offers so it can be corrected.

API

  • API Keys Are Scoped to Their Role

    An API key now has exactly the access its Role grants. An Endpoint key, such as a deployment token created from the Endpoint Protection Installation page, registers devices. A Data Upload key, which Boost Security creates and manages for integrations such as Zero Touch Provisioning, uploads scan, SBOM and telemetry results. Neither can read anything else in the platform. Previously every key also carried platform-wide read on top of the role it was given.

    Existing keys were migrated and keep behaving as they did, with one exception: a key whose only role was Data Upload or Endpoint has lost read access. If you were using an Endpoint or Data Upload key to query the GraphQL API, those queries now fail — create a User or Viewer key for the reads. See API Key Roles.

Policies

  • Policy Rules Can Match a Confidence That Is Not Set

    The Confidence attribute in the policy rule editor now offers Unset alongside High, Medium and Low, so a rule can target findings whose scanner never reported a confidence. Until now that value was not in the list and those findings could only be caught indirectly. See Matching a Confidence That Is Not Set.

    This changes what a rule can be written to say, not what any saved rule matches: a confidence that is not set has always ranked below Low, so a rule matching a confidence below Medium was already matching these findings. No policies were migrated.

Provision Scanners

  • Skip the Initial Scan When Provisioning

    The scanner-provisioning modal now offers a Skip initial scan after provisioning checkbox beside the Complete button, in both Easy and Advanced provisioning. Ticking it provisions the selected scanners without launching any scan jobs, so bringing a large set of repositories under coverage no longer floods your CI/CD pipelines. The initial scan still runs unless you tick the box, and the choice applies only to the provisioning you are performing.

    Skipping the scan leaves the affected security categories reporting as Pending until something scans the asset — including categories that are covered today, because a category reports as Pending as soon as any of its scanners is awaiting a first scan. Nothing is queued: the next push to the default branch, or a manual scan, clears it. See Skipping the Initial Scan.

Findings

  • Jira Tickets in the Findings CSV Export

    The Findings and Violations CSV exports now end with three columns describing the Jira ticket tracking a finding: ticket_key, ticket_url and ticket_status. A finding with no ticket exports three blank cells. See Jira Ticket Columns.

    The columns are appended after the existing ones, which keep their name, position and value, so an existing script that reads the export by header or by column index keeps working.

Azure DevOps Integration

  • Declared Organizations for Microsoft Entra ID and App Registration Integrations

    Azure DevOps integrations backed by Microsoft Entra ID or an App Registration now cover exactly the organizations you declare, instead of discovering them. Both installation wizards gain a step to declare the list before the webhooks are installed, and each organization is validated against the integration's credentials when you click Next: it must be readable and hold at least one visible project. Projects inside a declared organization are still discovered automatically, and personal access token integrations are unchanged.

    After installation, the list is edited from the Configuration tab of the integration's details, where a chevron on each Microsoft Entra ID or App Registration row opens the editor. Removing an organization detaches its projects while keeping their existing findings. Existing integrations were seeded with the organizations Boost Security already covered; review the seeded list once, since organizations that had already stopped being covered were not carried over. See Declared Organizations.

2026-08-31

Endpoint Protection

Endpoint Devices

  • Per-Device Tokens and the Endpoint Devices Page

    Each device now authenticates with its own unique device token, issued when the device registers, instead of a shared API key. The new Endpoint Devices page lists every device that has been enrolled; administrators can revoke a device's access, or delete a device to revoke its access and remove its data: the developers, components, and alerts collected from it.

    Devices deployed before this release are migrated automatically: each one receives its own device token as it updates, with no action required.

Install with Script

  • Deployment Tokens

    Script installation now authenticates with a deployment token created from the Installation page. A deployment token can only be used to register devices, is active for 30 days by default (the duration can be changed when creating the token), and is meant to be single use. Delete it once the fleet is deployed.

2026-08-19

ASPM

API

  • API Key Expiration

    Application keys can now be given an expiration. The Add Application Key dialog offers an Expiration of 30 days, 60 days, 90 days or 1 year, and keys still default to never expiring. A new Expiration column in the Application Keys list shows when each key lapses.

    The expiration of an existing key — including a key created with no expiration — can be changed from the key's row at any time, and can be moved earlier or later. An expired key stops authenticating and stays in the list, marked EXPIRED, until an administrator deletes it.

2026-08-13

ASPM

Posture Reports

  • Pending Scanner Coverage on the Coverage Chart

    The Coverage chart on the Report page now stacks a fourth state, Pending, next to Covered, Scan Error and Uncovered. It counts the assets whose provisioned scanners have not reported a scan result yet — the state a scanner sits in between being provisioned and completing its first scan. These assets were previously left out of the bars, so accounts that recently provisioned scanners will see taller bars than before, and the chart legend now names each of the four states.

  • Exact Counts on Report Charts

    Hovering over any chart on the Report page — Coverage, Violations, Findings, Critical Risks, and the per-finding-type Vulnerability and Coverage trends — now shows the exact counts behind the bar or point, instead of having to read them off the axis.

2026-08-03

ASPM

Scanner Coverage

  • Scanner Policies

    Scanner Policies are named, reusable sets of directives that govern how the scanners they are assigned to behave. Define a policy once on the new Scanner Coverage → Scanner Policy page, then assign it to scanners across your assets.

    This first release ships one directive, File pattern matching, which restricts a scanner to the files it is meant to cover: the scanner runs only when the files changed by a pull request or pushed commit include a match for one of the policy's patterns; otherwise the scan is skipped and a passing check is posted to the SCM. Use it to keep an Infrastructure-as-Code scanner on Terraform and Kubernetes manifests, or an SCA scanner on dependency lock files. Further directives will extend what a Scanner Policy can govern.

2026-05-13

Endpoint Protection

Endpoint Scanning

  • VS Code Extension Enhancements The Boost VS Code extension has been updated with expanded package coverage and improved developer experience.

    • IDE deep links: secrets detected by Boost's Bagel scanner now link directly to the specific file and line in the developer's IDE, enabling faster secret remediation without context switching.
    • Expanded package support: the extension now detects globally installed and project-defined npm and PyPI packages, as well as Homebrew components.
    • Package paths: the extension surfaces where packages are defined within project files, distinguishing installed packages from those merely referenced in dependency manifests.
    • npm cooldown alerts: developers are notified when newly introduced npm packages fall within the low-maturity cooldown window, flagging packages less than 7 days old.

Inventory and alerts

  • Cross-View Navigation & Group By Component

    The Endpoint Security page now includes cross-linking between views, enabling seamless navigation between the Developer view and the Alert view in both directions. A new Group By Component view is also available for aggregating endpoint findings by the detected component.

  • Developer Identity: Enhanced Contributor Attribution

    Boost now uses an improved developer identity resolution process to accurately attribute findings to the correct contributor. The system checks git configurations, workstation user accounts, and logged-in email addresses, falling back to a unique workstation ID when no other identity is available.

    • Multiple identities detected on a single machine are tracked as aliases under a unified developer record.

Policy

  • Grouped Slack Notifications

    Endpoint malware alerts are now grouped by package when multiple developers trigger the same alert simultaneously, preventing notification fatigue from high volumes of duplicate messages for a single malware event across a large developer fleet.

  • Allow/Deny Rules for Specific Package Versions

    The Boost allow/deny policy framework now supports targeting specific package versions or version ranges. Teams can define granular rules that permit or block exact versions of a component, providing finer-grained control over supply chain governance.

ASPM

SCM Integrations

  • Bitbucket: API Token Authentication (Marketplace App Transition)

    Boost's Bitbucket integration now uses API Token-only authentication following Atlassian's deprecation of the marketplace app model. Users connect via Email and API Token and select their workspace from a dropdown within the integration card.

    • ZTP enablement automatically uses the configured token — no separate credential configuration is required.
    • Migration guidance: do not delete and recreate your existing Bitbucket integration before migration tooling and documentation are available. The recommended path will be communicated when ready.

AI-Powered Remediation & Governance

  • Fix with AI: Generally Available

    Fix with AI is now generally available to all users — no feature flag required. The Fix with AI button is visible and actionable on all supported findings. If pull request creation fails, a direct link to the pipeline logs is provided to assist with troubleshooting.

Policy

  • Parametrized Policy: Per-Asset Jira & Outbound Notification Configuration

    Teams can now configure Jira and outbound notification settings on a per-asset basis using External Configuration, accessible from the Asset Management page under Actions. When creating a policy rule action for notifications or tickets, users choose between Policy Designer (organization-wide settings) or External Configuration (asset-specific overrides).

2026-04-21

Endpoint Protection

Endpoint Scanning

  • VSCode Extension & CLI Available

    The Boost Endpoint Security Extension and CLI are now available for installation, supporting developer workstation scanning across macOS, Linux, and Windows.

    • Authentication is supported via OAuth (using the Boost user identity) or API Token (user context inferred from local configuration).
    • Script-based installation is the recommended deployment method for the CLI.
    • Uninstalling the CLI removes the local agent and log files from the workstation while preserving historical scan data within Boost.

Inventory and alerts

  • Extended Package Detection

    Endpoint Security now detects npm and PyPI packages installed on developer workstations, expanding supply chain risk visibility beyond CI/CD pipelines.

Policy

  • Extended Malware Policy

    • Malware policy framework: configure allow/deny lists for specific components. Policy changes trigger automatic re-evaluation of all scanned endpoints.
    • Malware detections generate alerts and can trigger outbound notifications via Slack or Microsoft Teams.
    • Custom components can be added to the deny list to proactively block packages not yet present in the environment.

      Note

      Deny list rules currently match on provider and package name only — package version filtering is not yet supported.

ASPM

Scanners

  • SBOM: Lockless NuGet Package Detection

    Boost now supports SBOM scanning for .NET projects that do not use lock files, using the OSV Scalibr scanner. This extends software composition analysis coverage to NuGet dependencies that were previously undetectable without a lock file.

    Recommendation

    Enable only one SBOM scanner at a time. Concurrent scanners overwrite each other's results on each run; the UI does not currently prevent this configuration.

Integrating with Code-To-Cloud Context Providers

  • Upwind Integration: Runtime Reachability for Container Workloads

    Boost now integrates with Upwind to enrich findings with runtime reachability context. Teams can identify internet-facing vulnerabilities in container workloads and correlate images across multiple sources such as ECR and Google Artifact Registry. - Internet reachability context from Upwind can be used directly in policy rules to prioritize runtime-exposed risks.

AI-Powered Remediation & Governance

  • Fix with AI: Support for All SCM Platforms

    AI-powered fix generation is now supported across all four supported source code management platforms: GitHub, GitLab, Bitbucket, and Azure DevOps. Teams on any SCM can now receive AI-generated remediation pull requests directly in their repositories.

    Note

    Branch templates may require a manual update to activate this feature on existing integrations. Thorough documentation is provided for the setup process.

  • Fix with AI: False Positive Detection & Quality Review Agent

    Two new quality controls have been added to the AI remediation workflow.

    • False positive detection: the AI agent now evaluates whether a finding is likely a false positive before generating a fix. When a false positive is identified, it adds a noboost suppression comment rather than producing a code change.
    • Quality review agent: a second agent reviews the generated fix. If unsatisfied, it sends the fix back to the generation agent with feedback for up to three improvement rounds before failing open.

2026-03-30

Endpoint Protection

Endpoint Scanning

  • VS Code Extension

    The Boost Endpoint Security extension for VS Code is now available. Developers can view supply chain inventory and monitor scans in real time as they execute, with detected components and findings surfaced directly inside the IDE.

Inventory and alerts

  • Endpoint Bill of Materials (EBOM): Alerts Categories View

    The EBOM interface has been updated with a new Alerts Categories tab that groups alerts by category for a clearer overview of risk distribution across detected components. Components are grouped by name, with version details accessible within each component's detail view.

ASPM

AI-Powered Remediation & Governance

  • Fix with AI: Pull Request Integration

    The AI-powered fix workflow now surfaces status directly in the Finding Details panel. When a fix is submitted as a pull request, its PR status is visible inline — giving developers immediate feedback without leaving the Boost interface.

  • Fix with AI: Secret Validation & Rotation Guidance

    When the AI agent fixes a Secrets finding, Boost now validates the proposed change before applying it. A warning is automatically posted in the resulting pull request advising the developer to rotate or deactivate the affected secret, ensuring remediation is complete — not just code-level.

Integrating with Third-Party Notification Services

  • Jira Integration: Issue Type Selection

    Users can now configure the Jira issue type (e.g., Bug, Task, Story) directly from the Boost integration card, ensuring findings exported to Jira are created with the correct issue type for each team's workflow.

Asset Management

  • Export: Asset Type Column

    The Asset Management CSV export now includes a dedicated Asset Type column, providing additional context when reviewing exported asset data outside of the Boost platform.

Scanners

  • SCA: C# and JAR Package Support via OSV

    SCA scanning now includes support for C# (.NET) and JAR packages via the OSV scanner, extending open-source vulnerability detection to a wider range of ecosystems.

2026-03-11

Integrating with Third-Party Scanners

  • Dynamic Application Security Testing (DAST) with StackHawk

    Boost now supports DAST through a new StackHawk integration, enabling teams to detect runtime vulnerabilities in web applications alongside existing static and supply chain risk coverage.

    • New StackHawk integration card is available on the Integrations page. Activation requires a StackHawk API Key and a manually configured webhook in StackHawk.
    • New applications added in StackHawk are automatically synchronized on the next scheduled sync cycle.
    • DAST scanning can be enabled via Zero Touch Provisioning (ZTP), and results surface under a dedicated Policy scanner category.
    • Note: This feature is currently available under a feature flag.

Asset Management

  • Application-Level Grouping

    The Asset Management page introduces a new Application grouping view that organizes assets by application name. Each application can contain multiple environments, providing a cleaner structure for teams managing multi-environment deployments.

Integrating with Third-Party Notification Services

  • Multiple Jira Account Support

    Boost now supports adding multiple Jira integrations to a single account. Teams can mix Personal Access Token (PAT) and marketplace-authenticated connections and configure more than two integrations when needed.

    • Ticket IDs are surfaced on the Findings page. Note: IDs may appear identical across different Jira projects, but each links to the correct issue URL in the backend.

Account settings

  • Custom Pull Request Message Length Increase

    The character limit for custom PR messages has been increased from 200 to 1,000 characters, giving security and platform teams more room to communicate policy context and remediation guidance to developers in pull request comments.

2026-02-19

Software Supply Chain & Policy Refinements

  • This release sharpens the policy engine, expands SBOM filtering, and introduces early access to developer endpoint visibility to manage risk across every layer of the supply chain.

    • Low Maturity Package Cooldown Policy

      To guard against "brandjacking" and zero-day malicious packages, Boost now flags dependencies less than 7 days old as low maturity. This allows teams to create a configurable gate against rushing unvetted, brand-new code into production.

    • Advanced SBOM Package Version Filtering

      Users can now filter SBOMs by ecosystem, package name, and specific version ranges (supporting semver). This makes it significantly faster to identify if specific vulnerable versions exist anywhere in the environment.

Cloud & Integration Enhancements

  • AWS Bedrock: Improved Configuration Experience

    The Bedrock setup process has been streamlined with a new dialog featuring required permissions details, region selection dropdowns, guided tooltips, and the ability to select specific inference profiles for applicable models.

  • Jira: Automated Contributor Attribution

    When exporting SAST or Secrets findings to Jira, Boost now automatically identifies and includes the developer who introduced the code as the contributor. This eliminates manual git history lookups during ticket assignment.


2026-01-29

Supply Chain Security & Malware Detection

  • Malware Reporting Banner

    Boost now features a high-visibility malware reporting banner. If a malicious package is identified in your environment, an immediate alert appears upon login, providing details on the incident and guidance on how to identify impacted assets.

Enterprise Policy Management

  • Policy Inheritance

    Maintain organizational consistency by defining "Base Policies" that other policies can build upon. Base rules execute first to create a global security floor, while child policies layer on specific configurations for scanners and components.

  • Policy Rule: Block When Fix Is Available

    A new policy action allows teams to specifically trigger blocks or alerts on open-source findings that have a known fix version available, prioritizing actionable remediation over unpatchable vulnerabilities.


2025-12-05

AI-Powered Remediation & Governance

  • Policy-Controlled AI Fixes in Pull Requests

    Boost can now automatically generate AI-powered remediation suggestions as comments directly within PRs for SAST, IaC, and Secrets findings. This behavior is governed by the policy engine via the "Generate AI remediation" action.

Access Control & Asset Management

  • Granular API Key Roles

    Users can now create API keys scoped to specific roles — User (read & write) or Viewer (read-only) — ensuring integrations operate with least-privilege access.

  • Asset Groups for Organizational Structure

    Organize repositories and org-level assets into manageable groups. This provides the structural foundation for future group-based access policies and improved visibility across teams.

Cloud & Platform Infrastructure

  • ECR Root Integration for Multi-Account Discovery

    Boost now supports root-level ECR integration, enabling the discovery and monitoring of container images across all AWS accounts from a single integration point, reducing setup overhead for large environments.

  • Platform & Interface Enhancements

    • Smarter PR Scan Timeouts: Timeouts now account for repository cloning time, preventing false failures on very large codebases.
    • Archived Asset History: Historical scans for archived assets remain visible in the analysis history, marked with an "archived" indicator to preserve audit trails.
    • SBOM Search State: Search filters and states are now preserved when switching between views, with dynamic linking between repo and package lists.
    • MS Teams Webhook Support: Compatibility updated for the new Microsoft Teams webhook URL format to ensure uninterrupted notifications.

2025-11-18

Advanced AI Remediation Capabilities

  • Boost has introduced significant enhancements to the safety, context-awareness, and workflow integration of its AI remediation engine.

    • Pre-flight Secrets Redaction

      To strictly enforce data privacy, Boost now performs local GitLeaks scanning on code snippets before they are sent to the AI provider. Detected secrets are automatically masked (e.g., ******), ensuring credentials are never exposed to the Large Language Model (LLM).

    • Context-Aware Fixes via Repository Guidelines

      AI agents now consume project-specific documentation (such as cloud.md or gemini.md) to tailor remediation suggestions. This allows the AI to respect architectural decisions, such as enforcing specific ORM patterns (e.g., SQLAlchemy) over raw SQL.

    • False Positive Detection & Suppression

      The AI engine can now identify potential false positives during analysis and will suggest a "no boost" suppression action, reducing noise for developers.

    • AI Remediation in Jira (Preview)

      Users can now trigger AI remediation details directly when creating Jira tickets, populating the ticket with actionable fix logic. Note: This feature is currently enabled via feature flag.

Google Artifact Registry (GAR) Root Account Support

  • Multi-Project Scanning via Service Account

    Boost now supports GAR Root Account integration, allowing a single Google Service Account to list and scan multiple projects simultaneously.

Platform & Interface Enhancements

  • License & AI Component Management

    A new, dedicated tab within the policy interface is available for managing Open Source Software (OSS) licenses and AI components. This UI streamlines the process of allowing or denying specific licenses and AI models across the organization.

  • Microsoft Teams Webhook Updates

    Users can now update Webhook URLs for existing Microsoft Teams integrations directly within the UI, eliminating the need to recreate the integration when URLs change.

  • GitHub App Synchronization

    We have improved the synchronization logic between the Boost dashboard and GitHub. Deleting the Boost App in the dashboard now correctly syncs the status with GitHub (and vice versa), ensuring accurate integration states.

2025-10-28

Documentation Localization

Original Rule ID Policy Category

  • Boost now allows the display of the original rule ID for each finding, ensuring all known issues are tracked and addressed.

2025-09-17 and 2025-10-07

AI Enhancements for Secure SDLC

  • Boost now provides a suite of AI-powered capabilities designed to detect and remediate security risks earlier in the development lifecycle, without sending code outside your environment or introducing unapproved AI models. With additional Model Context Protocol (MCP) Support, Boost now provides the following:

    • Remediate Before Code Is Written

      Boost can now validate and improve code at generation time when using agentic coding tools. Potentially risky code is identified and remediated before it ever appears in the developer’s IDE, ensuring safer code is produced from the start.

    • Remediate Before Code Is Committed

      During development, Boost automatically detects newly introduced risks before merge. Developers receive an inline remediation suggestion directly in their Source Control System, with a one-click fix to apply the recommended change.

    • Remediate Legacy Risks

      A new MCP server enables developers to query Boost directly from their coding agent using natural language. Developers can ask for their highest-risk issues and receive remediation guidance directly in their IDE, simplifying the process of addressing existing technical debt.

These capabilities expand Boost’s security coverage while maintaining strict data-protection controls. Code remains fully within the user’s perimeter and is never transmitted to Boost or external services.

2025-08-25

Supply Chain Inventory

  • Boost now includes base container images in the Supply Chain Inventory. This feature enables users to efficiently review and manage base images used in their Dockerfiles through a rapid, integrated scan. The enhanced visibility strengthens supply chain security by providing comprehensive insights into container dependencies, seamlessly integrated into Boost Security’s existing Supply Chain coverage.

Findings Filters

  • To support the expanded scope of Boost’s scanning capabilities across diverse detection technologies and risk types, we’ve revamped the findings filters interface. The updated design introduces a cleaner, more intuitive UI with natural grouping of filter categories. This allows users to navigate complex datasets effortlessly, quickly pinpointing critical information and prioritizing actionable insights.

2025-08-06

This sprint focused on enhancing user experience by introducing several quality-of-life improvements across the application. These updates streamline workflows, improve usability, and enhance clarity for both administrators and end-users. Below is a detailed breakdown of the new features, enhancements, and fixes included in this release.

Asset Tag Search in Filters

  • Users can now search for assets using asset tags across the Search For filter category, making it easier to locate specific resources quickly. This simplifies asset management and improves efficiency in workflows involving asset searches. This feature is currently available only on the Findings and Asset Management pages.

User Onboarding Improvements

  • Admins can now copy a unique invitation link for each invited user directly from the Users page. This enhancement eliminates the friction caused by email delivery issues (e.g., spam filters) by enabling manual sharing of invitation links. The copied link can be used by the invited user to join the organization on Boost Security, even if they didn’t receive the original email.

    The link becomes available when a user’s status is marked Pending Confirmation, alongside existing options to remove, resend the invite, or change their role.

SSO Service Account Management Without Email

  • Administrators can now manage Single Sign-On (SSO) service accounts without requiring an email address, providing greater flexibility for service account configurations.

    Impact: Streamlines SSO setup for organizations using non-email-based service accounts.

Jira Access Token Updates for Active Connections

  • Users can now update Jira access tokens without disrupting active connections, ensuring continuous integration with Jira workflows.

Organization Details on Asset Management Page

  • The Asset Management page now displays organization details, providing better context for managing assets within multi-organization setups. This update improves visibility and decision-making for administrators managing assets across organizations.

EntraID Service Account Support for ADO

  • Boost now supports service accounts through EntraID for Azure DevOps (ADO) integrations, enabling seamless authentication for automated processes.

Optional Mass Scanning for ZTP

  • Users can now opt out of triggering mass scanning when enabling Zero Touch Provisioning (ZTP) for the first time, giving more control over initial setup. This update prevents unintended resource-intensive scans, improving setup flexibility for users.

Improved Error Handling and Explanations

  • Error messages across the application have been refined to provide clearer, more actionable explanations.

    Impact: Reduces confusion and helps users resolve issues more efficiently.

Branch Visibility in Integrations

  • All ticketing, webhook, and chat integrations now display the specific branch where a violation was detected in multi-branch configurations. This update provides clearer context for violations, enabling faster resolution in complex environments.

Improved Policy Scanner Rule Search

  • The Policy Scanner Rule search functionality has been enhanced to provide more precise filtering, allowing users to quickly find relevant rules. This saves time and improves usability when managing or troubleshooting policy rules.

2025-07-04

Custom Asset Tagging

  • We’re excited to introduce Custom Asset Tagging, a highly requested feature that allows users to define and manage their own asset tags directly within Boost. This goes beyond the default attributes ingested from your source control system, giving you full flexibility to tailor asset metadata to your specific needs.

    This new functionality was designed with scalability in mind, supporting everything from small teams to large enterprise environments. Additionally, we’ve integrated custom tag filtering across all views in the platform, making it easier than ever to organize, search, and manage assets.

    This feature was built in direct response to user feedback. Thank you for helping shape the future of Boost!

Multi-branch Support

  • We’ve expanded Boost’s capabilities to support multi-branch monitoring, enabling teams to scan, track, and manage multiple branches of code within a single repository.

    This enhancement goes beyond pull request coverage and now includes full baseline scans, automated ticketing, reporting, etc, across all defined branches. You can now configure branch-specific workflows directly from the Boost UI, supporting teams that maintain separate development, staging, and production environments, as well as those managing multiple versions of the same application simultaneously.

    No more trade-offs between dev and prod, or v1.1 and v2.0 - If the branch exists, Boost can scan it.

2025-06-12

Application Posture Reporting

  • We’ve launched an all-new Reports page designed to help users better understand, track, and scale their AppSec programs. Key highlights include:
    • A unified view of asset scale and security scanning coverage over time.
    • The ability to quickly identify areas of concern within your security posture.
    • Deep insights into specific coverage types and see overviews of your most frequently exposed secrets, riskiest packages and license, or most frequently coded static vulnerabilities. -Full filtering support across time periods and asset scopes, and scanning technologies.

SBOM Enhancements

  • Software Bill of Materials (SBOM) views and exports have been upgraded for even more clarity and context. What’s new:
    • Vulnerability lists now include package names inline with each reported issue.
    • SBOM export files now contain source repository details for improved traceability.
    • Added enrichment support for Ruby packages, enabling deeper insights into gem-based dependencies.

Asset Archiving

  • Many users have visibility into many repositories that are no longer relevant, such as internal developer pet-projects, deprecated services, or archived proof-of-concept apps. To help focus your AppSec efforts, Boost now supports Asset Archiving, allowing you to:

    • Manually archive repositories that shouldn’t count toward active posture reports.
    • Automatically respect source control archival status, ensuring inactive repos are excluded from security coverage metrics.

    This gives your team a cleaner, more accurate view of your actual application surface area.

2025-05-28

SBOM Direct File Upload

  • You can now upload standalone CycloneDX SBOM files directly to Boost Security without the need for build pipeline or source code access. This feature is particularly useful for teams working in environments like Mergers & Acquisitions due diligence, where source code may be unavailable. Simply upload a CycloneDX SBOM, and Boost will automatically enrich it with:

    • Known vulnerability data (CVEs, EPSS, CVSS)
    • Malware insights
    • OpenSSF Scorecard metrics
    • Open source license detection
    • Nightly monitoring for emerging threats, including 0-day vulnerabilities

    This ensures your SBOMs receive the same level of analysis and protection as those generated through integrated pipelines.

Audit Logging and Activity Reports

  • We’ve introduced a new Audit page for administrators to track, filter, and report on user activity within the platform. Gain visibility into:

    • Who modified which security policies, and when
    • Which scanners were added or removed—and by whom
    • Key operational actions across your instance

    This feature enhances accountability and compliance across your teams.

Scan History Filters

  • Since day one, Boost has empowered teams to define security policies that proactively notify developers of potential weaknesses, whether through pull request comments or build fail checks—before code merges into the main branch. However, visibility into how often and where these policies were triggered has been limited.

With our new Scan History filters, it's now significantly easier to track when and where policy enforcement occurs, giving you deeper insight into your security posture across the development lifecycle. With these filters, you can quickly view:

  • All scans that triggered Fail Checks
  • Scans that flagged policy violations in pull requests

This provides clearer insights into policy coverage and developer feedback loops over time.

Performance Enhancements

  • Managing thousands, or tens of thousands of repositories? You’ll see a major boost in performance. Our backend optimizations have achieved up to 10x improvement in load times on the scanner coverage page. As your codebase grows, Boost scales with you - ensuring a smoother, faster experience for enterprise-scale operations.

2025-04-29

End of Life Detection

  • Boost Security's SBOM and SCA scanners have been updated to now support detection and enrichment of End-of-Life (EoL) packages. You can:

    • Filter your entire SBOM to identify EoL packages.

    • Receive proactive notifications when EoL packages are detected in your codebase or introduced via pull requests.

SCM Integration Enhancements

  • GitHub

    Boost has added support and detection of RuleSets for branch protection settings. You can now identify if your repositories lack secure configuration using RuleSets and can alert your team whenever your security posture weakens based on RuleSet changes.

  • GitLab

    GitLab integration now supports Group and Service Access Tokens in addition to Personal Access Tokens

  • Azure DevOps

    Connection to ADO now supports Microsoft Entra ID in addition to Personal Access Tokens.

Policy Enhancements

  • Our incredibly powerful and flexible policy engine has been updated with some additional usability improvements, allowing users to reorder their rules quickly through the UI to create even faster and simpler customization by manipulating the execution order of your rules.

Findings Detail Redesign

  • Finally in this sprint, we’ve rolled out a redesigned Findings Detail panel for an improved user experience. Key improvements include:

    • A cleaner, more intuitive layout.
    • Easier navigation to critical insights.
    • Faster access to actions and remediation steps.

2025-04-02

Filters Redesign

Filtering within Boost just got a major upgrade!

We’ve completely redesigned filters across all relevant pages to improve usability, reduce complexity, and maximize screen space. This update ensures you can find the data you need more quickly and take action with greater ease.

Highlights:

  • Cleaner, more intuitive filter layout
  • Enhanced usability on all filtered pages
  • Optimized screen real estate for improved workflow

Performance Enhancements

Working with large datasets just got significantly faster.

Our backend team has optimized filtering and search algorithms for high-volume use cases, resulting in a 10x improvement in load times when handling six-figure datasets on the Findings page.

Ideal for teams managing:

  • Tens of thousands of violations
  • Hundreds of thousands of findings

Your triage workflow just got supercharged.

Runtime Reachability Support

We’ve expanded our reachability features!

Building on last year’s Code Reachability capabilities (powered by the OSV scanner), we now support Runtime Reachability via our Dynatrace integration.

You can now: - Identify which vulnerabilities Dynatrace has confirmed have Runtime Reachability - Build policies around runtime-loaded vulnerabilities - Prioritize risks more effectively

This gives your security policies even greater precision.

Other Improvements

  • Policy Rule Clarity: We’ve improved language and consistency in our policy rule definitions, making it easier for new users to understand and use the policy engine effectively.
  • GitLab Integration: Now supports Service Account Access Tokens with the same functionality as Personal Access Tokens.
  • Azure DevOps Integration: Now supports Microsoft Entra ID connections with the same functionality as Personal Access Tokens.

2025-02-21

Code to Cloud - Integration with Dynatrace

  • Dynatrace is an industry leader in Infrastructure and Runtime observability, and as a Boost user you can now benefit from all Dynatrace has to offer as enrichment to our source code, CI/CD, and Supply Chain risk detections! Provide your developers with runtime context of which vulnerabilities are in production or have public routes from the internet. Provide your infrastructure team with code context of which repository or development team members are responsible for the code running on a specific service!

Enhanced Default Coverage

  • Add SAST to the auto-provisioning list! With Boost you can now automatically detect new assets and provision static analysis scanning to the newly detected code with no human intervention. This joins the existing automated provisioning capabilities for Supply Chain, Secrets, SBOM, and SCA!

Expanded Critical Risk Detection

  • Our ability to identify critical risks has expanded once again, this time to flag repositories that contain PII and are missing branch protection settings.

2025-01-31

Deeper Runtime Detections and Policies

  • Boost will now enrich services and findings with detected Root user access and Privileged containers. For example, you can now have policies that alert when detecting certain vulnerabilities existing within services that have Root Access.

Enhanced Asset Discovery Information

  • With multiple potential sources of asset detection (Source Control Management, 3rd party Scanner, etc), it can become unclear where an asset in Boost originated from. We have enhanced the Asset Management page with additional metadata to help you track your asset origins

Export CIS Supply Chain Compliance Report

  • We’re continuing to enhance our Compliance feature with file exporting. Filter your portfolio or compliance rules down to just the scope you want to report on and create CSV data exports for downstream reporting or archiving

2024

2023

2022