SECOPS
Axiom WAF anomaly to Honeycomb RCA thread
When an Axiom monitor detects an anomalous WAF block pattern, fetches the matching Honeycomb traces and opens a structured root-cause analysis thread in Slack with the timeline…
How it runs
The automated pipeline, trigger to output.
- TriggerAxiom WAF anomaly alert hits webhookHTTP webhook
- ActionQuery Axiom for surrounding log contextAxiom
- ActionFetch matching Honeycomb traces for the windowHoneycomb
- LogicAssemble timeline correlating anomaly with traces
- OutputOpen prefilled RCA thread in SlackSlack
What it does
It listens for an Axiom anomaly alert on ingested WAF logs (for example, an unusual block rate on a normally quiet endpoint), then pulls the corresponding Honeycomb traces for that endpoint and window. It assembles a timeline and opens a dedicated root-cause analysis thread in Slack so responders start from shared, prefilled evidence instead of a blank channel.
When to use it
Use it when your WAF logs already flow into Axiom for detection and you want anomalies to spin up a structured investigation surface automatically.
How it works
- 1An Axiom monitor fires on an anomalous WAF block pattern and posts to the webhook trigger.
- 2An action step queries Axiom for the surrounding log context and the affected endpoint and window.
- 3An action step fetches the matching Honeycomb traces for that endpoint over the anomaly window.
- 4A logic step assembles a timeline correlating the WAF anomaly with the trace events.
- 5The output step opens an RCA thread in Slack prefilled with the timeline, trace links, and an owner prompt.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect HoneycombDistributed traces and queries.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 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.