SECOPS
Dormant-Account Reactivation Watch
Detects when a long-inactive account suddenly authenticates in Axiom, verifies the dormancy window.
How it runs
The automated pipeline, trigger to output.
- TriggerAxiom emits a successful loginAxiom
- ActionLook up account's last prior login
- LogicCheck if dormancy gap exceeds threshold
- ActionGather reactivation context and owner
- ActionEmail manager a verification requestGmail
- OutputLog pending case to Notion registerNotion
What it does
Flags the reactivation of dormant accounts — a classic sign of compromised or orphaned credentials being abused. When an identity with no logins for a defined period suddenly authenticates, the flow confirms the dormancy and asks the owner's manager to verify it was legitimate.
When to use it
Use for environments with service accounts, ex-contractor logins, or seasonal staff where stale credentials are a real risk. Best when Axiom retains enough history to establish last-seen dates per account.
How it works
- 1Axiom emits a successful login event.
- 2The flow looks up that account's most recent prior login to measure the dormancy gap.
- 3A logic step checks whether the gap exceeds the dormancy threshold; active accounts are ignored.
- 4For a reactivation it gathers context — last-seen date, source IP, account type, and owning team.
- 5It emails the account owner's manager a verification request with one-click confirm/deny framing and the event details.
- 6It writes the reactivation and pending verification to a Notion register so unresolved cases stay visible for follow-up.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect GmailRead, draft, send, label.
- 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.