Building an evidence-grounded agentic security operations harness on Cloudflare
Cloudflare describes its Managed Defense AI agent harness, built to help analysts handle the "alert paradox"—a single alert can cause a spike across the environment, and simultaneous alerts can overwhelm even seasoned analysts. The post explains why a single general-purpose agent failed in their first prototype: context became authority (a detection is a hypothesis, not proof), scope drifted (a prompt isn't a boundary), and failure disappeared (timeouts couldn't distinguish "not checked" from "checked and not found"). The redesign moves evidence collection and scope enforcement into deterministic application code before any model runs: fixed, versioned reconnaissance workflows collect identity, detection history, traffic baseline, enforcement outcome, and network observations, each stored with source, version, and timestamp, making evaluation reproducible. Noise is filtered early—Clef, Cloudflare's open-source decision model running on Workers AI, scores alerts against recon data, and high-likelihood false positives skip specialist analysis. For deeper review, a coordinator agent runs four specialists in parallel (traffic analysis, customer context, global telemetry, threat intelligence), with a synthesis agent combining typed findings without fetching new evidence. Global telemetry uses only aggregates to preserve customer privacy. History is treated as evidence, and related alerts are aggregated into consolidated cases. Before analysis, the system builds a versioned evidence package; specialists must cite items in it, and application code validates every citation. Clef scores evidence sufficiency and picks from a reduced list of classifications. The platform stack uses Workers, Workflows, D1, R2, Durable Objects with Flue, and AI Search. The post details how incomplete evidence is handled with three distinct states (not checked, checked with no match, checked with supporting absence), how advisories lead to concrete remediations like rate limiting or WAF rules, and that analysts remain responsible for decisions. It closes with plans for a Custom Managed tier and continuous agents that surface patterns fixed rules miss, plus availability of the early beta.
Comments
Post a Comment