SECOPS
Cloudflare WAF Emergency Block with PagerDuty Escalation and Timed Rollback
On a PagerDuty incident webhook, deploys an emergency Cloudflare WAF block rule, then automatically removes it after a defined TTL unless an on-call engineer confirms it should…
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident webhook with offender detailsPagerDuty
- LogicValidate payload and build scoped block expression
- ActionDeploy emergency WAF block with expiry tagCloudflare
- ActionPost Keep/Let-Expire prompt to on-call SlackSlack
- LogicBranch on Keep vs. TTL expiry, remove rule if expiredCloudflare
- OutputLog action and decision to Axiom incident timelineAxiom
What it does
Lets you respond to an active attack by instantly deploying a Cloudflare WAF block from a PagerDuty incident, while preventing forgotten emergency rules from lingering. The block self-expires after a TTL unless explicitly extended.
When to use it
Use it during live incidents (credential stuffing, L7 floods, malicious IP ranges) when speed matters but you don't want temporary mitigations to become permanent, unreviewed cruft. It pairs fast action with guaranteed cleanup.
How it works
- 1A PagerDuty incident webhook carries the offending IP, ASN, or path pattern in its payload.
- 2The flow validates the payload and constructs a scoped WAF block expression.
- 3It deploys the emergency block rule via the Cloudflare API and tags it with an expiry timestamp.
- 4It posts the active rule and a Keep / Let-Expire prompt to the on-call Slack channel.
- 5A branch waits for the TTL: if the engineer chooses Keep, the rule is promoted to a tracked permanent change; otherwise on expiry the rule is removed via Cloudflare.
- 6The action, decision, and removal are logged to Axiom for the incident timeline.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect AxiomLog streams, queries, dashboards.
- 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
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.