SECOPS
Cloudflare WAF False-Positive Triage with Slack Approval
Watches Cloudflare WAF block events for legitimate traffic that tripped a managed rule, drafts a proposed exception.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 30 min, pull recent WAF firewall eventsCloudflare
- LogicCluster blocks by rule ID and score false-positive likelihood
- ActionDraft scoped exception proposal per high-confidence cluster
- OutputPost proposal to Slack with approve/reject buttonsSlack
- ActionOn approval, apply scoped exception to CloudflareCloudflare
What it does
Scans recent Cloudflare WAF firewall events, isolates blocks that look like false positives (known-good user agents, internal IP ranges, expected API paths), and turns each cluster into a concrete proposed rule change — a skip rule, a custom exception, or a sensitivity drop on a specific managed rule ID. Nothing is applied automatically; every proposal lands in Slack with the evidence and an Approve / Reject control.
When to use it
Run it when a newly deployed managed ruleset starts blocking real customers and your team is drowning in "why am I blocked" tickets. It keeps a human in the loop so you tune away noise without silently widening your attack surface.
How it works
- 1A schedule fires every 30 minutes and pulls Cloudflare firewall events for the trailing window.
- 2Logic groups blocks by rule ID and source signature, scoring each cluster for false-positive likelihood.
- 3Clusters above the confidence threshold become drafted exception proposals with sample requests attached.
- 4Each proposal posts to a Slack secops channel with approve/reject buttons.
- 5On approval, the workflow writes the scoped exception back to Cloudflare via the API.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.