SECOPS
Leaked Secret Scanner: Detect, Rotate, and Page the Owner
Continuously scans public GitHub commits for leaked credentials, and on a verified hit it auto-rotates the exposed key, archives evidence, and pages the owning engineer.
How it runs
The automated pipeline, trigger to output.
- TriggerPublic repo push receivedGitHub
- ActionScan commit diff for secret patterns
- LogicVerify match is a live credential
- ActionRevoke and reissue exposed key
- ActionArchive leak evidence to S3AWS S3
- OutputPage the commit author's on-callPagerDuty
What it does
This workflow watches your public GitHub footprint for accidentally committed secrets (API keys, tokens, cloud credentials), confirms the leak is real, immediately rotates the exposed credential, and pages whoever introduced it so they can react within minutes instead of hours.
When to use it
Run this when your org has public repos and you need a closed-loop response to credential leaks rather than just an alert. It is built for secops teams who want rotation and human escalation to happen automatically, not just a Slack ping that sits unread overnight.
How it works
- 1A GitHub push event arrives for any watched public repo.
- 2The diff is scanned with secret-detection patterns to find candidate credentials in the new commits.
- 3A logic branch verifies the match (entropy and provider-prefix checks) and drops false positives.
- 4For a confirmed live key, an action calls the provider to revoke and reissue the credential.
- 5The leaking commit, file path, and rotation receipt are written to an S3 evidence bucket.
- 6PagerDuty pages the commit author's on-call so a human owns the cleanup.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect AWS S3Buckets, objects, signed URLs.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.