Amplitude
Connect Amplitude to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Amplitude 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 |
| Amplitude's guide | amplitude.com |
Connect with an API token
-
In Amplitude:
- In Amplitude, open your organization's settings menu and go to Access and SSO Settings › Provisioning Settings.
- Set the Enable SCIM Provisioning toggle to Enabled.
- Click Generate SCIM Key and copy the key right away; this SCIM key is the token you paste into Safeguard.
Where to find the other values:
- Region (optional): Use the region your Amplitude organization lives in: the SCIM API is at
https://core.amplitude.comfor the US andhttps://core.eu.amplitude.comfor the EU.
Amplitude shows the secret only once, so copy it before you leave the page.
"SCIM API (bulk user management) is available on the Enterprise plan." Amplitude shows the SCIM key only when you enable it; if lost, click Regenerate SCIM Key, which takes effect immediately and invalidates the old key (this breaks any IdP SCIM integration already using it). The docs do not name the role needed to open Provisioning Settings. The SCIM key can also create and change users; there is no read-only option.
Source: amplitude.com, amplitude.com, checked 2026-10-07.
The permissions Safeguard needs:
SCIM key. A SCIM token can also create and change users, and Amplitude has no read-only one. Safeguard only reads with it. Needs Amplitude's Enterprise plan. -
On Compliance › Connectors, open Amplitude, click Connect, choose API token and fill in:
Field What to enter SCIM token Required. Stored encrypted and never shown again. Region (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Amplitude 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 | 2 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5 | 2 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 2 |
| PCI DSS | Automated tests | 7.2.4, 8.2.5 | 2 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 2 |
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