Cortex connects to many third-party vendors whose system interfaces frequently change. As a result, integration behavior or configuration steps may shift without notice. If you encounter unexpected issues, check with your system administrator or refer to the vendor’s documentation for the most current information. Additionally, integration sync times vary and are subject to scheduling overrides and timing variance.
Overview
Checkmarx is an automated application security platform that checks source code for security vulnerabilities and compliance issues. Integrate Cortex with Checkmarx to drive insight into the vulnerabilities detected on your entities. This integration is supported for Checkmarx Static Application Security Testing (SAST).How to configure Checkmarx with Cortex
Prerequisites
Before getting started, create a user with access to thesast_rest_api scope.
Configure the integration in Cortex
- In Cortex, navigate to the Checkmarx settings page.
- Click Integrations from the main nav. Search for and select Checkmarx.
- Click Add configuration.
- Configure the Checkmarx integration form:
- Username and Password: Enter the username and password for the user with access to
sast_rest_api. - Host: Enter the full URL of your Checkmarx instance.
- Username and Password: Enter the username and password for the user with access to
- Click Save.
How to connect Cortex entities to Checkmarx
Discovery
By default, Cortex will use your associated Git repository (e.g.repo-name) or the service tag as the “best guess” for the Checkmarx project name.
If your repository and entity names don’t cleanly match the Checkmarx CxSAST project names, or if you have multiple Checkmarx projects for a service, you can add a Checkmarx project ID (recommended) or a Checkmarx project name in the Cortex entity descriptor.
Editing the entity descriptor
We recommend using the project ID as it is a unique identifier across projects. Example using project IDs:Using the Checkmarx integration
Entity pages
Once the integration is established, vulnerabilities pulled from Checkmarx will be available for each entity in the Code and Security block in the Overview tab. While viewing an entity, click Code & security > Checkmarx. On this page, view the number of vulnerabilities per severity and a link directly to your Checkmarx instance.Scorecards and CQL
With the Checkmarx integration, you can create Scorecard rules and write CQL queries based on Checkmarx details. See more examples in the CQL Explorer in Cortex.Check if Checkmarx project is set
Check if Checkmarx project is set
Check if entity has a registered Checkmarx project in its entity descriptor. If there is a Checkmarx project name, we will try and make sure that the project exists in Checkmarx.Definition:
checkmarx (==/!=) null: BooleanExampleIn a Scorecard, you can write a rule to check whether an entity has a Checkmarx project set:Checkmarx scan risk
Checkmarx scan risk
Get the maximum scan risk among the entity’s project’s latest scansDefinition:
checkmarx.sastScanRisk(): NumberExampleIn a Scorecard, you can write a rule to verify that an entity has no Checkmarx projects where the latest scan risk is higher than 35:Number of Checkmarx vulnerabilities
Number of Checkmarx vulnerabilities
Get the count of all vulnerabilities for an entity’s Checkmarx project’s last scanDefinition: Verify that an entity has less than 5 vulnerabilities total:
checkmarx.numOfVulnerabilities(): NumberExampleIn a Scorecard, you can write a rule to verify that an entity has no vulnerabilities with a severity of HIGH:View integration logs
This feature is available in Cortex cloud.

FAQs and troubleshooting
Does Cortex support integrating with Checkmarx One? No, Cortex does not currently support Checkmarx one. Only Checkmarx SAST is supported for this integration.Still need help?↗
The following options are available to get assistance from the Cortex Customer Engineering team:- Email: help@cortex.io, or open a support ticket in the in app Resource Center
- Slack: Users with a connected Slack channel will have a workflow added to their account. From here, you can either @CortexTechnicalSupport or add a
:ticket:reaction to a question in Slack, and the team will respond directly.