Terraform Cloud
Connect Terraform Cloud to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Terraform Cloud 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 |
Connect with an API token
-
In Terraform Cloud:
- Team token (recommended, least privilege): in HCP Terraform go to Organization Settings › API Tokens and open the Team Tokens tab to create a new team token, for a team that has only read permissions.
- Copy the token now. HCP Terraform displays API tokens only once when you create them; they are obfuscated afterwards and must be regenerated if lost.
- Alternative: an organization owner can use Organization settings › API Token under the Organization Tokens header. Each organization has only one valid organization token, and it can perform CRUD on most resources, so prefer a read-only team token.
Where to find the other values:
- HCP Terraform host: If your URL includes
portal.cloud.eu.hashicorporapp.eu.terraform.io, your organization is in HCP Europe (host app.eu.terraform.io).
Terraform Cloud shows the secret only once, so copy it before you leave the page.
Terraform Cloud's public documentation does not cover every step.
Source: developer.hashicorp.com, checked 2026-10-07.
-
On Compliance › Connectors, open Terraform Cloud, click Connect, choose API token and fill in:
Field What to enter Organization or team API token Required. Create under Organization settings → API tokens. HCP Terraform has no OAuth sign-in for integrations. Stored encrypted and never shown again. Organization name Required. HCP Terraform host Optional. app.terraform.io, or app.eu.terraform.io for HCP Europe. Self-hosted Terraform Enterprise is not supported. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Terraform Cloud 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.1, CC6.2, CC6.3, CC8.1 | 5 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2, A.8.5, A.8.32 | 5 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.312(d) | 4 |
| PCI DSS | Automated tests | 6.5.1, 7.2.2, 7.2.4, 8.2.5, 8.4.2 | 5 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-03, PR.AA-05, PR.PS-01 | 5 |
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