SECOPS
Sustained bot surge: escalate to PagerDuty with prepared rule
Escalates only when a Cloudflare bot surge persists past a sustained window, pages the on-call via PagerDuty.
How it runs
The automated pipeline, trigger to output.
- TriggerTight-interval Cloudflare bot metric sampleCloudflare
- LogicSurge sustained past window threshold?
- ActionPull attack signature from CloudflareCloudflare
- LogicBuild candidate block rule + severity score
- ActionCreate PagerDuty incident with prepared rulePagerDuty
- OutputMirror context to Slack for team visibilitySlack
What it does
Distinguishes a brief spike from a sustained attack. It tracks bot-traffic surge duration and only escalates when the surge holds past a configured window. On escalation it pages on-call via PagerDuty and attaches a ready-to-apply Cloudflare block rule and runbook.
When to use it
Use this when you want to avoid alert fatigue from short, self-resolving spikes but still guarantee a human is paged for a real attack. It's the heavier-weight sibling to the Slack proposers — reserved for incidents that warrant waking someone up.
How it works
- 1A schedule samples Cloudflare bot-traffic metrics on a tight interval.
- 2A logic step maintains a sustained-surge counter; the flow only proceeds once the surge has persisted across enough consecutive samples.
- 3An action pulls the attack signature (top paths, ASNs, geographies) from Cloudflare.
- 4A logic step assembles a candidate block/JS-challenge rule and a severity score.
- 5An action creates a PagerDuty incident with the evidence and prepared rule.
- 6A final output drops the same context into Slack so the wider team has visibility while the page is handled.
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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
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.
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.