SECOPS
Cloudflare Bot ASN Anomaly Hunter with Auto-Quarantine
Scans Cloudflare access logs every 10 minutes for ASNs generating abnormal request volume or error rates, blocks the worst offenders via a firewall rule.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 10 minutes
- ActionQuery per-ASN request and error ratesAxiom
- LogicFlag ASNs exceeding baseline
- ActionAdd offender ASNs to Cloudflare block listCloudflare
- OutputOpen Linear evidence ticketLinear
What it does
This workflow continuously hunts for malicious bot traffic in your Cloudflare logs. It pulls recent HTTP events from Axiom, groups them by source ASN, and flags any network whose request rate or 4xx/5xx ratio spikes far above its own rolling baseline. Confirmed offenders get dropped into a Cloudflare IP-list block rule automatically, and a Linear ticket is filed so a human can review the evidence and decide whether to keep or lift the block.
When to use it
Run this when you are getting hammered by credential-stuffing, scraping, or layer-7 floods that rotate IPs but stay within a handful of hosting ASNs. It is built for teams who want fast, evidence-backed mitigation without paging a human for every blip.
How it works
- 1A 10-minute schedule fires the hunt.
- 2Axiom runs a grouped query over the last hour of Cloudflare logs, returning per-ASN request counts and error ratios.
- 3A logic step compares each ASN to its 7-day baseline and keeps only those exceeding the anomaly threshold.
- 4For each flagged ASN, Cloudflare adds it to the managed block list.
- 5A Linear issue is opened with the ASN, sample paths, and the exact Axiom query as evidence.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.