Fivetran
Connect Fivetran to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Fivetran 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 |
| Fivetran's guide | fivetran.com |
Connect with an API token
-
In Fivetran:
- Sign in to Fivetran as a user with the Account Administrator role (a scoped API key inherits that user's RBAC permissions).
- Click your username, then click API Key.
- Click Generate API key (or Generate new API key if one already exists).
- Copy the API key and the API secret before you close or leave the page.
- Alternative (Private Preview): to avoid tying the key to a person, go to Users & Permissions, select the API Key tab, click + Add API key, select a service user with the Account Administrator role (or click + Add new service user), set the Key expiration (1 to 365 days), and copy the API Key and API Secret.
Fivetran shows the secret only once, so copy it before you leave the page.
The key and secret disappear once you close the page; the service-account dashboard "won't show the API key, API secret, or Base64-encoded API key again after you reload the page." Clicking Generate new secret replaces the secret immediately and breaks the old pair. Managing service account keys needs the Account Administrator role or the Security Manage permission, and that feature is marked Private Preview.
Source: fivetran.com, fivetran.com, fivetran.com, checked 2026-10-07.
The permissions Safeguard needs:
Account Administrator. Fivetran shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it. -
On Compliance › Connectors, open Fivetran, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. API secret Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Fivetran 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