Cloudflare Access
Connect Cloudflare Access to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Cloudflare Access 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 |
| Cloudflare Access's guide | developers.cloudflare.com |
Connect with an API token
-
In Cloudflare Access:
- In the Cloudflare dashboard, go to Manage Account › API Tokens (account token) or My Profile › API Tokens (user token).
- Select Create Token and choose to create a custom token.
- Name the token (for example Safeguard Access read-only).
- Under permissions, choose the Account permission group and add Access: Audit Logs Read and Access: Apps and Policies Read.
- Under resources, select only the account you want Safeguard to read.
- Optionally set Client IP Address Filtering and TTL (time to live).
- Select Continue to summary, review, then select Create Token.
- Copy the token secret now; it is shown only once.
Where to find the other values:
- Account ID: On Account home, select Search (or press CMD/CTRL + K), enter Copy account ID and select the result. It is also in Workers & Pages › Account Details next to Account ID, and in the API section at the bottom of any domain's Overview page.
Cloudflare Access shows the secret only once, so copy it before you leave the page.
Access: Audit Logs Read grants read access to Access authentication logs; Access: Apps and Policies Read grants read access to Access applications and policies.
Source: developers.cloudflare.com, developers.cloudflare.com, developers.cloudflare.com, checked 2026-10-07.
The permissions Safeguard needs:
Access: Audit Logs Read,Access: Apps and Policies Read. -
On Compliance › Connectors, open Cloudflare Access, click Connect, choose API token and fill in:
Field What to enter API token Required. Stored encrypted and never shown again. Account ID Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Cloudflare Access 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 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.5 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.312(d) | 3 |
| PCI DSS | Automated tests | 7.2.4, 8.2.5, 8.4.2 | 3 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-03, PR.AA-05 | 3 |
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