SECOPS
Hourly WAF block to Honeycomb error-rate correlation
On an hourly schedule, compares Cloudflare WAF block volume against Honeycomb backend error rate for the same paths and flags only the paths where blocked traffic and origin…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule fires
- ActionPull WAF blocks per path from Cloudflare GraphQLCloudflare
- ActionPull error rate per route from HoneycombHoneycomb
- LogicJoin by path; keep routes where blocks and errors both rose
- OutputWrite correlated rows to AxiomAxiom
What it does
Every hour it pulls Cloudflare WAF block counts grouped by path and pulls Honeycomb error rates for the matching service routes, then joins the two. It surfaces only paths where WAF blocks AND origin errors both climbed in the same hour, which is the pattern that suggests an attack is actually degrading the service rather than being cleanly absorbed.
When to use it
Use it as a steady heartbeat when you want correlation, not raw alerts. It separates "WAF is doing its job quietly" from "WAF is busy and the backend is also hurting on the same routes."
How it works
- 1A schedule fires hourly.
- 2An action step queries Cloudflare GraphQL for blocked-request counts per path over the last hour.
- 3An action step queries Honeycomb for error rate per matching route over the same hour.
- 4A logic step joins both datasets by path and keeps only routes where blocks and errors both increased.
- 5The output step writes the correlated rows to Axiom as a structured event for trend dashboards and longer retention.
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 AxiomLog streams, queries, dashboards.
- 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.