SECOPS
Daily Auth-Anomaly Digest with Snowflake Enrichment
Runs once a day, pulls the prior 24 hours of Axiom auth anomalies, enriches each with employee and asset context from Snowflake.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule starts digest run
- ActionQuery Axiom for 24h of auth anomaliesAxiom
- ActionEnrich with employee/asset context from SnowflakeSnowflake
- LogicScore and rank by blast radius and confidence
- ActionPublish ranked digest to ConfluenceConfluence
- OutputPost digest summary to Slack for standupSlack
What it does
Produces a single, ranked daily digest of every auth anomaly — impossible travel, MFA skips, failed-login spikes — instead of scattered real-time alerts. Each entry is enriched with who the user is and what they can reach, so the standup can prioritize quickly.
When to use it
Use for teams that triage in a daily review rather than 24/7 paging, or as a companion report alongside real-time pagers. Requires an HR/asset table in Snowflake to join against.
How it works
- 1A daily schedule kicks off the digest run.
- 2The flow queries Axiom for all flagged anomalies in the trailing 24 hours.
- 3It joins each anomaly to Snowflake for employee department, role, and the sensitivity of systems that identity can access.
- 4A logic step scores and ranks anomalies by blast radius and confidence.
- 5It renders a structured digest — top risks first, with evidence links and recommended next steps.
- 6The digest is published as a Confluence page, and a short summary with the page link is posted to Slack ahead of the standup.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.