Civo
Connect Civo to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Civo to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.
| Category | Cloud Infrastructure |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Civo's guide | civo.com |
Connect with an API token
-
In Civo:
- In the Civo dashboard, go to the Profile/Security section (dashboard.civo.com/security).
- Copy the API key shown for the account (if your account belongs to an Organization, pick the key tied to the right account).
Source: civo.com, checked 2026-10-07.
The permissions Safeguard needs. Civo issues no read-only credential. Safeguard only reads with it, and you can revoke it at any time.
-
On Compliance › Connectors, open Civo, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. Regions (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Civo 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 | CC6.6 | 2 |
| ISO/IEC 27001 | Automated tests | A.8.20 | 2 |
| HIPAA Security Rule | Automated tests | 164.312(e)(1) | 2 |
| PCI DSS | Automated tests | 1.3.1 | 2 |
| NIST CSF 2.0 | Automated tests | PR.IR-01 | 2 |
These tests are switched on per workspace by the Safeguard team.
Related
- Cloud Infrastructure 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