SECOPS
Agent-driven leaked-secret triage and guided rotation
An agent investigates a flagged leaked secret across repos and services, decides the safest rotation order, executes the rotation.
How it runs
The automated pipeline, trigger to output.
- TriggerFlagged-secret event received
- ActionAgent searches GitHub for all usagesGitHub
- LogicAgent reasons about safe rotation order
- ActionRotate Vercel value and revoke old keyVercel
- ActionOpen Linear incident with narrativeLinear
- OutputRequest sign-off in SlackSlack
What it does
Gives a security agent a flagged credential and lets it do the judgment work a junior responder would: figure out where the secret is used, what depends on it, the right order to rotate without causing an outage, then carry out the rotation across GitHub and Vercel and write up a clear incident report for review.
When to use it
Use this for secrets that are not a clean one-to-one rotation, where blindly swapping a value could break dependent services. The agent reasons about blast radius before acting, which a deterministic pipeline cannot.
How it works
- 1A flagged-secret event starts the agent with the credential fingerprint and source.
- 2The agent searches GitHub for every reference and reconstructs where the key is consumed.
- 3It reasons about dependencies and proposes a safe rotation sequence.
- 4It rotates the value in Vercel and revokes the old credential, staging changes to avoid breaking live traffic.
- 5It opens a Linear incident with its findings, the rotation order it used, and residual risk.
- 6It posts a human-readable summary to Slack requesting sign-off on the closed incident.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.