Turbot
Connect Turbot to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Turbot to collect cspm evidence with automated compliance tests, switched on per workspace.
| Category | CSPM |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Turbot's guide | turbot.com |
Connect with an API token
-
In Turbot:
- Sign in to Turbot Guardrails as the user Safeguard will act as.
- Click your username/avatar in the top right to open the User Profile Overview page.
- Select the Access Keys tab and click Create Access Key.
- Copy the access key and the secret key into a secure location now; this is the first and last time the secret is available. Paste them into Safeguard's Access key and Secret key fields.
- Grant that user the Turbot/ReadOnly permission (it allows viewing resource data in the CMDB). Guardrails permissions limit what the API keys can do. The UI click path for granting the permission was not found in the fetched docs.
Where to find the other values:
- Instance URL: Your Guardrails Workspace URL (the CLI docs' example is
https://turbot-customer.cloud.turbot.com); the Guardrails CLI asks for the same Workspace URL with the access key and secret key.
Turbot shows the secret only once, so copy it before you leave the page.
Turbot's public documentation does not cover every step.
Access keys inherit the creating user's Guardrails permissions. Missing: the sourced UI steps to grant Turbot/ReadOnly to a user (Permissions tab labels not fetched). The vendor_doc page (GraphQL controls query) notes control results need Turbot/Metadata permission or above.
Source: turbot.com, turbot.com, turbot.com, checked 2026-10-07.
The permissions Safeguard needs:
Turbot/ReadOnly. -
On Compliance › Connectors, open Turbot, click Connect, choose API token and fill in:
Field What to enter Instance URL Required. For example: https://acme.cloud.turbot.com Access key Required. Stored encrypted and never shown again. Secret key Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Turbot 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 | 1 |
| ISO/IEC 27001 | Automated tests | A.8.9 | 1 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1) | 1 |
| PCI DSS | Automated tests | 2.2.1 | 1 |
| NIST CSF 2.0 | Automated tests | PR.PS-01 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- CSPM 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