SECOPS
Exposed Key Revocation and Rotation Orchestrator
When a secret-scanning alert fires, this workflow revokes the leaked credential, mints a replacement, writes it to your secret stores.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub secret-scanning alert webhookGitHub
- LogicClassify secret type and load consumers from PostgresPostgres
- ActionRevoke leaked key and issue replacement via provider APIGitHub
- ActionWrite new secret to Cloudflare env bindingsCloudflare
- ActionRecord per-consumer rotation status in PostgresPostgres
- OutputPost incident thread with consumer tracker to SlackSlack
What it does
Turns a raw secret-leak alert into a closed-loop remediation: the old key is killed within seconds, a new key is issued, every system that consumed the old key is updated, and the incident stays open until the last consumer confirms.
When to use it
Run this whenever a production credential (API token, cloud key, signing secret) is exposed in a public repo, log, or paste. It replaces the manual scramble of revoke-here, rotate-there, and chase-the-teams with one auditable flow.
How it works
- 1A GitHub secret-scanning alert webhook fires with the matched secret pattern and location.
- 2A logic step classifies the secret type and looks up its registered downstream consumers in Postgres.
- 3The provider API call revokes the leaked credential immediately and issues a replacement.
- 4The new secret is written to Cloudflare (Workers/Pages env) and any other registered store.
- 5Postgres records each consumer's rotation status as pending.
- 6Slack posts an incident thread listing every consumer and its live update state.
- 7The flow stays open, marking consumers complete as confirmations arrive, then closes the incident.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 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.