SECOPS
Triage a secret-exposure PagerDuty incident with a response agent
When a secret-exposure incident opens in PagerDuty, an agent investigates the blast radius across repos and logs, drafts a remediation plan.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty secret-exposure incident openedPagerDuty
- ActionSearch GitHub for credential occurrences and blast radiusGitHub
- LogicAgent classifies severity and drafts remediation plan
- ActionPost triage note and severity to the incidentPagerDuty
- OutputMirror triage summary to SlackSlack
What it does
Wraps a PagerDuty secret-exposure incident in an investigative agent. Instead of paging a human into a cold start, the agent gathers context on where the credential lives, estimates blast radius, classifies severity, and attaches a concrete remediation plan to the incident.
When to use it
Use this when secret-exposure pages arrive with little context and your responders spend the first 20 minutes just figuring out what leaked and where. The agent does that triage so the human starts with a plan.
How it works
- 1A PagerDuty incident with a secret-exposure label triggers the workflow.
- 2The agent searches GitHub for occurrences of the credential pattern across repos and recent commits.
- 3It reasons over the findings to classify severity, identify the likely owning service, and draft rotation steps.
- 4It posts the investigation summary, severity, and recommended owner as a note on the PagerDuty incident.
- 5The same summary is mirrored to Slack so responders see it without opening PagerDuty.
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.