SECOPS
Forked-Repo and Gist Leak Watch with Escalation
Monitors forks and public gists of your repositories for secrets that may have been re-exposed outside your control, and escalates confirmed leaks to PagerDuty.
How it runs
The automated pipeline, trigger to output.
- TriggerNew fork or public gist detectedGitHub
- ActionFetch fork or gist contentsGitHub
- ActionScan content for org credentials
- LogicCheck if matched key is still live
- OutputEscalate live leak to PagerDutyPagerDuty
What it does
This workflow tracks the forks and public gists derived from your repositories, scans them for credentials that match your org's key formats, and escalates any confirmed exposure that lives outside your direct control to PagerDuty.
When to use it
Use it when secrets are dangerous even after you clean your own repo, because a fork or gist can keep an exposed key alive. Security teams use it to close the long-tail of leaks that a single-repo scanner never sees.
How it works
- 1A GitHub event signals a new fork or public gist tied to a watched repo.
- 2An action pulls the fork or gist contents.
- 3The content is scanned for credential patterns owned by your org.
- 4A logic branch checks whether the matched key is still active via the provider.
- 5Live keys route to a PagerDuty incident tagged with the external source URL; inactive matches are logged only.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.