SECOPS
Match new CVE advisories against SBOM and open GitLab remediation MRs
Polls a CVE advisory feed on a schedule, matches each new advisory against your committed SBOM.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled CVE feed poll
- ActionFetch advisories since last runHTTP webhook
- ActionRead and parse SBOM from repoGitLab
- LogicMatch affected ranges to installed versions
- LogicAssign priority by severity and exploit maturity
- ActionOpen version-bump MR per affected packageGitLab
- OutputPost remediation summary to SlackSlack
What it does
Keeps your repos ahead of disclosed vulnerabilities by automatically reconciling fresh CVE advisories with the exact dependency versions you ship. When an advisory names a package and range you actually use, it opens a ready-to-review GitLab MR that pins the fixed version, so an engineer just reviews and merges instead of hunting.
When to use it
Run this when you maintain an SBOM (CycloneDX or SPDX) in-repo and want hands-off triage of upstream advisories without a paid scanner. Best for teams on GitLab who'd rather review a concrete fix than read a vuln report.
How it works
- 1A schedule fires (hourly or daily) and the run begins.
- 2An HTTP call pulls the latest advisories published since the last run.
- 3The SBOM is read from the repo via the GitLab API and parsed into a package-version map.
- 4Logic matches each advisory's affected range against installed versions and drops anything not present or already patched.
- 5For each real hit, severity and exploit-maturity set a priority label.
- 6A GitLab MR is opened per affected package bumping it to the fixed version, labeled by priority.
- 7A Slack message summarizes opened MRs and unfixable advisories needing manual review.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.