SECOPS
Cloudflare WAF Rule Spike Triage with Sentry Correlation
When a Cloudflare WAF rule's block rate spikes, this workflow pulls the matching app errors from Sentry to decide if it's a real attack or a false positive.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery few minutes, scan WAF rule block countsCloudflare
- LogicKeep only rules exceeding spike threshold vs baseline
- ActionQuery Sentry errors for the spiking rule's pathsSentry
- LogicClassify as attack vs false positive from combined signals
- OutputPost verdict with evidence to SlackSlack
What it does
Watches your Cloudflare WAF for any managed or custom rule whose block count jumps sharply over a short window. When a spike fires, it correlates the blocked request paths and timing against Sentry application errors for the same window, then classifies the spike as a likely attack or a likely false positive and posts an evidence-backed verdict to Slack.
When to use it
Run this when WAF rule changes or traffic shifts keep generating block-rate noise and your team can't tell legitimate customer traffic from probes by eye. It removes the manual cross-referencing between the Cloudflare dashboard and Sentry.
How it works
- 1A schedule fires every few minutes and queries Cloudflare for per-rule block counts over the trailing window.
- 2A logic step compares each rule against its baseline and keeps only rules whose block rate exceeds the spike threshold.
- 3For each spiking rule, an action pulls the affected URIs and queries Sentry for errors on those same paths in the same window.
- 4A logic step weighs the signals: many distinct source IPs with no matching Sentry errors leans attack; few IPs hitting a real endpoint with 5xx errors leans false positive.
- 5The verdict, top blocked paths, and Sentry links post to a Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect SentryErrors, performance, releases.
- 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.