SECOPS
Staged WAF Sensitivity Canary with Auto-Revert
Safely raises a Cloudflare WAF rule's sensitivity on a canary slice of traffic, watches false-positive rates.
How it runs
The automated pipeline, trigger to output.
- TriggerManual start with target rule and sensitivity
- ActionApply new sensitivity to canary traffic slice in CloudflareCloudflare
- LogicSample WAF events and compute canary false-positive rate
- LogicCompare canary rate against guardrail threshold
- ActionPromote to full traffic or revert the rule in CloudflareCloudflare
- OutputPost outcome and metrics to SlackSlack
What it does
Progressively tunes a WAF rule the way you'd canary a deploy. It applies a higher sensitivity to a small percentage of traffic, watches the resulting block and false-positive rates for a hold period, and then decides: promote the new setting to all traffic if it stays clean, or revert and alert if benign blocks climb past the threshold.
When to use it
Use it when tightening a rule but you're nervous it will over-block. Canarying the change limits blast radius and gives you data-driven confidence before a full rollout.
How it works
- 1A manual trigger starts a tuning run for a chosen rule and target sensitivity.
- 2The workflow applies the new sensitivity to a canary traffic slice in Cloudflare.
- 3During the hold window it samples WAF events and computes the canary's false-positive rate.
- 4Logic compares the canary rate against the guardrail threshold.
- 5If clean, it promotes the setting to full traffic; if noisy, it reverts the rule.
- 6The outcome and metrics post to Slack for the record.
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.