Skip to main content

Cotool + Cloudflare

Connect Cloudflare to Cotool so agents investigate HTTP traffic, firewall events, Zero Trust Gateway activity, DNS, zones, and devices, and ingest Cloudflare logs.

Network
Updated

The short answer

Cotool's Cloudflare integration lets agents investigate HTTP traffic, firewall events, Zero Trust Gateway activity, DNS, zones, and devices. Cloudflare logs can also be ingested into Cotool for detections and hunts.[1][2]

How it connects: Cotool calls the Cloudflare API with an API token. Cloudflare tokens carry named permissions, such as Analytics Read or Zero Trust Read, scoped to the accounts and zones you choose.[2][6]

What Cotool uses from Cloudflare

HTTP traffic
Agents query HTTP request data, including filters by client ASN. Cloudflare serves analytics through its GraphQL Analytics API, which has a single endpoint.[1][7]
Firewall events
Agents read WAF and firewall events to see what Cloudflare blocked or challenged for an IP, path, or rule.[1][6]
Zero Trust Gateway
Agents read Gateway activity. Cloudflare logs Gateway DNS, network, and HTTP traffic, and network logs include only TCP connections that were successfully established.[1][8]
DNS, zones, and devices
Agents look up zones, DNS records, and Zero Trust devices to tie traffic back to an asset or a person.[1]

Detections, hunts, and triage

Investigate a suspicious IPTriage
An agent checks which zones the IP hit, what the WAF did with those requests, and whether any Gateway user resolved or reached it, then enriches the IP with threat intel.[1][3]
Hunt across Cloudflare logsHunt
With Cloudflare logs in Cotool, a hunt joins HTTP, firewall, and Gateway events with identity and endpoint logs in one query.[1][4][5]

Setup and permissions

Create an API token with only read permissions, scoped to the accounts and zones agents should see.[6]

PermissionAccess
Analytics ReadRead zone analytics.[6]Read
Firewall Services ReadRead firewall resources.[6]Read
Zero Trust ReadRead Cloudflare Zero Trust resources, including Gateway.[6]Read
Zone ReadRead zone management.[6]Read
DNS ReadRead DNS records.[6]Read
  • Raw logs reach external systems through Logpush, which pushes logs to storage services, SIEMs, and log management providers.[9]
  • Gateway does not log HTTP bodies, except the first 512 bytes of error requests, kept for 30 days for internal troubleshooting.[8]

How Cotool works with Cloudflare

  • Cotool added the Cloudflare integration in release 0.66.0 and managed log ingestion for Cloudflare in release 0.78.0.[1]
  • Cotool keeps an environment map for Cloudflare so agents know your zones and accounts before they query.[1]

FAQ

Does Cotool need write access to Cloudflare?
The investigation capabilities Cotool lists for Cloudflare are reads: traffic, firewall events, Gateway activity, DNS, zones, and devices. Cloudflare's read permissions cover them.[1][6]

Sources

  1. Changelog (Cotool docs) · accessed November 16, 2026
  2. Integrations (Cotool) · accessed November 16, 2026
  3. Respond to every signal (Cotool Respond) · accessed November 16, 2026
  4. SIEM (Cotool) · accessed November 16, 2026
  5. Threat hunting (Cotool Hunt) · accessed November 16, 2026
  6. API token permissions (Cloudflare docs) · accessed November 16, 2026
  7. GraphQL Analytics API (Cloudflare docs) · accessed November 16, 2026
  8. Gateway activity logs (Cloudflare docs) · accessed November 16, 2026
  9. Logpush (Cloudflare docs) · accessed November 16, 2026

Related integrations

All integrations

Use cases with Cloudflare

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo