SECOPS
CEO-Triaged Exposed-Secret Response
An agent triages each incoming secret-scanner hit, judges blast radius and key type, drafts a tailored rotation plan.
How it runs
The automated pipeline, trigger to output.
- TriggerScanner hit arrives via webhookHTTP webhook
- ActionAgent gathers repo + commit contextGitHub
- LogicClassify severity and blast radiusOpenAI
- LogicBranch: real exposure vs false positive
- ActionOpen issue with generated rotation planGitHub
- OutputRequest owner acknowledgement in SlackSlack
What it does
Applies judgement to scanner noise. The agent reads the alert in context, estimates how bad the exposure is, decides whether it warrants a full rotation or a downgrade, and writes a specific remediation plan rather than a generic ticket.
When to use it
Use it when scanner hits vary wildly in severity (an expired test token versus a live production database URL) and a flat rule engine over- or under-reacts. The agent decides the response per case.
How it works
- 1A scanner hit arrives via inbound webhook with repo, secret type, and commit context.
- 2The CEO agent pulls the surrounding file, commit history, and repo metadata from GitHub to assess real blast radius.
- 3It classifies severity and drafts a rotation plan with concrete steps for that credential type.
- 4A decision branch separates true exposures needing rotation from confirmed false positives or already-dead keys.
- 5For true exposures it opens a GitHub issue with the generated plan and requests owner ack in Slack.
- 6It records its reasoning and classification so future triage stays consistent.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect OpenAIModels, embeddings, files.
- 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.