SECOPS
Block a PR that leaks a secret, rotate it, and notify the author
When a CI secret scan flags a secret in a pull request, this workflow fails the check, rotates the exposed credential, and DMs the PR author with cleanup instructions.
How it runs
The automated pipeline, trigger to output.
- TriggerCI secret-scan result webhook on a PRGitHub
- LogicFilter to PRs where a secret was detected
- ActionSet failing commit status to block the mergeGitHub
- ActionRotate the exposed credential in GitHubGitHub
- OutputDM the PR author with cleanup steps in SlackSlack
What it does
Stops a leaked secret at the pull-request gate. When CI's secret scan finds a credential in a PR, the workflow fails the status check to block merge, rotates the exposed credential so the leaked value is worthless, and sends the author a direct message explaining what to do next.
When to use it
Use this when developers occasionally commit secrets into branches and you want to both prevent the merge and neutralize the credential immediately, without making security manually chase each author.
How it works
- 1A CI secret-scan result webhook fires when a PR scan completes.
- 2A filter proceeds only when a secret was detected in the diff.
- 3The workflow sets a failing commit status on the PR to block the merge.
- 4It rotates the exposed credential in GitHub so the leaked value no longer works.
- 5It posts a PR comment and Slack DM to the author with the detection and cleanup steps.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.