SECOPS
GitHub Push Secret Scan to Auto-Revoke and Page
Watches GitHub push events for committed credentials, immediately revokes the leaked AWS key, and pages on-call with the offending commit and author.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub push receivedGitHub
- LogicScan diff for AWS key pattern
- LogicBranch on high-confidence match
- ActionDeactivate IAM access keyAWS S3
- ActionPage on-call (high urgency)PagerDuty
- OutputPost containment alert to SlackSlack
What it does
Catches secrets the moment they land in a GitHub repo, kills the credential before it can be abused, and gets a human on it. It turns a silent leak into a contained, tracked incident within seconds of the push.
When to use it
Use it on any repo where developers can push directly and a leaked AWS access key would be an emergency. Best paired with GitHub secret scanning push protection as a backstop rather than the only line of defense.
How it works
- 1A GitHub push webhook fires with the new commits and diffs.
- 2A scan step inspects added lines for AWS key patterns (AKIA-prefixed IDs plus a paired secret).
- 3A logic gate decides: if a high-confidence match is found, continue to revocation; otherwise exit quietly.
- 4The matched IAM access key is deactivated through the AWS API so it can no longer authenticate.
- 5PagerDuty raises a high-urgency incident tagged with the repo, commit SHA, and author.
- 6A Slack alert posts to the security channel with a remediation checklist and links back to the commit.
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.
- 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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
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.
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.