SECOPS
Agent-driven WAF burst triage and investigation
On a WAF burst, an agent investigates by querying Cloudflare and Honeycomb, forms a hypothesis about the attack type and blast radius.
How it runs
The automated pipeline, trigger to output.
- TriggerCloudflare WAF burst triggers the agentCloudflare
- ActionCharacterize attack signature via Cloudflare GraphQLCloudflare
- ActionInspect traces and error response in HoneycombHoneycomb
- LogicClassify attack type and estimate blast radius
- OutputPublish triage brief to NotionNotion
What it does
When a WAF burst fires, an investigative agent takes over: it queries Cloudflare for the attack signature (rule IDs, paths, methods, geographies) and queries Honeycomb for what reached origin and how the service responded. It reasons about whether this looks like credential stuffing, an L7 flood, a scanner, or a targeted exploit attempt, estimates blast radius, and writes a structured triage brief.
When to use it
Use it when you want a first-pass human-readable investigation done before an engineer even opens the dashboards, especially off-hours when context-gathering is the slow part.
How it works
- 1Cloudflare WAF burst triggers the agent.
- 2The agent calls Cloudflare GraphQL to characterize the attack signature across the burst window.
- 3The agent calls Honeycomb to inspect traces, latency, and error response for the targeted routes.
- 4A logic step has the agent classify the attack type and estimate blast radius from the gathered evidence.
- 5The output step publishes a triage brief to Notion with the hypothesis, evidence links, and recommended next actions.
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 NotionPages, databases, comments.
- 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
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.