Checkmarx
Connect Checkmarx to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Checkmarx to collect vulnerability scanning evidence with automated compliance tests, switched on per workspace.
| Category | Vulnerability Scanning |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Checkmarx's guide | docs.checkmarx.com |
Connect with an API token
-
In Checkmarx:
- Log in to Checkmarx One (open the URL for your environment and enter your Tenant Account, Username and Password) as a user that holds only the view permissions below. An API key inherits the roles of the user who generates it.
- Select Settings › Identity and Access Management in the main navigation. The IAM portal opens.
- In the main navigation, click API Keys, then click Create Key.
- Optionally fill Note, adjust Expiration period (30 to 365 days), and add Notification emails.
- Click Create, then copy the key from the window that opens. Once you close the window you can no longer access this API key.
- Give the user (directly or through a custom role) the Checkmarx One permissions view-projects (View projects), view-scans (View scans) and view-results (View results).
Where to find the other values:
- Tenant: The Tenant Account name you enter on the Checkmarx One login page.
- Region: The environment of your Checkmarx One URL: US (ast.checkmarx.net), US2 (us.ast), EU (eu.ast), EU2 (eu-2.ast), DEU (deu.ast), ANZ (anz.ast), India (ind.ast), India 2 (ind-2.ast), Singapore (sng.ast), UAE (mea.ast), Israel (gov-il.ast).
Checkmarx shows the secret only once, so copy it before you leave the page.
Paste the Checkmarx One API key into the Refresh token field (Checkmarx exchanges it for an access token; click Show details on the key window for the token request curl). Whenever the Checkmarx One license is updated (for example a new scanner is added), all existing API keys become invalid and must be regenerated. An administrator can enforce the default expiration period, locking that field.
Source: docs.checkmarx.com, docs.checkmarx.com, checked 2026-10-07.
The permissions Safeguard needs:
view-projects,view-scans,view-results. -
On Compliance › Connectors, open Checkmarx, click Connect, choose API token and fill in:
Field What to enter Refresh token Required. Stored encrypted and never shown again. Tenant Required. Region Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Checkmarx and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC7.1 | 4 |
| ISO/IEC 27001 | Automated tests | A.8.8 | 4 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1) | 4 |
| PCI DSS | Automated tests | 6.3.3, 11.3.1 | 4 |
| NIST CSF 2.0 | Automated tests | ID.RA-01, ID.RA-06 | 4 |
These tests are switched on per workspace by the Safeguard team.
Related
- Vulnerability Scanning connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks