SECOPS
Cloudflare Block-List Expiry and Auto-Unblock Reviewer
Periodically reviews active Cloudflare ASN blocks, checks whether each still shows abusive traffic in Axiom, lifts blocks that have gone quiet.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 6 hours
- ActionList active Cloudflare ASN blocksCloudflare
- ActionRecheck recent activity per blocked ASNAxiom
- LogicDecide lift or keep per ASN
- ActionRemove quiet ASNs from block listCloudflare
- OutputLog decisions to Linear ticketLinear
What it does
Quarantine lists rot if nobody prunes them. This workflow closes the loop on the other templates by reviewing every active Cloudflare ASN block on a schedule. For each blocked network it re-checks recent Axiom data to see whether abusive traffic has stopped. Networks that have gone quiet past a cooldown window get unblocked automatically, while persistent offenders stay blocked. Every keep-or-lift decision is appended to a running Linear ticket for audit.
When to use it
Use this alongside any auto-blocking workflow to prevent permanent collateral damage to shared hosting ASNs and to keep your block list lean. It is the cleanup crew that stops stale rules from silently blackholing legitimate traffic.
How it works
- 1A 6-hour schedule triggers the review.
- 2Cloudflare returns the current list of blocked ASNs and when each was added.
- 3Axiom checks recent request and error activity for each blocked ASN.
- 4A logic step decides lift for ASNs quiet past cooldown, keep otherwise.
- 5Cloudflare removes the lifted ASNs from the block list.
- 6Each decision and its rationale is logged to a Linear ticket.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect AxiomLog streams, queries, dashboards.
- 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.