SECOPS
Confirmed Secret Leak to Incident Bridge and Postmortem
When a high-severity credential exposure is confirmed, this workflow opens a PagerDuty incident, spins up a Slack war room.
How it runs
The automated pipeline, trigger to output.
- TriggerConfirmed high-severity leak webhookHTTP webhook
- LogicGate on incident-level severity
- ActionDeclare PagerDuty incidentPagerDuty
- ActionOpen Slack incident war roomSlack
- ActionSeed pre-filled postmortem pageConfluence
- OutputPost linked incident bundle to security channelSlack
What it does
For the leaks serious enough to be incidents, this workflow runs the coordination layer. It declares a PagerDuty incident, assembles the responders in a dedicated Slack channel, and stands up a postmortem document already populated with the detection source, affected service, and timeline so responders coordinate instead of scrambling.
When to use it
Use it for confirmed high-severity exposures, like a production database credential or signing key found in public, where ad-hoc rotation isn't enough and you need a tracked incident with a paper trail.
How it works
- 1A webhook receives a confirmed high-severity leak event with the secret type and owning service.
- 2The flow gates on severity so only true incidents trigger the full bridge.
- 3It declares a PagerDuty incident assigned to the security escalation policy.
- 4It opens a dedicated Slack incident channel and posts the initial context and responders.
- 5It creates a Confluence postmortem page seeded with the detection time, source, and affected service.
- 6It links the incident, channel, and postmortem together and posts the bundle to the security channel.
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 SlackChannels, DMs, threads, mentions.
- 4Connect ConfluenceSpaces, pages, blueprints.
- 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
Scheduled AWS Access-Key Age Sweep and Forced Rotation
Runs daily to find IAM access keys older than your policy threshold, deactivates the stale key, issues a fresh pair, and notifies the key owner with their replacement instructions.
Correlate Datadog WAF anomaly alert with Cloudflare evidence
When Datadog fires a WAF block-rate anomaly monitor, it pulls the matching Cloudflare firewall events, builds an evidence pack of top rules and ASNs.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
Non-Rotatable Leaked Secret to PagerDuty Escalation
Catches secret-scan hits for credentials that cannot be auto-rotated, gathers blast-radius context, and pages the on-call engineer with a step-by-step manual rotation runbook.
GitHub Secret-Scan Hit to Auto-Revoke and Rotate
When GitHub secret scanning flags a leaked credential in a repo, it auto-classifies the secret type, revokes the live key at the provider, mints a replacement.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
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.