How to Connect Cloudflare to SecureSpect (Step-by-Step)
Set up the Cloudflare integration in SecureSpect to automate DNS, WAF, and access-policy evidence collection for SOC 2.
Ready to connect? Follow the steps in SecureSpect — the integration dialog walks you through the same process described here.
Open Integrations →Overview
SecureSpect's Cloudflare integration pulls configuration data from your Cloudflare account using a read-only API token — no write permissions are ever requested. Once connected, SecureSpect continuously checks your WAF rules, access policies, and DNS security settings against SOC 2 Common Criteria.
What Gets Monitored
- WAF rules — Custom rules enabled, OWASP ruleset active, challenge mode configured
- Zero Trust Access policies — Application policies, identity provider connections
- DNS security — DNSSEC enabled, CAA records present
- Bot management — Bot Fight Mode or Super Bot Fight Mode status
- DDoS protection — L7 DDoS managed rulesets
Step 1 — Create a Read-Only API Token
Minimum required permissions:
| Resource | Permission |
| Zone · Zone | Read |
| Zone · WAF | Read |
| Zone · DNS | Read |
| Account · Access: Apps and Policies | Read |
| Account · Bot Management | Read |
Step 2 — Connect in SecureSpect
Step 3 — Review the First Scan Results
After the initial scan, navigate to Integrations → Cloudflare → View Findings. Common first-run findings include:
- WAF managed rules not fully enabled on a zone
- DNSSEC disabled on a domain
- Zero Trust applications without MFA policy
Ongoing Evidence Collection
SecureSpect re-scans Cloudflare every 24 hours and on demand. Evidence snapshots (JSON exports of your WAF config, access policies, and DNS settings) are automatically attached to the relevant SOC 2 controls in your evidence locker.
Troubleshooting
"Invalid API token" error Confirm the token has not expired and that Account Resources include the correct account.
No zones appear after connecting Check that your token's Zone Resources is set to "All zones" or explicitly includes the zones you want monitored.
WAF findings show "N/A"
Your plan may not include WAF. The Cloudflare Free plan does not expose WAF API data — a Pro or Business plan is required.