SECOPS
Emergency Rotation When a Secret Leaks to a Public Repo
When a secret is detected in a public or newly-public repository, it escalates as a critical incident: rotates the credential, force-pushes a history scrub, opens a PagerDuty page.
How it runs
The automated pipeline, trigger to output.
- TriggerSecret-scanning alert webhook receivedGitHub
- LogicFilter: repo is public or newly public
- ActionRotate credential and scrub git historyShell
- ActionOpen critical PagerDuty incidentPagerDuty
- OutputCreate Zoom war room and share join linkZoom
What it does
Treats a public-repo leak as the worst-case scenario it is. A secret in a private repo is bad; one in a public repo is being scraped within minutes. This workflow fast-paths the highest-urgency response: rotate the credential, trigger a git history rewrite to remove the secret from the commit log, and immediately convene humans rather than just logging a ticket.
When to use it
Use it for the small set of repos that are public or can flip to public, where exposure time is measured in minutes and you want a coordinated emergency response, not a queued task.
How it works
- 1A secret-scanning alert webhook fires and includes repo visibility.
- 2A filter confirms the repo is public or recently made public; private-repo findings route elsewhere.
- 3A shell step rotates the credential and runs a history-scrub force push to purge the secret.
- 4PagerDuty opens a critical incident for on-call security.
- 5A Zoom war-room meeting is created and its join link is posted as the incident output.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect ZoomMeetings, recordings, transcripts.
- 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
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.