SECOPS
Daily Geo-Anomaly Login Digest
Once a day, summarizes all geo-velocity and new-location login anomalies from the prior 24 hours into a ranked digest and delivers it to the security team via Slack and Notion.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule for the prior 24-hour window
- ActionQuery all flagged anomaly events from AxiomAxiom
- LogicGroup by user, rank by severity, compute trends
- ActionPost the morning briefing to SlackSlack
- OutputAppend dated digest page to Notion historyNotion
What it does
This workflow rolls up every login anomaly detected over the last day — impossible-travel pairs, new-country first-seens, and high-velocity sessions — into a single ranked digest. It turns a stream of individual alerts into a readable daily briefing the security team can review over coffee.
When to use it
Use it alongside real-time alerting to catch the medium-risk events that did not warrant a page but still deserve a look. It is the steady-state situational-awareness layer for teams that do not want to live inside their SIEM.
How it works
- 1A daily schedule triggers the digest run for the previous 24-hour window.
- 2An Axiom query returns all flagged anomaly events with their risk scores and geographies.
- 3A logic step groups events by user, ranks by severity, and computes day-over-day trend counts.
- 4The formatted digest is posted to the security Slack channel as the morning briefing.
- 5The same digest is appended as a dated page in a Notion database to build a searchable historical record.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.