SECOPS

Cloudflare WAF False-Positive Triage Agent

Pulls recent WAF-blocked requests from Cloudflare, classifies which look like legitimate traffic caught by mistake.

CategorySecOps
Enginepaperclip
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHourly schedule fires triage pass
  • ActionFetch recent firewall eventsCloudflareCloudflare
  • LogicClassify each block: legit / suspicious / malicious
  • LogicKeep only high-confidence false positives
  • OutputPost ranked triage digest to SlackSlack

What it does

This agent reviews requests your Cloudflare WAF blocked over the last hour and separates real attacks from likely false positives. It looks at the firewall event sample, reasons about each blocked request, and posts a ranked digest so your team only spends attention on the blocks that probably hurt real users.

When to use it

Use it when a managed WAF ruleset is too aggressive and you suspect legitimate API clients, internal tools, or partner integrations are getting 403s. Run it hourly during a tuning period instead of manually scrolling the Cloudflare Security Events log.

How it works

  1. 1A schedule fires every hour to start a triage pass.
  2. 2The agent fetches the latest firewall events from Cloudflare, including the matched rule ID, path, method, and source ASN.
  3. 3It classifies each blocked request as likely-legitimate, suspicious, or clearly-malicious based on path patterns, user agents, and rule behavior.
  4. 4A filter keeps only events scored as likely false positives above a confidence threshold.
  5. 5It groups survivors by triggering rule and writes a ranked digest.
  6. 6The digest posts to a Slack channel with the top offending rules and example requests.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.