SECOPS
Scan pushes for leaked secrets and open a PagerDuty incident on verified hits
Scans every Git push for credential patterns, verifies each suspected secret is live, and opens a PagerDuty incident only for confirmed exposures so on-call sees real leaks.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub push event receivedGitHub
- ActionFetch commit diffs from GitHub APIGitHub
- LogicMatch added lines against secret patterns
- LogicKeep only secrets that pass a liveness probe
- ActionOpen PagerDuty incident per verified leakPagerDuty
- OutputPost incident link as GitHub commit statusGitHub
What it does
On every push to a GitHub repo, this workflow scans the new commits' diffs for credential patterns (API keys, tokens, private keys, connection strings). For each suspected match it runs a lightweight validation to decide whether the secret is actually live, then opens a PagerDuty incident for confirmed leaks and stays silent on false positives.
When to use it
Use it when you want push-time secret detection that pages on-call only for real, exploitable exposures. It is the right fit for teams that already triage incidents in PagerDuty and are drowning in scanner noise from inert or already-rotated strings.
How it works
- 1A GitHub push event fires the workflow with the changed commit range.
- 2An action fetches each commit's diff from the GitHub API.
- 3A scan step matches the added lines against a curated set of secret regexes and entropy rules.
- 4A logic branch keeps only matches that pass a liveness probe (the key authenticates) and drops the rest.
- 5For each verified leak, a PagerDuty action opens an incident tagged with the repo, file, and commit SHA.
- 6The final output posts the incident link back as a GitHub commit status.
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.