Hevo Data
Connect Hevo Data to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Hevo Data to collect data export evidence with automated compliance tests, switched on per workspace.
| Category | Data Export |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Hevo Data's guide | api-docs.hevodata.com |
Connect with an API token
-
In Hevo Data:
- Sign in to Hevo as a user with the Owner role (only owners can generate API credentials).
- Open the API Keys page for your region, for example
https://us.hevodata.com/account/api-keys(US east),https://us2.hevodata.com/account/api-keys(US west),https://eu.hevodata.com/account/api-keys,https://in.hevodata.com/account/api-keys,https://asia.hevodata.com/account/api-keysorhttps://au.hevodata.com/account/api-keys. - Click GENERATE NEW API KEY.
- Click DOWNLOAD to save the access key and secret key as a JSON file, then paste both into Safeguard.
Where to find the other values:
- Region: The subdomain of the Hevo URL you sign in to:
asia,au,eu,in,us(US east) orus2(US west).
Hevo Data shows the secret only once, so copy it before you leave the page.
"Hevo does not store the API secret key due to security reasons." Hevo documents no read-only or scoped API key; the credentials are valid for all APIs. They are used as HTTP Basic auth (access key as username, secret as password).
Source: api-docs.hevodata.com, api-docs.hevodata.com, checked 2026-10-07.
-
On Compliance › Connectors, open Hevo Data, click Connect, choose API token and fill in:
Field What to enter Access key Required. Stored encrypted and never shown again. Secret key Required. Stored encrypted and never shown again. Region Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Hevo Data 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 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 3 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5 | 3 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 3 |
These tests are switched on per workspace by the Safeguard team.
Related
- Data Export 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