Duo Security
Connect Duo Security to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Duo Security 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 |
| Duo Security's guide | duo.com |
Connect with an API token
-
In Duo Security:
- Sign in to the Duo Admin Panel as an administrator with the Owner role.
- Go to Applications › Application Catalog, search for Admin API, and click + Add.
- On the new application's page, select only Grant resource - Read and Grant administrators - Read (leave write, settings and other grants unselected), then save the application.
- Copy the Integration key, Secret key and API hostname shown on the application's page.
Where to find the other values:
- Integration key: The Admin API application's page in the Duo Admin Panel shows the Integration key.
- Host: The Admin API application's page shows the API hostname (api-xxxxxxxx.duosecurity.com).
Only Owner-role administrators can create or modify an Admin API application. Duo says to treat the secret key like a password. The exact label of the save button was not confirmed on the fetched page, and the page did not state whether the secret key is shown only once.
Source: duo.com, checked 2026-10-07.
The permissions Safeguard needs:
Grant resource - Read,Grant administrators - Read. -
On Compliance › Connectors, open Duo Security, click Connect, choose API token and fill in:
Field What to enter Integration key Required. Secret key Required. Stored encrypted and never shown again. Host Required. For example: api-xxxxxxxx.duosecurity.com -
Click Connect with token.
Frameworks
Safeguard's automated tests read Duo Security 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.2, CC6.3 | 6 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.17, A.5.18, A.6.5, A.8.2, A.8.5 | 6 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.312(d) | 6 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5, 8.2.6, 8.4.2 | 6 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-03, PR.AA-05 | 6 |
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