SECOPS
GitHub Push Secret Scanner with Auto-Quarantine and Rotation
Scans every push for committed credentials, force-quarantines the offending commit to a locked branch, fires a rotation webhook for the exposed key.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub push event receivedGitHub
- LogicScan added lines for secret signatures and high entropy
- ActionMove offending commit to locked quarantine branchGitHub
- ActionFire rotation webhook for exposed credentialHTTP webhook
- OutputOpen Linear evidence ticket with redacted matchLinear
What it does
When a developer pushes to GitHub, this workflow inspects the diff for live secrets (API tokens, private keys, connection strings). If it finds one, it isolates the bad commit on a `quarantine/*` branch, kicks off credential rotation through your secrets webhook, and files a Linear ticket so the incident has a paper trail.
When to use it
Run this on any repo where a leaked key reaches production fast. It is the front-line control for teams that can't wait for nightly scans and need the secret invalidated within minutes of the push.
How it works
- 1A GitHub push event fires the workflow with the commit SHAs and diff.
- 2A logic step pattern-matches the added lines against known secret signatures and entropy thresholds.
- 3If clean, the run ends. If a secret is found, an action creates a locked `quarantine/<sha>` branch holding the commit out of the default branch's reach.
- 4An HTTP webhook call hands the secret fingerprint to your rotation service to revoke and reissue the key.
- 5A Linear issue is opened with the file path, redacted match, and rotation status as the evidence record.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.