Spacelift
Connect Spacelift to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Spacelift to collect infrastructure evidence with automated compliance tests, switched on per workspace.
| Category | Infrastructure |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Spacelift's guide | docs.spacelift.io |
Connect with an API token
-
In Spacelift:
- In Spacelift, click your account name in the lower right corner and select Organization settings.
- In the Access section, click API keys, then Create API key.
- Enter a Name, set Type to Secret, and under Space select the root space with reader access (not writer). Leave Groups empty unless you manage access by group.
- Create the key. The API key is generated in a file and automatically downloaded to your device; Spacelift doesn't store the token and it cannot be retrieved or recreated afterwards.
Where to find the other values:
- Instance URL: Your Spacelift account address, https://<account-name>.app.spacelift.io (the GraphQL endpoint is https://<account-name>.app.spacelift.io/graphql).
- API key ID: The api_key_id value in the downloaded file (the secret is api_key_secret).
- Access token (optional): A JWT obtained by exchanging the key ID and secret with the apiKeyUser GraphQL mutation; an alternative to the key ID and secret.
Spacelift shows the secret only once, so copy it before you leave the page.
Reader access on the root space gives read access across all spaces beneath it.
Source: docs.spacelift.io, checked 2026-10-07.
The permissions Safeguard needs:
Read on the root space. -
On Compliance › Connectors, open Spacelift, click Connect, choose API token and fill in:
Field What to enter Instance URL Optional. An address under app.spacelift.io. API key ID Optional. API key secret Optional. Stored encrypted and never shown again. Or, instead: Access token (optional).
-
Click Connect with token.
Frameworks
Safeguard's automated tests read Spacelift 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.2, CC6.3, CC8.1 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.32 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 2 |
| PCI DSS | Automated tests | 6.5.1, 7.2.4, 8.2.5 | 3 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05, PR.PS-01 | 3 |
These tests are switched on per workspace by the Safeguard team.
Related
- 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