Edge-specific evidence
Requests, WAF outcomes, bot behavior, source IPs, Ray IDs, and affected paths stay attached to the incident.
Use case
Connect Cloudflare telemetry, investigation context, and response recommendations for incidents at the edge.
Capabilities
Each use case starts from Cloudflare telemetry and ends with evidence your team can use.
Requests, WAF outcomes, bot behavior, source IPs, Ray IDs, and affected paths stay attached to the incident.
Recommendations can map to practical Cloudflare controls such as blocking abusive traffic or tightening access.
Retained telemetry supports follow-up reviews, recurrence checks, and compliance-oriented exports.
Context
Flarehawk keeps autonomous investigation concrete by connecting AI output to security evidence and reviewable action.
Cloudflare Logpush gives Flarehawk the request and security event history needed to reconstruct edge incidents.
Vigil translates suspicious patterns into a clear response plan your team can review before applying changes.
Every recommended action should remain traceable to the request evidence and behavior that triggered it.
Workflow
The same core loop supports analytics, autonomous investigation, and retention-driven evidence review.
Cloudflare telemetry streams into Flarehawk.
Detections identify suspicious edge, WAF, Zero Trust, or traffic behavior.
Vigil builds the incident narrative and response recommendation.
Your team reviews the affected paths, actors, and Cloudflare context.
Flarehawk monitors for recurrence after the response.
Related
These pages connect the search path from category evaluation to the concrete Flarehawk workflow.
FAQ
The current Cloudflare incident response workflow is built around Logpush telemetry and the evidence it provides.
The default posture is review-first. Flarehawk recommends actions and keeps humans in control of approval.
Start free
Connect a telemetry source free. No credit card, no sales call.