SECOPS
Security Advisory Dependency Fast-Track
When a vulnerability advisory webhook fires for a tracked package, it checks whether the repo uses the affected version, and if so opens a fix PR, runs tests, and pages on-call…
How it runs
The automated pipeline, trigger to output.
- TriggerSecurity advisory webhookHTTP webhook
- LogicCheck affected version + severity
- ActionBump + run testsShell
- ActionOpen fix PR with advisoryGitHub
- LogicBranch on critical severity
- OutputPage on-call for criticalPagerDuty
What it does
Listens for security advisory webhooks and reacts only when your codebase actually uses the vulnerable version range. It opens a PR bumping to the patched release, runs the test suite, and for critical-severity advisories escalates to on-call so a fix is not waiting in a review queue.
When to use it
Use it when dependency CVEs need a faster path than the normal upgrade cadence and you want escalation proportional to severity rather than treating every advisory as an emergency.
How it works
- 1An HTTP webhook receives a security advisory payload.
- 2A logic step checks the installed version against the affected range and severity.
- 3A shell step bumps to the patched version and runs tests in a checkout.
- 4A GitHub step opens the fix PR with the advisory link and test result.
- 5A logic branch checks severity.
- 6For critical advisories, a PagerDuty incident pages on-call; otherwise the flow ends with the PR.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 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.