SECOPS
Triage GitHub Dependabot alerts into prioritized Linear issues
Listens for new GitHub Dependabot alerts, enriches each with EPSS exploit probability and reachability, then files a deduplicated.
How it runs
The automated pipeline, trigger to output.
- TriggerDependabot alert created (webhook)GitHub
- ActionFetch EPSS exploit probabilityHTTP webhook
- LogicScore priority from CVSS, EPSS, reachability
- LogicFilter below-floor and dev-only alerts
- ActionResolve owning team from CODEOWNERSGitHub
- OutputCreate or update Linear issue (deduped)Linear
What it does
Turns raw Dependabot noise into a clean, prioritized backlog. Every new alert is scored by real-world exploit likelihood and whether the vulnerable code path is actually reachable, then routed as a single Linear issue to the team that owns the affected service, with duplicates folded into the existing issue.
When to use it
Use it when Dependabot is enabled across many repos and the alert volume is drowning your security channel. Ideal for engineering orgs that already plan work in Linear and want vulnerabilities to land as tracked, owned, ranked tickets.
How it works
- 1A GitHub webhook fires when a Dependabot alert is created.
- 2An HTTP call to the EPSS API fetches the exploit-probability score for the CVE.
- 3Logic computes a priority from CVSS, EPSS, and whether the dependency is a direct/reachable import.
- 4A branch filters out alerts below the priority floor and auto-dismisses dev-only dependencies.
- 5Logic maps the repo to its owning team via a CODEOWNERS lookup.
- 6A Linear issue is created or updated (dedup by CVE+repo) with priority, owner, and the fix version.
- 7The new or updated issue link is confirmed back as the output.
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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
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.
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.
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.