SECOPS
Recommend ASN blocklist additions from sustained WAF abuse
Hourly, it tracks which source ASNs are responsible for sustained WAF blocks across multiple rules.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule
- ActionFetch Cloudflare blocks grouped by ASNCloudflare
- LogicUpdate rolling per-ASN abuse score
- LogicFilter ASNs above persistence and breadth thresholds
- OutputPost blocklist candidates to SlackSlack
What it does
It watches Cloudflare WAF blocks hour over hour and accumulates per-ASN abuse: how many distinct rules an ASN trips, total block volume, and how many consecutive windows it has stayed hot. When an ASN shows sustained, broad abuse — not a one-off burst — it surfaces that ASN as a blocklist candidate in Slack, with the traffic profile an operator needs to decide whether to add a network-level block.
When to use it
Use it to graduate from per-rule whack-a-mole to network-level decisions. It catches noisy bad-actor ASNs that quietly probe many rules instead of hammering one.
How it works
- 1An hourly scheduled trigger fires.
- 2Cloudflare returns the window's blocked events grouped by ASN.
- 3Logic updates a rolling per-ASN abuse score across rules and consecutive windows.
- 4A filter keeps only ASNs above the persistence and breadth thresholds.
- 5Slack receives a blocklist-candidate recommendation with each ASN's profile and a one-click rationale.
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.