SECOPS
Privileged-Grant Collusion and Self-Grant Pattern Investigator
An agent investigates suspicious grant patterns — self-grants, reciprocal grant rings, and after-hours elevations — by correlating Axiom logs and GitHub activity.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly scheduled investigation run
- ActionPull and correlate grant events from AxiomAxiom
- ActionCross-reference GitHub permission changesGitHub
- LogicIdentify self-grants, rings, and off-hours clusters
- ActionFile evidence-backed case in NotionNotion
- OutputNotify security lead of top findings in SlackSlack
What it does
It hunts for relationship-level abuse of the grant process that single-event rules miss: people granting themselves privilege, pairs who repeatedly elevate each other, and clusters of off-hours grants. It assembles the evidence into a reviewable case rather than a raw alert.
When to use it
Use this for periodic insider-risk review of how privileged access is being handed out, not just whether a single grant is risky. Best when you need narrative, evidence-linked findings an investigator can act on.
How it works
- 1A weekly schedule starts the investigation run.
- 2The agent pulls the period's grant events from Axiom and correlates grantor-grantee pairs, timing, and self-grants.
- 3It cross-references GitHub org and repo permission changes to catch elevation tied to code-access changes.
- 4It reasons over the combined timeline to identify collusion rings, self-elevation, and anomalous clusters.
- 5It files a structured case in Notion with linked evidence, and pings the security lead in Slack with the top findings.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect NotionPages, databases, comments.
- 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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
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.
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.