SECOPS
Cluster Cloudflare WAF block spikes by rule and ASN
On a scheduled interval, pulls Cloudflare WAF blocked-request events, clusters the spike by firewall rule ID and source ASN.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 minutes
- ActionFetch Cloudflare WAF blocked eventsCloudflare
- LogicCluster by rule ID x ASN, compute deltas
- LogicKeep clusters above spike threshold
- OutputPost ranked triage digest to SlackSlack
What it does
Every 15 minutes it queries Cloudflare's firewall event analytics, groups blocked requests by rule ID crossed with source ASN, and ranks the clusters by volume and acceleration versus the prior window. It then posts a compact, ranked digest to a secops Slack channel — only when a cluster crosses your spike threshold, so the channel stays quiet on normal days.
When to use it
Use it as your always-on first line of WAF triage when you don't want an analyst polling the Cloudflare dashboard. It surfaces "rule X is suddenly firing 40x from ASN Y" before it becomes a page.
How it works
- 1A scheduled trigger fires every 15 minutes.
- 2Cloudflare returns blocked firewall events for the window with rule ID, action, and source ASN.
- 3Logic groups events by rule + ASN and computes each cluster's count and delta versus the previous window.
- 4A threshold filter drops clusters below the spike floor; if none qualify, the run ends silently.
- 5Slack receives a ranked digest of the surviving clusters with counts, deltas, and example paths.
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
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
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.
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.
GitLab Push Secret Detection to Block and History Purge
On a GitLab push that contains a detected secret, it revokes the exposed credential, opens a tracking issue with git-history purge instructions.
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.