SECOPS
Axiom Egress Baseline Breach to PagerDuty Escalation
Runs a scheduled Axiom query over Cloudflare egress logs, detects sources breaching their learned data-out baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires evaluation window
- ActionQuery Axiom for egress bytes per sourceAxiom
- LogicCompute deviation vs trailing baseline
- LogicSuppress known-good, gate on confidence
- ActionOpen PagerDuty incident with evidencePagerDuty
- OutputAnnotate sub-threshold drift back to AxiomAxiom
What it does
Queries Axiom on a schedule for outbound-byte totals per source, compares each against a learned baseline window, and pages an on-call analyst only when a source blows past its threshold with a suspicious destination. Low-confidence drift is logged, not paged.
When to use it
Use it when real-time webhooks are too noisy and you'd rather batch-evaluate egress every few minutes against statistical baselines. Ideal for teams that already centralize Cloudflare logs in Axiom and run on-call through PagerDuty.
How it works
- 1A schedule trigger fires the evaluation window (e.g. every 10 minutes).
- 2An Axiom action runs an aggregation query summing egress bytes per source over the window.
- 3A logic step computes each source's deviation from its trailing baseline and filters to breaches only.
- 4A second logic step suppresses known-good destinations and requires a minimum confidence to escalate.
- 5A PagerDuty action opens an incident for each qualifying source with the query evidence attached.
- 6Sub-threshold drift is written back to Axiom as an annotated event for trend tracking.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.