1Password
Connect 1Password to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect 1Password to collect identity & sso evidence with automated compliance tests, switched on per workspace.
| Category | Identity & SSO |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
Connect with an API token
-
In 1Password:
- Use the bearer token you saved when you set up the 1Password SCIM bridge.
- If you no longer have it, sign in to 1Password.com and select Integrations in the sidebar.
- Select Automated User Provisioning, then select Regenerate Credentials.
- Save the new bearer token, update the
scimsessionfile in your SCIM bridge deployment, and update the bearer token in your identity provider's settings.
Where to find the other values:
- SCIM bridge URL: In 1Password.com, select Integrations › Automated User Provisioning, then select Manage in the Health Monitoring section; the SCIM bridge address field shows it.
1Password's public documentation does not cover every step.
Requires 1Password Business with a self-hosted SCIM bridge. 1Password issues one bearer token per bridge; regenerating it breaks the existing identity-provider connection until the IdP is updated with the new token. The docs do not state whether the token is shown only once. The SCIM bridge token is not a read-only credential.
Source: support.1password.com, checked 2026-10-07.
-
On Compliance › Connectors, open 1Password, click Connect, choose API token and fill in:
Field What to enter SCIM bridge URL Required. The address of your 1Password SCIM bridge (1Password Business). It must be https on the standard port. SCIM bridge bearer token Required. The bearer token shown when the SCIM bridge was set up (Integrations → your bridge). Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read 1Password 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
- Identity & SSO 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