SECOPS
Repeat-offender IP auto-block with trace evidence
When a single source IP trips the WAF repeatedly inside a window, adds it to a Cloudflare IP block list and captures the Honeycomb traces it generated as evidence in a Linear…
How it runs
The automated pipeline, trigger to output.
- TriggerCloudflare WAF firewall event keyed by source IPCloudflare
- LogicCount offenses per IP; gate on repeat-offender threshold
- ActionAdd IP to Cloudflare IP Access block listCloudflare
- ActionCapture Honeycomb traces from that IP as evidenceHoneycomb
- OutputFile Linear ticket with block action and trace linksLinear
What it does
It tracks WAF firewall events per source IP and, when one IP crosses a repeat-offense threshold in a short window, programmatically adds that IP to a Cloudflare IP Access (block) list. It then captures the Honeycomb traces tied to that IP's requests as evidence and files a Linear ticket so the action is reviewable and reversible.
When to use it
Use it for fast, defensible containment of obvious single-source abuse where you want the block applied immediately but also want an audit trail and a human review hook.
How it works
- 1Cloudflare WAF firewall events trigger, keyed by source IP.
- 2A logic step counts offenses per IP in the window and gates on the repeat-offender threshold.
- 3An action step adds the IP to a Cloudflare IP Access block list via the API.
- 4An action step pulls the Honeycomb traces generated by that IP during the window for evidence.
- 5The output step opens a Linear ticket containing the block action, offense counts, and trace links for review.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect HoneycombDistributed traces and queries.
- 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.