SECOPS
Escalate security-driven dependency bumps by exploitability and reach
When a GitLab dependency MR closes a known vulnerability, this checks the advisory severity, measures how deep the package reaches into production code.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened with security-advisory labelGitLab
- ActionRead advisory severity, CVSS, and affected packageGitLab
- ActionMeasure production reachability from dependency graphPostgres
- LogicCombine severity and reach into escalation tier
- ActionPage on-call for critical reachable bumpsPagerDuty
- OutputPost lower-tier bumps to security Slack channelSlack
What it does
Not every CVE is an emergency. This workflow detects security-flagged dependency MRs, pulls the advisory severity and exploitability, measures whether the vulnerable package sits on a production code path, and escalates only the bumps that are both severe and reachable, routing the rest to a normal review queue.
When to use it
Use it when security bots open a steady stream of dependency MRs and your team can't tell which ones warrant dropping everything. It separates "critical CVE in a runtime auth library" from "moderate advisory in a dev-only build tool."
How it works
- 1A GitLab MR webhook fires when an MR carries a security-advisory label.
- 2The workflow reads the linked advisory to extract severity, CVSS, and the affected package.
- 3It queries the Postgres dependency graph to determine whether the package reaches any production entrypoint and how many modules depend on it.
- 4A logic step combines severity with production reachability to set an escalation tier.
- 5Critical-and-reachable bumps page on-call via PagerDuty with the MR and advisory; lower tiers post a Slack note to the security review channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.