SECOPS
Paged Secret Exposure to Auto-Revoke and Incident
When a leaked-secret detector pages PagerDuty, this workflow auto-revokes the credential, attaches the revocation evidence to the PagerDuty incident.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty secret-exposure incident webhookPagerDuty
- LogicExtract credential and check auto-revoke allowlist
- ActionRevoke credential via provider APIGitHub
- ActionAttach revocation evidence and update PagerDuty incidentPagerDuty
- OutputAlert on-call channel in Slack with rotation stepsSlack
What it does
Bridges detection and response: a high-severity secret-exposure page triggers immediate revocation, and the proof of revocation is written straight back onto the PagerDuty incident so the on-call engineer arrives to a half-solved problem instead of a blank alert.
When to use it
Use it when secret exposures already flow through PagerDuty as incidents and you want the first containment action automated before a human acknowledges the page.
How it works
1. A PagerDuty incident webhook fires for a secret-exposure alert, carrying the credential identifier. 2. A logic step extracts the credential reference and confirms it is in scope for auto-revocation. 3. An action revokes the credential through its provider API and captures the response. 4. An action appends a note to the PagerDuty incident with the revocation timestamp and fingerprint, and updates incident status. 5. Slack alerts the on-call channel with next-step rotation instructions. Credentials outside the auto-revoke allowlist skip revocation and escalate to a human instead.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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
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.