Upcoming Single-Tenant Version | 3.42

When setting up a code repository integration with Azure DevOps (ADO), the authentication is now done via Microsoft Entra OAuth (in place of Azure DevOps OAuth which was used previously). The change was made because the previous method is no longer supported by ADO.

To learn more about Entra, see Microsoft documentation.

Easily start authenticated DAST scans without writing a YAML file. This new flow simplifies onboarding by guiding users through setup and authentication via a user-friendly UI, even when initiated from the CLI.

Admins can now manage webhooks at the tenant level, enabling centralized configuration across multiple projects. This reduces manual setup, ensures consistent settings, and streamlines administration for large environments.

The PATCH method is now supported for both Update Applications and Update Projects endpoints, allowing partial updates of specific fields without requiring the full data set.

This improves API efficiency, reduces data transfer, and simplifies workflows by letting users make quick changes - such as adding a tag - without affecting other properties. As a result, updates are faster, more flexible, and require fewer API calls.

See API documentation for the PATCH method in Applications and Projects.

ASPM risk score results are now shown directly in Checkmarx One IDE plugins, aligning the developer experience with the web app. This eliminates the noise of unprioritized findings by allowing developers to focus on high-risk vulnerabilities first.

The integration streamlines remediation, improves efficiency, and promotes adoption by embedding meaningful risk insights directly into the developer workflow.

This feature is currently available only for VS Code. For more information, see documentation.

The SAST engine in Checkmarx One has been upgraded to version 9.7.3. To discover all the new features and updates in the latest version, refer to this page.

To simplify and scale CxLink client distribution, customers can now pull the CxLink image directly from Checkmarx's Docker Hub account. This eliminates the need for manual TAR file delivery and local Docker installation steps previously required, providing a more streamlined and scalable deployment process.

SAST Policy rules now support grouping conditions to enable more precise break-build logic. For example, a rule can now break the build if there are over two High severity vulnerabilities that are also older than 10 days.

All conditions in a group must match the same result to evaluate as true. A rule triggers only if all groups are true.

Existing rules will be migrated with each condition placed in its own group to preserve current behavior. New rules default to a single group, with the option to add more.

Users can now return to previously visited pages with their filters, sorting, and view state preserved - whether using the browser's back button or in-app navigation. In addition, users can save custom views as their default, eliminating the need to reapply the same filters and sorting daily.

This enhancement is especially helpful on pages with customizable tables, where many users follow the same steps every day to get started.

The new Engineering Dashboard in Analytics helps organizations manage application security visibility across complex engineering structures. It introduces dynamic data segmentation by project, application, tag, and group (such as teams or departments), aligning key performance indicators with the actual organizational context.

This update enables clearer communication of trends and status across the enterprise, supports identification of responsible teams, and improves decision-making on where attention is needed.

A new KPI, Vulnerabilities by Aging and Severity, is now available in Analytics to help organizations monitor how vulnerabilities evolve over time based on severity. This metric provides visibility into remediation efficiency, allowing teams to assess alignment with SLA targets and overall risk management goals.

By tracking aging trends, security teams can prioritize efforts on high-severity issues, evaluate remediation performance over time, and identify areas that require intervention. The KPI also includes drill-down functionality, offering a detailed list of vulnerabilities that can be shared directly with development teams for faster resolution.

The new IDE KPI in Analytics tracks developer activity through IDE plugins and CLI tools to measure the adoption of Shift Left security practices. This KPI helps organizations evaluate how proactively security is being integrated into the development workflow.

To improve visibility into project-application associations, an Applications column has been added to the Projects page. This column displays which applications a project is associated with.

You can now integrate ACR private registries with Checkmarx One, enabling the Checkmarx One Containers scanner to scan images in the registry. We provide a convenient wizard for setting up the integration.

For more information, see documentation.

You can now integrate Red Hat Quay private registries with Checkmarx One, enabling the Checkmarx One Containers scanner to scan images in the registry. We provide a convenient wizard for setting up the integration.

For more information, see documentation.

We now support including data identified by the Containers scanner in SBOM reports. When generating an SBOM for an application, you can now select which scanners to include in the report, SCA and/or Containers. This will increase visibility into all of the open source components used in your application.

To learn more about Checkmarx One SBOM Reports, click here.