SECOPS
GitHub Push Secret Scan to Rotate and Page
When GitHub secret scanning flags a leaked credential in a push, this workflow classifies the secret type, revokes it at the provider, opens a PagerDuty incident.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub secret scanning alert webhookGitHub
- LogicClassify secret type and severity
- ActionRevoke or rotate credential at providerCloudflare
- ActionOpen PagerDuty incident for on-callPagerDuty
- OutputPost blast-radius summary to Slack threadSlack
What it does
Turns a GitHub secret scanning alert into a closed-loop response: it identifies what kind of credential leaked, revokes or rotates it at the source, and pages the on-call so a human confirms the kill within minutes instead of hours.
When to use it
Use it when your repos have GitHub secret scanning (or push protection bypass) enabled and you need a guaranteed, auditable reaction every time a key lands in git history — not a Slack message someone might miss overnight.
How it works
- 1A GitHub `secret_scanning_alert` webhook fires with the detected secret type, repo, and commit.
- 2A logic step maps the secret type to its owning provider and severity (e.g. Cloudflare token, Stripe key, generic high-entropy).
- 3An action calls the matching provider API to revoke or roll the credential.
- 4A PagerDuty incident is opened, tagged with the repo and commit SHA, and assigned to the security on-call.
- 5The workflow outputs a Slack thread summarizing the secret, who pushed it, the revocation result, and the linked incident.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.