SECOPS
MFA-Bypass and New-Geography Triage Agent
An agent that reviews Axiom successful-login events for sessions that skipped MFA or originated from a country the user has never used, gathers context, and decides whether…
How it runs
The automated pipeline, trigger to output.
- TriggerAxiom flags MFA-skip or new-geo loginAxiom
- ActionPull user's historical geo and device baseline
- LogicAgent classifies risk: benign, step-up, escalate
- ActionWrite rationale and evidence for escalations
- ActionOpen Linear issue for high-risk verdictsLinear
- OutputPost verdict to secops Slack threadSlack
What it does
Triages suspicious successful logins where MFA was bypassed or the geography is brand-new for that identity. Instead of a fixed rule, an agent weighs the user's history, the auth method, and the resource accessed, then chooses an action and explains why.
When to use it
Use when raw geo/MFA rules generate too many false positives and you want judgment in the loop. Best for orgs with a real history baseline per user in Axiom.
How it works
- 1Axiom emits successful logins flagged as MFA-skipped or from an unseen country.
- 2The agent pulls the user's historical login geographies and device list for baseline context.
- 3It reasons over the signal: known travel pattern, corporate VPN egress, or genuine anomaly.
- 4A decision branch routes the outcome — benign events are suppressed with a note; medium-risk events trigger a step-up re-auth request; high-risk events escalate.
- 5For escalations the agent writes a plain-language rationale and the supporting evidence.
- 6It opens a Linear issue with the rationale and posts the verdict to the secops Slack thread.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.