Concord
Connect Concord to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Concord connection as digital signature evidence. Automated collection is not available for this provider yet.
| Category | Digital Signature |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Concord:
- From your Concord account, click the lightning bolt icon (Automations).
- Select Integrations and open the Concord API section.
- Click Generate a new API Key.
- Copy the private API key from the pop-up window; it is displayed only once.
Where to find the other values:
- Base URL (optional): Leave blank for your live Concord account. Concord's sandbox (UAT) environment signs in at
https://uat.concordnow.com/#/login; use the sandbox only for testing.
Concord shows the secret only once, so copy it before you leave the page.
API key generation is only offered on paid Concord plans. If you lose the key you must generate a new one. Concord documents no read-only or scoped API key. The production API base URL is not stated in the fetched help articles.
Source: help.concord.app, help.concord.app, checked 2026-10-07.
-
On Compliance › Connectors, open Concord, 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
Concord 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
- Digital Signature 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