SECOPS
Scan GitHub pushes for leaked secrets, then quarantine and rotate
On every push to GitHub, scans the new commits for exposed API keys and tokens. If a real secret is found it opens a tracking issue, revokes the leaked credential.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub push webhook receivedGitHub
- ActionFetch commit diff and scan for secret patternsGitHub
- LogicBranch: verified live secret vs false positive
- ActionRevoke leaked credential at providerShell
- ActionOpen GitHub issue with commit, file, and lineGitHub
- OutputPost severity and remediation status to SlackSlack
What it does
Watches your GitHub repositories for newly pushed commits and inspects the diff for high-entropy strings and known credential patterns (AWS keys, Stripe keys, OpenAI tokens, private keys). When a verified secret is detected, it immediately revokes the leaked key, files a GitHub issue for the audit trail, and alerts the security channel in Slack.
When to use it
Use it as a last line of defense behind pre-commit hooks. Developers forget to install local scanners, and CI-only scanning is too late once code is on the remote. This catches leaks at push time and shuts the credential down before it can be abused.
How it works
- 1A GitHub push webhook fires with the commit range.
- 2The flow fetches the diff for each new commit and runs pattern plus entropy detection.
- 3A logic branch checks whether any match is a live, verifiable secret versus a false positive.
- 4For confirmed leaks, it calls the provider to revoke the key (via a shell rotation step) and opens a GitHub issue capturing the commit SHA, file, and line.
- 5It posts a structured alert to Slack with the severity and remediation status.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 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
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.