SECOPS
WAF burst origin-impact PagerDuty escalation
On a WAF block burst, checks Honeycomb for elevated p95 latency or 5xx on the targeted service and pages on-call via PagerDuty only when origin impact is confirmed.
How it runs
The automated pipeline, trigger to output.
- TriggerCloudflare WAF burst detectedCloudflare
- ActionQuery Honeycomb for p95 latency and 5xx on target serviceHoneycomb
- LogicBranch on confirmed origin impact vs clean absorption
- ActionOpen PagerDuty incident with trace link on impactPagerDuty
- OutputRecord decision and no-page cases to AxiomAxiom
What it does
A WAF burst alone is rarely page-worthy, but a WAF burst that is also slowing or erroring the backend is. This workflow takes the burst signal, asks Honeycomb whether the targeted service is showing elevated p95 latency or a 5xx jump, and escalates to PagerDuty only when origin impact is confirmed. Clean bursts are logged instead of paged.
When to use it
Use it to cut alert fatigue on the WAF channel while guaranteeing a real page when an attack is breaking through and hurting users.
How it works
- 1Cloudflare WAF firewall events trigger and a burst is detected.
- 2An action step queries Honeycomb for p95 latency and 5xx rate on the targeted service during the burst window.
- 3A logic step branches: confirmed origin impact versus clean absorption.
- 4On confirmed impact, an action step opens a PagerDuty incident with the burst stats and a Honeycomb trace link embedded.
- 5The output step records the decision and the no-page cases to Axiom for audit.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect HoneycombDistributed traces and queries.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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
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.