Cobalt
Connect Cobalt to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Cobalt 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 |
| Cobalt's guide | docs.cobalt.io |
Connect with an API token
-
In Cobalt:
- Navigate to https://app.cobalt.io/settings/api-tokens (sign in to the Cobalt app if needed).
- Enter a name for your token and select Generate New Token.
- In the modal that appears, copy the API token from the Secret Token field. After you close the overlay you won't see the full token again.
Where to find the other values:
- Organization token (optional): Send GET https://api.cobalt.io/orgs with the personal token (Authorization: Bearer, Accept: application/vnd.cobalt.v2+json) and save the token value (resource.token) for your organization from the response.
- Region (optional): Cobalt's public API docs use https://api.cobalt.io; no other region is documented on the fetched pages, so leave empty unless Cobalt gave you a different API host.
Cobalt shows the secret only once, so copy it before you leave the page.
The personal API token acts as the user who created it, so the user must be an organization member. Most API calls are scoped to an organization and need the organization token in the X-Org-Token header. Cobalt does not document a read-only token scope.
Source: docs.cobalt.io, docs.cobalt.io, checked 2026-10-07.
The permissions Safeguard needs:
organization member. -
On Compliance › Connectors, open Cobalt, click Connect, choose API token and fill in:
Field What to enter API token Required. Stored encrypted and never shown again. Organization token (optional) Stored encrypted and never shown again. Region (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Cobalt 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 | CC4.1, CC7.1 | 3 |
| ISO/IEC 27001 | Automated tests | A.8.8 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1), 164.308(a)(8) | 3 |
| PCI DSS | Automated tests | 6.3.3, 11.3.1, 11.4.2, 11.4.3 | 3 |
| NIST CSF 2.0 | Automated tests | ID.IM-02, ID.RA-01, ID.RA-06 | 3 |
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