Checkmarx One Azure DevOps Plugin - Changelog

Added a new environment variable, SCS_REPO_TOKEN, for submitting your repo access token when running SCS Scorecard scans. See Repository Health (OSSF Scorecard)

General improvements and bug fixes

Added support for the new Software Supply Chain Security (SCS) module, which enables running Secret Detection and Repository Health scans on your projects. For more info, see Software Supply Chain Security.

Added support for container-security as an independent scanner. For more info, see Container Security.

Added support for *.rs (Rust source code) files.

 To make the Checkmarx One plugin for ADO more lightweight, the CLI tool has been removed and now needs to be downloaded separately during use. This change may affect customers who restrict access to whitelisted domains, requiring them to add download.checkmarx.com to their whitelist. Customers who are unable to whitelist this domain, can use an older version of the plugin, follow the links provided below.

Enabled seamless use of proxy parameters configured in Azure settings.

General improvements and bug fixes

General improvements and bug fixes

General improvements and bug fixes

General improvements and bug fixes

General improvements and bug fixes

The CLI that this plugin is based on is now signed with the Checkmarx digital signature, indicating that this is an official Checkmarx product. This enables communication from this plugin to bypass firewalls on Windows computers that previously blocked the unsigned CLI.

We have improved the precision of the exit codes in order to give a more clear picture of which particular scanners failed. We have also created a new CLI command, results exit-code, for retrieving information about the completion status for a particular scan in Checkmarx One, as well as details about failures of specific scan engines.

Added a new flag, --sast-fast-scan to the additional_params, for running SAST scans in fast scan mode.

Added a new flag --application-name to the additional_params, which enables users to assign the project to a specific application.

Note: This is only effective when creating a new project and assigning it to an existing application.

Added Directory.Packages.props to the list of included files (when creating the zip archive for scanning).

Improved the "Results Summary" shown in the CLI output. The summary now shows vulnerabilities by severity level for each scanner separately, in addition to the overall totals.

Remediated vulnerabilities that we identified in our project.

Uses CLI version in which vulnerabilities affecting that project have been remediated.

Fixed issue that submitting --groups was interfering with project configuration (e.g., removing designation of primary branch).

Fixed issue that sarif reports had been failing when no vulnerabilities were identified.

Fixed issue with SCA risk management.

Added an output variable CxOneScanId, which can be used to reference the scan later on in the pipeline, e.g., to generate a report.

Fixed issue that when checking for policy violations times out it had been causing the CLI to return a fail status.

Updated for CLI version that uses GO version 1.21.1, in order to remediate a vulnerability.

Added an environment variable, "CX_IGNORE_PROXY", for ignoring proxies. Mark the variable as true to ensure that all Checkmarx One CLI commands run directly from the local machine.

Added Podfile and Podfile.lock to the list of included files (when creating the zip archive for scanning).

Added information about violated policies to the scan summary output.

Enabled SBOM reports for all tenant accounts.

Increased the default limit for projects returned using the project list command to 10,000. (This enables Checkmarx One to effectively verify whether a project with the specified name already exists when a scan is initiated via CLI/plugin.)

Added the ability to generate SBOM reports. SBOMs can be generated using CycloneDX or SPDX format. SPDX reports are output in JSON format, and CycloneDX can be output as JSON or xml.

We added a new environment variable, CX_HTTP_PROXY, which can be used to designate a specialized proxy for Checkmarx One. When this is used, it overrides the proxy specified in your general HTTP_PROXY variable.

You can now designate a scan as a "Private Package" and assign a package version to it using the Additional Parameters options. Once a private package has been scanned, info about the risks affecting that package will be identified by SCA when that package version is used in any of your projects. You can download an article about private packages here.

We added the --exploitable-path flag to the Additional Parameters options. This enables you to designate whether or not Exploitable Path will run on this particular scan. When used, this overrides the designation made in the project settings.

We also added a flag --sca-last-sast-scan-time, which enables you to specify the number of days that SAST scan results are considered valid for use in Exploitable Path (i.e., if there is no current SAST scan, how many days prior to the current SCA scan will Checkmarx One look for a SAST scan to use for analyzing Exploitable Path.)

Improved memory usage when uploading zip files.

Added file extensions go.mod, go.sum, *.dart, and *.plist to the list of included files (when creating the zip archive for scanning).

Rollback change of product name, back to Checkmarx AST.

All references to AST have been changed to use the new product name "Checkmarx One".

Added option to generate reports in PDF format by setting --report-format to pdf. For PDF format reports, you can add the following additional flags:

The KICS scanner is now referred to in Checkmarx One as "IaC Security". All mentions of the scanner and the vulnerabilities identified by it, now refer to IaC Security.

The API Security scanner is now supported for use via the CLI. When running the scan create command, you can now add api_security to the list of scanners under --scan-types.

General improvements and bug fixes

General improvements and bug fixes

Added support for Azure 2019

You can now add filters to the scan create command (to exclude files/folders from the scan) separately for each specific scanner. The flags for the new filters are: --sast-filter <string>, --kics-filter <string>, --sca-filter <string>. See scan create.

You can now add an ssh key to a scan, using the flag --ssh-key <string> with the path to the ssh private key.

Added new --sca-resolver-params flag to the scan create command. See documentation here.

Fixed problems with proxy connection.

In the scan create command, we renamed the format flag as scan-info-format.

Renamed the results command as results show command.

Updated UI elements to reflect the new Checkmarx branding (e.g., logo).

Fixed naming of agent for scans run via Azure DevOps to accurately reflect scan origin.

Added SummaryJSON reports.

Added the --scan-timeout <int> flag to the scan create command, enabling users to specify a time limit after which the scan will fail and terminate. See documentation here.

Updated UI elements to reflect the new Checkmarx branding (e.g., logo).

Updated CLI to version 2.0.4

Added branch parameter (required)

Automatically trigger SAST, SCA and KICS scans from Azure DevOps pipelines

Supports adding a Checkmarx One scan as a pre-configured task or as a YAML

Supports use of CLI arguments to customize scan configuration

Interface for viewing scan results summary and trends in the Azure environment

Direct links from within Azure to detailed Checkmarx One scan results and reports