Airbyte
Connect Airbyte to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Airbyte 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 |
| Airbyte's guide | reference.airbyte.com |
Connect with an API token
-
In Airbyte:
- Sign in to Airbyte as a user with the Organization Admin role (only an Organization Admin can list all users in the organization; Airbyte recommends a service account rather than a personal user).
- Open your profile and select User settings › Applications.
- Click Create an application, give it a descriptive name and click Submit.
- Copy the Client ID, then click the icon to expose the Client Secret and copy it.
- Optional: click Generate access token and Copy (or Download access token) if you want to paste a token as well; it expires in 15 minutes, so Safeguard should rely on the client ID and secret.
Where to find the other values:
- Client ID: User settings › Applications shows the application's Client ID.
- Client secret: User settings › Applications: click the icon next to the secret to expose it.
- Access token (optional): User settings › Applications › Generate access token (valid 15 minutes).
Airbyte's public documentation does not cover every step.
Not sourced: where Airbyte Cloud (cloud.airbyte.com) shows the Organization ID in the UI. Airbyte docs that mention copying the ID from an /organizations/<organization_id> URL refer to the separate Airbyte AI agents app (app.airbyte.ai), so they were not used. The docs do not say whether the client secret can be re-exposed later. Access tokens expire in 15 minutes per the current page (an older search snippet said 3 minutes).
Source: docs.airbyte.com, reference.airbyte.com, checked 2026-10-07.
The permissions Safeguard needs:
Organization Admin. Airbyte shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it. -
On Compliance › Connectors, open Airbyte, click Connect, choose API token and fill in:
Field What to enter Organization ID Optional. Client ID Optional. Client secret Optional. Stored encrypted and never shown again. Or, instead: Access token (optional).
-
Click Connect with token.
Frameworks
Safeguard's automated tests read Airbyte 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