SECOPS
WAF False-Positive Spike Detector
Monitors Cloudflare block rates on a short interval, and when blocks against known-good paths spike past a threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerShort-interval schedule polls
- ActionFetch recent block counts by rule/pathCloudflare
- LogicDetect spike vs known-good baseline
- ActionPage on-call via PagerDutyPagerDuty
- OutputPost offending rule + samples to SlackSlack
What it does
This pipeline watches for sudden surges in WAF blocks that hit paths you've marked as legitimate, the classic signature of a managed-ruleset update gone wrong. When the rate crosses a threshold it pages on-call immediately so a bad rule doesn't quietly break production traffic.
When to use it
Use it as a safety net after Cloudflare pushes managed-rule updates, or anytime a deploy could trip the WAF. It catches the "we just started 403ing all our own API calls" incident in minutes instead of waiting for customer complaints.
How it works
- 1A schedule polls every few minutes.
- 2It fetches recent block counts from Cloudflare grouped by rule and path.
- 3A threshold check compares blocks against an allowlist of known-good paths to the recent baseline.
- 4If no anomalous spike, the run exits quietly.
- 5On a spike, it pages on-call through PagerDuty with the rule ID and affected paths.
- 6It also posts the offending rule and sample blocked requests to Slack for fast diagnosis.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.