SECOPS
GitHub Secret-Scanning Alert to Owner Rotation
When GitHub secret scanning flags a leaked credential in a repo, this workflow identifies the owning service from CODEOWNERS, opens a tracking issue.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub secret-scanning alert webhookGitHub
- LogicDrop resolved or test-token alerts
- ActionResolve owning team via CODEOWNERSGitHub
- ActionOpen tracking issue for owning teamGitHub
- ActionPage owning team's on-callPagerDuty
- OutputPost triage summary to security channelSlack
What it does
Turns a raw GitHub secret-scanning alert into an owned, trackable rotation task. It maps the leaked secret to the team that owns the affected path, creates an issue with the exact file and commit, and escalates to that team's on-call so the credential is rotated before it's abused.
When to use it
Use it when your org has GitHub Advanced Security secret scanning enabled and you want every alert to land on a named owner instead of dying in a security inbox. Ideal for teams with clear CODEOWNERS coverage.
How it works
- 1A GitHub secret-scanning alert webhook fires with the secret type, repo, and file path.
- 2The flow filters out resolved or test-token alerts so only live, exploitable secrets continue.
- 3It reads CODEOWNERS for the leaked file path to resolve the owning team and service.
- 4It opens a GitHub issue tagged to that team, embedding the commit SHA, file, and secret type.
- 5It pages the resolved team's on-call rotation in PagerDuty with the issue link.
- 6It posts a triage summary to the security Slack channel with the owner and rotation deadline.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.