SECOPS
Push-Blocked Secret Auto-Rotation
When GitHub push protection blocks a commit containing a real secret, this workflow confirms the credential is live, revokes it, and opens a remediation issue assigned…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub push-protection blocked-secret webhookGitHub
- LogicValidate whether the credential is still live
- ActionRevoke the live credential via provider APIGitHub
- ActionOpen remediation issue assigned to committerGitHub
- OutputDM committer and notify security channel in SlackSlack
What it does
A blocked push usually means a developer almost leaked a working secret. This workflow treats that near-miss as a live exposure: it validates whether the credential actually works, revokes it if so, and hands the developer a clear remediation issue instead of a cryptic block message.
When to use it
Use it when your org has push protection enabled and wants every bypass attempt or blocked-secret event to trigger automatic revocation rather than relying on developers to self-report.
How it works
1. A GitHub push-protection event webhook delivers the blocked secret type and committer. 2. A logic step calls the provider's validation endpoint to check whether the credential is live. 3. If live, an action revokes the credential through its provider API. 4. A GitHub issue is opened in the affected repo, assigned to the committer, with rotation steps and the revoked key fingerprint. 5. Slack DMs the committer and posts a summary to the security channel. If the secret is dead, the flow logs the event and exits without paging anyone.
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.