SECOPS
Human-approval gate for new AdministratorAccess grants
Detects when an IAM principal is granted admin-level access via Axiom logs, holds the grant in a pending state.
How it runs
The automated pipeline, trigger to output.
- TriggerAxiom admin-grant eventAxiom
- LogicConfirm policy is admin-equivalent
- ActionSend Slack approval requestSlack
- LogicBranch on approval / timeout
- ActionRevoke policy if not approvedAWS S3
- OutputPost decision to Slack threadSlack
What it does
When any IAM identity is granted admin-equivalent access, this workflow intercepts the event from Axiom's normalized log stream, opens a time-boxed approval request in Slack with Approve and Revoke buttons, and acts on the human decision. Unanswered requests default to revoke, so a privileged grant never lingers without an owner signing off.
When to use it
Use this when admin grants are rare and always need a named approver — common in regulated environments where SOC 2 or FedRAMP requires that privileged access changes have explicit authorization. It turns an after-the-fact audit finding into a real-time control.
How it works
- 1Axiom emits a parsed event for an admin-level policy attachment and triggers the run.
- 2A logic step confirms the policy is truly admin-equivalent (AdministratorAccess, IAMFullAccess, or a wildcard action).
- 3A Slack interactive message goes to the security approvers channel with grant details and Approve/Revoke buttons.
- 4The decision branches: an approval logs and closes the request; a revoke or timeout calls the IAM API to detach the policy.
- 5The outcome is written back to Slack as a threaded reply for the record.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect AWS S3Buckets, objects, signed URLs.
- 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.