Setup GuideCloudflareIntegrationWAFDNSSetup

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.

SecureSpect Team··7 min read

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

  • Log in to the Cloudflare dashboard.
  • Go to My Profile → API Tokens → Create Token.
  • Click Use Template → Read All Resources (or build a custom token with the permissions below).
  • Minimum required permissions:

    ResourcePermission
    |---|---|
    Zone · ZoneRead
    Zone · WAFRead
    Zone · DNSRead
    Account · Access: Apps and PoliciesRead
    Account · Bot ManagementRead
  • Set Account Resources to your organization account.
  • (Optional) Add IP address filtering to restrict token use to SecureSpect's egress IP range.
  • Click Continue to summary → Create Token and copy the token.
  • Step 2 — Connect in SecureSpect

  • Navigate to Integrations in the SecureSpect sidebar.
  • Find the Cloudflare card and click Connect.
  • Paste your API token and your Account ID (found on the right side of your Cloudflare dashboard home page).
  • Click Verify & Save. SecureSpect will run a test call to confirm the token works.
  • Your first scan runs within 5 minutes. Results appear in Findings filtered by source: Cloudflare.
  • 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
    Each finding links to the exact Cloudflare dashboard page where you can remediate it.

    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.

    Automate your SOC 2 evidence collection

    Connect your AWS and GitHub environments and start collecting audit-ready evidence today. Free to start.

    Start Free →More Articles