SECOPS
Escalate confirmed secret exposures to PagerDuty with auto-rotation
When a secret-scanning webhook reports a confirmed exposed credential, it rotates the key, opens a PagerDuty incident with full context, and logs the timeline to an audit store.
How it runs
The automated pipeline, trigger to output.
- TriggerConfirmed-exposure webhook receivedHTTP webhook
- LogicFilter for high-severity production secrets
- ActionRotate and reissue affected credentialShell
- ActionOpen PagerDuty incident with full contextPagerDuty
- OutputWrite response timeline to S3 audit bucketAWS S3
What it does
Receives confirmed exposure events from your scanner and treats them as security incidents. It rotates the affected credential, pages the on-call security engineer through PagerDuty with the leak location and blast radius, and records the full response timeline to an audit log in S3.
When to use it
Use it when a leaked production secret is a wake-someone-up event, not a ticket for next sprint. This is for the credentials that gate customer data or payment systems, where minutes of exposure matter and you need a paged human plus an automated first-response.
How it works
- 1An incoming webhook delivers a confirmed-exposure payload (credential type, source, severity).
- 2A logic step filters for high-severity, production-scoped secrets only.
- 3The flow runs a shell rotation routine to revoke and reissue the credential.
- 4It opens a PagerDuty incident with the leak source, affected service, and rotation status.
- 5It writes the complete event timeline to an S3 audit bucket for post-incident review.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect AWS S3Buckets, objects, signed URLs.
- 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.