Skip to content

Cloudflare security analytics without the blind spots

Turn Cloudflare Logpush telemetry into searchable history, real-time detection, and incident context your team can act on.

What Flarehawk gives this workflow

Each use case starts from Cloudflare telemetry and ends with evidence your team can use.

Broad Logpush visibility

Ingest Cloudflare edge, DNS, Zero Trust, audit, email, Workers, and network datasets for search, detection, and incident review.

Detection tuned to edge behavior

Surface suspicious traffic, WAF anomalies, auth abuse, and traffic spikes with context instead of raw alert volume.

Evidence ready for response

Keep the request evidence, affected paths, source IPs, Ray IDs, and rule context close to each incident.

From setup to investigation

The same core loop supports analytics, autonomous investigation, and retention-driven evidence review.

1

Connect Cloudflare Logpush to the Flarehawk ingest endpoint.

2

Flarehawk stores and indexes selected Cloudflare Logpush datasets for investigation.

3

Detection rules and ML-backed analysis identify suspicious behavior.

4

Vigil turns detections into a concise incident narrative.

5

Your team reviews remediation steps and applies the right action.

Use-case questions

Which Cloudflare datasets does this focus on?

The core workflow starts with HTTP request logs and WAF/firewall events, and the ingest catalog also covers DNS, Access, Gateway, audit, Workers, email security, and network datasets.

Is this only for enterprise Cloudflare accounts?

No. Plan fit depends more on accepted data volume, AI cases, retention, and response workflow than company size.