SECOPS
Agent-Driven Secret Triage and Disposition
When a secret is detected in a push, an agent investigates whether the key is live, who owns it, and where it is used.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub push delivers candidate secretGitHub
- ActionAgent validates liveness and gathers ownership contextHTTP webhook
- LogicRoute on agent disposition: dismiss or confirm
- ActionQuarantine commit and fire rotation webhookGitHub
- OutputDocument evidence and reasoning in LinearLinear
What it does
This workflow puts an investigating agent between detection and action. Instead of a fixed rule deciding what to do, the agent gathers context — is the token still valid, what service owns it, is it a test fixture — and chooses the right disposition, cutting false-positive noise while still acting fast on real leaks.
When to use it
Use it on busy repos where naive scanners generate too many false alarms (example keys in docs, expired tokens) and a human would otherwise burn time triaging each one. The agent does that triage and only escalates genuine exposures.
How it works
- 1A GitHub push event delivers the candidate secret match to the agent.
- 2The agent calls a validation webhook to test whether the credential is live and queries the GitHub API for surrounding context and ownership.
- 3A logic branch routes on the agent's disposition: dismiss as false positive, or confirm exposure.
- 4On confirmation, an action moves the commit to a quarantine branch and fires the rotation webhook.
- 5The agent writes a Linear ticket capturing the evidence, its reasoning, and the disposition as the final record.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.