SECOPS
Quarantine and Rotate a Leaked AWS Access Key
On a secret-scan finding for an AWS access key, it immediately deactivates the exposed key in IAM, provisions a fresh key pair, stores it in the secret manager.
How it runs
The automated pipeline, trigger to output.
- TriggerSecret-scan finding webhook receivedGitHub
- LogicFilter: AWS access key, resolve IAM user
- ActionDeactivate leaked key, mint new key pairShell
- ActionStore new key in secret managerAWS S3
- OutputNotify owning team in Microsoft TeamsMicrosoft Teams
What it does
Contains the most time-sensitive secret leak there is: a live AWS access key. The workflow does not wait for human judgment on the dangerous first move. It deactivates the exposed key right away to stop the bleeding, then issues a replacement and hands it to the team that owns the affected repo so they can finish wiring it in.
When to use it
Use it when AWS access keys appear in your codebase risk model and you want deactivation to happen in seconds, not after a ticket gets picked up. Pair it with least-privilege IAM users so quarantine is safe to automate.
How it works
- 1A secret-scanning webhook fires with an AWS access key finding.
- 2A filter confirms the credential type is an AWS access key and resolves the IAM user.
- 3A shell step calls the AWS CLI to set the leaked key to inactive, then creates a new key pair.
- 4The new key is written into the secret manager keyed to the repo and environment.
- 5A Microsoft Teams message alerts the owning team with the quarantined key id and next steps.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect AWS S3Buckets, objects, signed URLs.
- 4Connect Microsoft TeamsChannels, chats, files.
- 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.