Cohere
Connect Cohere to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Cohere to record its access review and data terms as attested evidence. Cohere offers no admin API for automated tests.
| Category | Business Applications |
| Connect with | API token |
| What a connection produces | Attested evidence |
Connect with an API token
-
In Cohere:
- Sign in to the Cohere dashboard and open the API Keys page.
- To get a production key, an organization Owner completes the Go to Production form for the team.
- Generate the production key and copy it right away; production keys are only viewable in full when they are created.
Cohere shows the secret only once, so copy it before you leave the page.
Cohere's public documentation does not cover every step.
Source: docs.cohere.com, docs.cohere.com, docs.cohere.com, checked 2026-10-07.
-
On Compliance › Connectors, open Cohere, 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
Cohere 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 | C1.2, CC6.2, CC6.3, CC6.5 | 2 |
| ISO/IEC 27001 | Attestation | A.5.18, A.5.34, A.8.10 | 2 |
| HIPAA Security Rule | Attestation | 164.308(a)(3) | 1 |
| PCI DSS | Attestation | 7.2.4 | 1 |
| NIST CSF 2.0 | Attestation | GV.OC-03, PR.AA-05 | 2 |
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