SECOPS
Cloudflare WAF Rule Effectiveness Review and Tightening Loop
On a weekly schedule it audits each candidate rule currently running in log-only mode in Cloudflare, measures how cleanly it matched real attacks versus legitimate traffic.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionList log-only rules and match counts in CloudflareCloudflare
- LogicScore each rule's match precision
- ActionRecommend promote / tighten / retireOpenAI
- OutputPost recommendations to Slack for approvalSlack
- ActionApply approved change in CloudflareCloudflare
What it does
It closes the loop on rules that were deployed in observation mode. Rather than letting log-only rules pile up forever, it weekly scores each one's match precision and recommends whether to promote it to active blocking, narrow it, or retire it.
When to use it
When your anomaly-to-rule pipeline produces many log-only candidates and you need a disciplined cadence to graduate the good ones and prune the noisy ones without manual log-spelunking.
How it works
- 1A weekly schedule fires.
- 2List active log-only rules and pull their match counts from Cloudflare.
- 3Logic scores each rule's precision: malicious matches versus likely-legitimate matches.
- 4An LLM step recommends an action per rule — promote to block, tighten the expression, or retire — with reasoning.
- 5Post the per-rule recommendations to Slack with approval buttons.
- 6On approval, apply the chosen change to the rule in Cloudflare.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.