Compliance ConnectorsSetup by categoryBusiness Applications
Carta
Connect Carta to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Carta so Griffin AI can search it. This provider does not produce audit evidence.
| Category | Business Applications |
| Connect with | API token |
| What a connection produces | Search only |
Connect with an API token
-
In Carta:
- Sign in to Carta's developer portal at developers.app.carta.com.
- Click Create App.
- Choose the client credentials grant type (for your own Carta account's data) and select only the read scopes you need.
- Click View app details and copy the client_id and client_secret.
Carta's public documentation does not cover every step.
Source: docs.carta.com, docs.carta.com, checked 2026-10-07.
-
On Compliance › Connectors, open Carta, 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
Carta 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
- Business Applications 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