Releases of June 2023

This version introduces support for query override at the application level for scans. By allowing query overrides at the application level, users can customize scan parameters and tailor the scanning behavior specifically for individual applications, optimizing the scan results and enhancing the overall security assessment process.

Users now have the option to upgrade their existing Read/Write privileges to Admin privileges within the Code Repository system. By doing so, users gain access to additional Webhook functionalities, enabling them to perform a wider range of actions and further enhance their workflow within the system.

Users now have the flexibility to manually add or modify version releases for scans that were launched without a tag. This can be done conveniently in both the Resource Manager list view and the Project Scan History view after the scan has been completed. This enhancement allows for better organization and tracking of scans, ensuring accurate version information is associated with each scan.

The IaC Security version has been upgraded to 1.7.0.

In JIRA, all statuses are categorized under To Do, In Progress, or Done. As part of our effort to streamline the user experience, we have removed the OPEN-STATUS and CLOSE-STATUS configuration fields. Instead, we now automatically consider all statuses in the To Do and In Progress categories as open-status, and all statuses in the Done category as close-status.

This update allows us to support custom states in a drop-down list, reducing the number of configuration steps required, and providing a more intuitive, user-friendly experience.

Lines of Code (LOC) analysis is used in generating reports, calculating code density, and generating various charts. This functionality has now been extended to include the IaC engine. It is also a critical factor in determining the maximum LOC allowed in a tenant, with a limit of 9.5 million LOC in Q3.

The concurrent scan capacity has been expanded to enhance performance and efficiency. The following updates have been implemented:

Max Concurrent scans on Checkmarx One per tenant: The system can now handle up to 1000 concurrent scans simultaneously, ensuring smooth operation without failures or significant latency in scan time. This capacity allocation is distributed:

Scan throughput on Checkmarx One per tenant: The system can now process up to 10 new scan requests per minute, enabling faster initiation of scans and improved overall throughput.

Scan latency: The maximum waiting time for a scan in the queue has been optimized to 10 seconds, minimizing any potential delays and ensuring timely scan execution.

Code Repository integration now supports Bitbucket Single Tenant.