SECOPS
Leaked AWS Key Auto-Deactivation with Audit Logging
When a leaked AWS access key is found in a public repo, it deactivates the IAM key, snapshots affected resources to S3, and writes a structured audit row to Snowflake.
How it runs
The automated pipeline, trigger to output.
- TriggerPublic repo push receivedGitHub
- ActionScan diff for AWS key pairs
- LogicConfirm key belongs to account
- ActionDeactivate the IAM access key
- ActionArchive exposure evidence to S3AWS S3
- OutputWrite audit row to SnowflakeSnowflake
What it does
This workflow handles the specific, high-stakes case of an exposed AWS access key. It deactivates the offending IAM key immediately, captures evidence of what the key could reach, and records a structured audit entry so compliance can prove the leak was contained.
When to use it
Use it when AWS credentials in source control are your top fear. Cloud keys grant broad access, so this template prioritizes instant deactivation and a defensible audit trail over a slower human-in-the-loop path.
How it works
- 1A GitHub push event arrives for a public repo.
- 2The diff is scanned specifically for AWS access-key ID and secret pairs.
- 3A logic step confirms the key prefix and that it belongs to your account.
- 4An action deactivates the IAM access key to cut off access.
- 5Evidence of the exposed scope and commit is archived to S3.
- 6An output appends a structured incident row to Snowflake for audit and reporting.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect AWS S3Buckets, objects, signed URLs.
- 3Connect SnowflakeWarehouses, queries, shares.
- 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.