Airbase
Connect Airbase to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Airbase connection as vendor procurement evidence. Automated collection is not available for this provider yet.
| Category | Vendor Procurement |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Airbase, create the credential for API token / Personal access token, read-only where it offers that. Airbase does not publish these steps; its support team can confirm them.
-
On Compliance › Connectors, open Airbase, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
Airbase publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC6.2, CC6.3 | 1 |
| ISO/IEC 27001 | Attestation | A.5.18 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(3) | 1 |
| PCI DSS | Attestation | 7.2.4 | 1 |
| NIST CSF 2.0 | Attestation | PR.AA-05 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- Vendor Procurement 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