HashiCorp Vault
Connect HashiCorp Vault to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect HashiCorp Vault 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 |
| HashiCorp Vault's guide | developer.hashicorp.com |
Connect with an API token
-
In HashiCorp Vault:
- Write a policy file (for example safeguard-read.hcl) that grants only what Safeguard reads: path "sys/audit" { capabilities = ["read", "sudo"] } path "sys/auth" { capabilities = ["read"] } path "identity/mfa/login-enforcement" { capabilities = ["read", "list"] } path "identity/mfa/login-enforcement/*" { capabilities = ["read", "list"] }
- Load it with the Vault CLI: vault policy write safeguard-read safeguard-read.hcl
- Create a token bound to that policy: vault token create -policy=safeguard-read
- Copy the token value from the command output and paste it into Safeguard.
Where to find the other values:
- Server URL: Your Vault server's https address.
- Namespace (optional): Vault Enterprise or HCP Vault only: the namespace path the policy and token were created in.
HashiCorp Vault issues this credential through its API or its support team, not through its admin screens.
Source: developer.hashicorp.com, checked 2026-10-07.
The permissions Safeguard needs:
read + sudo: sys/audit,read: sys/auth,read + list: identity/mfa/login-enforcement. HashiCorp Vault has no narrower grant for these reads. Safeguard only reads with it. -
On Compliance โบ Connectors, open HashiCorp Vault, click Connect, choose API token and fill in:
Field What to enter Server URL Required. Your own server: an https address reachable from the internet. API token Required. Stored encrypted and never shown again. Namespace (optional) โ -
Click Connect with token.
Frameworks
Safeguard's automated tests read HashiCorp Vault 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, CC7.2 | 2 |
| ISO/IEC 27001 | Automated tests | A.8.5, A.8.15 | 2 |
| HIPAA Security Rule | Automated tests | 164.312(b), 164.312(d) | 2 |
| PCI DSS | Automated tests | 8.4.2, 10.2.1 | 2 |
| NIST CSF 2.0 | Automated tests | DE.CM-01, PR.AA-03 | 2 |
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