Logto
Connect Logto to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Logto to collect identity & sso evidence with automated compliance tests, switched on per workspace.
Step-by-step guide: Connect Logto.
| Category | Identity & SSO |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Logto's guide | docs.logto.io |
Connect with an API token
-
In Logto:
- In Logto Console, go to Applications and create a new application of type Machine-to-machine.
- On the role assignment page during creation (or later on the app's detail page), assign the Logto Management API access role, or another M2M role marked with the Logto icon that includes the Logto Management API all permission.
- Open the M2M app's details page and copy the App ID and App Secret.
Where to find the other values:
- Instance URL: For Logto Cloud, https://<tenant-id>.logto.app (the same host as the Management API resource indicator https://<tenant-id>.logto.app/api); for self-hosted Logto, your own Logto address.
- Client ID: The M2M app's details page shows the App ID.
- Tenant ID (optional): The <tenant-id> part of https://<tenant-id>.logto.app.
Source: docs.logto.io, checked 2026-10-07.
The permissions Safeguard needs:
Logto Management API: all (M2M role). Logto issues no read-only credential. Safeguard only reads with it, and you can revoke it at any time. -
On Compliance › Connectors, open Logto, click Connect, choose API token and fill in:
Field What to enter Instance URL Required. For example: https://<tenant-id>.logto.app, or your own Logto address Client ID Required. Client secret Required. Stored encrypted and never shown again. Tenant ID (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Logto 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.1, CC6.3 | 6 |
| ISO/IEC 27001 | Automated tests | A.5.17, A.8.2, A.8.5 | 6 |
| HIPAA Security Rule | Automated tests | 164.308(a)(4), 164.308(a)(5), 164.312(d) | 4 |
| PCI DSS | Automated tests | 7.2.2, 8.3.4, 8.3.6, 8.4.2 | 4 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-03, PR.AA-05 | 4 |
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