SECOPS
Archive revoked IAM grant evidence to S3 for audit
After any IAM grant is revoked, this workflow assembles a tamper-evident evidence bundle, archives it to a write-once S3 bucket.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: grant revocation completedHTTP webhook
- LogicAssemble evidence bundle
- ActionArchive to write-once S3 bucketAWS S3
- ActionCreate Confluence case pageConfluence
- OutputPost case confirmation to SlackSlack
What it does
Whenever an IAM grant is revoked — by automation or a human — this workflow captures the full evidence package: the original grant event, the actor, the revoking decision, approvals, and timestamps. It writes the bundle to a write-once S3 bucket for immutable retention and logs a summary case page in Confluence so auditors can trace every privileged-access action end to end.
When to use it
Use this when you need defensible records of privileged-access changes for SOC 2, ISO 27001, or incident post-mortems. It turns scattered logs into a single auditable artifact per revocation, with the raw evidence preserved and the human-readable summary searchable.
How it works
- 1A webhook fires when a grant revocation completes and triggers the run.
- 2A logic step assembles the evidence bundle from the event, actor, decision, and approval trail.
- 3The bundle is written to a write-once (object-lock) S3 bucket keyed by case ID.
- 4A Confluence page is created summarizing the case with a link to the archived evidence.
- 5A Slack confirmation posts the case ID and archive location for the record.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AWS S3Buckets, objects, signed URLs.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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
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.