SECOPS
WAF Attack Confirmation and PagerDuty Escalation
When a WAF block spike shows attack signatures and no matching Sentry app errors, this workflow opens a PagerDuty incident with the attacking IPs, targeted rule, and recommended…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule polls Cloudflare for block-volume spikesCloudflare
- LogicMeasure source-IP spread and path diversity
- ActionCheck Sentry for real user errors on same pathsSentry
- LogicConfirm attack profile or stop
- ActionOpen PagerDuty incident with IPs and mitigationPagerDuty
- OutputPost summary to security Slack channelSlack
What it does
Detects when a Cloudflare WAF block spike carries the hallmarks of an active attack — many distinct source IPs, scattered probe paths, and no corresponding Sentry application errors that would indicate the requests came from real users — and escalates it as a PagerDuty incident with the offending IP ranges, the rule that caught them, and a recommended mitigation.
When to use it
Use it for genuine paging: you only want an on-call human woken when the evidence points to a real attack, not a deploy that tripped a rule. The Sentry cross-check is what keeps this from paging on false positives.
How it works
- 1A schedule polls Cloudflare for rules whose block volume spiked in the trailing window.
- 2A logic step measures the source-IP spread and path diversity of the blocked requests.
- 3An action queries Sentry to check whether the same paths produced real user-facing errors.
- 4A logic step confirms the attack profile: high IP spread plus absent Sentry errors equals escalate; otherwise stop.
- 5An action opens a PagerDuty incident with the attacking IPs and mitigation steps.
- 6An action posts the same summary to the security Slack channel for awareness.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect SentryErrors, performance, releases.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.