Veza
Connect Veza to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Veza to collect user access review evidence with automated compliance tests, switched on per workspace.
| Category | User Access Review |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Veza's guide | docs.veza.com |
Connect with an API token
-
In Veza:
- Sign in to your Veza instance as a user who can view access reviews.
- Go to Administration › API Keys › Personal › Add New Personal API Key.
- Enter a descriptive name for the key and click Save.
- Copy and save the API key value, which will not be shown again.
Where to find the other values:
- Instance URL: The URL of your Veza instance (VEZA_URL in Veza's examples, such as https://yourcompany.cookiecloud.ai); API calls go to https://<url>/api/v1/.
Veza shows the secret only once, so copy it before you leave the page.
Veza's public documentation does not cover every step.
A personal API key inherits the permissions of the user who created it, and Veza documents no per-key scope picker, so create it from a user whose role can view access reviews (workflows). Which Veza role grants view-only access to access reviews was not confirmed in the fetched pages. Team API keys authenticate as a service account with the oaa_push role for OAA operations only, so they do not suit this use.
Source: docs.veza.com, docs.veza.com, checked 2026-10-07.
The permissions Safeguard needs:
view access reviews. -
On Compliance › Connectors, open Veza, click Connect, choose API token and fill in:
Field What to enter Instance URL Required. An address under vezacloud.com. API key Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Veza 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 | 1 |
| ISO/IEC 27001 | Automated tests | A.5.18 | 1 |
| HIPAA Security Rule | Automated tests | 164.308(a)(4) | 1 |
| PCI DSS | Automated tests | 7.2.4 | 1 |
| NIST CSF 2.0 | Automated tests | PR.AA-05 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- User Access Review 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