Incident narratives
Vigil explains what happened, which signals matter, and why the incident deserves attention.
Use case
Turn suspicious activity into an evidence-backed incident narrative with likely impact, affected assets, and recommended response steps.
Capabilities
Each use case starts from Cloudflare telemetry and ends with evidence your team can use.
Vigil explains what happened, which signals matter, and why the incident deserves attention.
Related requests, detections, IP behavior, assets, and timing are grouped into one investigation view.
Each investigation can include practical actions a security or engineering lead can review.
Context
Flarehawk keeps autonomous investigation concrete by connecting AI output to security evidence and reviewable action.
Instead of opening with a raw alert, Flarehawk starts by reconstructing the sequence of suspicious activity.
AI output stays tied to Cloudflare evidence such as paths, IPs, Ray IDs, rule context, and historical baselines.
Recommendations are written for humans to approve, reject, or adapt before changes are made.
Workflow
The same core loop supports analytics, autonomous investigation, and retention-driven evidence review.
Detection logic flags a suspicious behavior pattern.
Vigil gathers related telemetry and asset context.
The investigation explains the timeline, likely intent, and affected surface.
Flarehawk proposes response steps with supporting evidence.
Your team reviews the plan and tracks recurrence.
Related
These pages connect the search path from category evaluation to the concrete Flarehawk workflow.
FAQ
No. Flarehawk speeds up investigation by collecting context and writing the first evidence-backed narrative for review.
Vigil uses detections, Cloudflare event details, asset context, baselines, and related activity stored in Flarehawk.
Start free
Connect a telemetry source free. No credit card, no sales call.