Integrate Docker Scout with Vulnesis. Scan container images for CVEs using Docker Scout and export SARIF findings or CycloneDX SBOMs for upload to Vulnesis.
Install & scan
$ # Docker Scout is included in Docker Desktop and Docker Engine 24.0+ docker scout version # Or install the CLI plugin curl -fsSL https://raw.githubusercontent.com/docker/scout-cli/main/install.sh | sh $ # Scan for CVEs with SARIF output docker scout cves myimage:latest --format sarif --output docker-scout.sarif # Generate CycloneDX SBOM docker scout sbom myimage:latest --format cyclonedx --output docker-scout.cdx.json
Run Docker Scout in CI
Scan on every push and upload the report as a workflow artifact:
- name: Build image
run: docker build -t myapp:${{ github.sha }} .
- name: Scan with Docker Scout
run: |
docker scout cves myapp:${{ github.sha }} --format sarif --output docker-scout.sarif
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: docker-scout
path: docker-scout.sarif
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under Docker Scout's own name and version. Written once per workflow, however many scanners you run:
publish:
name: Publish to Vulnesis
runs-on: ubuntu-latest
needs: [scan] # every scanner job, or its report is never published
if: always() # or one failing scanner suppresses all the others
permissions:
contents: read
actions: read # required to list the run's artifacts
env:
VULNETIX_ORG_ID: ${{ secrets.VULNETIX_ORG_ID }}
VULNETIX_API_KEY: ${{ secrets.VULNETIX_API_KEY }}
steps:
- uses: actions/checkout@v5
- name: Install Vulnesis CLI
run: |
curl -fsSL https://cli.vulnes.is/install.sh | sh -s -- --install-dir "$HOME/.local/bin"
echo "$HOME/.local/bin" >> "$GITHUB_PATH"
- name: Publish scanner reports
env:
GITHUB_TOKEN: ${{ github.token }}
run: vulnetix gha upload --org-id "$VULNETIX_ORG_ID" --jsonAfter the run, vulnetix gha status reports what was actually recorded.
How Vulnesis compares: better together
Vulnesis does not replace Docker Scout. Keep running it. Vulnesis sits on top of Docker Scout (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
Docker Scout is strongest at its core category and also carries features in SCA, SBOM Generation, License Compliance, just as Vulnesis spans categories.
| Capability | Vulnesis | Docker Scout |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ✓ Detects application-dependency vulnerabilities within images, not just OS packages |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ✓ Core: CVE scanning of image OS + app packages across ~23 advisory DBs |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✗ |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ✗ |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ~ Surfaces package license metadata as part of image inventory |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✓ Generates SBOMs in CycloneDX and SPDX formats |
| Malware / supply-chain | ✓ De-duplicated corpus + install-time firewall (25 registries) | ✗ |
| Network / infra vuln | ~ Ingests network scanner output; no native network scanner | ✗ |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests pentest/bug-bounty findings; not a testing service | ✗ |
| The Vulnesis orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ✗ |
| Exploit-intel prioritisation | ✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnesis LEV | ~ Surfaces CVSS (v4 preferred), EPSS scoring and CISA KEV flags for prioritisation |
| Reachability analysis | ✓ Tree-sitter + CVEAffected; direct/transitive/semantic | ✗ |
| Versioned VEX + audit trail | ✓ Immutable OpenVEX/CycloneDX, cosign-signable | ~ Consumes/authors VEX statements to filter non-exploitable CVEs; not immutable-versioned VEX |
| Safe Harbour autofix | ✓ Resolves + applies the nearest safe version | ~ Actionable remediation + base-image upgrade suggestions; not automated fix PRs |
| End-of-life policy | ✓ Flags/blocks past-EOL runtimes & packages | ~ Flags out-of-date/end-of-support base images via recommendations |
| SSVC / risk-based policy | ✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets | ✗ |
✓ full · ~ partial · ✗ not covered
What Docker Scout does well
- Base-image recommendations that show which base-image upgrade removes the most CVEs, a genuinely useful, image-specific remediation signal
- Deeply integrated across Docker Hub, Docker Desktop, the CLI and a hosted dashboard, so scanning is one command away from where developers already work
- Policy evaluation engine plus CI/CD gating (GitHub Action) to enforce standards across an image portfolio
- Matches components against ~23 advisory sources (including CISA KEV and EPSS) and supports VEX statements to suppress non-exploitable CVEs
Where Vulnesis adds to it: Docker Scout is a strong container-native scanner but stays inside the Docker ecosystem and one image at a time. Vulnesis sits above it and every other scanner (SAST, IaC, secrets, cloud, SCA) to dedup findings into one prioritised queue, add Coalition ESS / CWSS / Vulnesis LEV prioritisation on top of the CVSS+EPSS+KEV Scout already provides, reachability, immutable versioned VEX with audit trail, SSVC policy and Safe Harbour autofix. Better together: Scout scans the image, Vulnesis orchestrates and prioritises its output alongside the rest of the estate.
No migration, no rip-and-replace. Docker Scout keeps doing what it does best; Vulnesis adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today. Software Factory agents on a Pix Sandbox can then turn the findings from any scanner into pull requests that a person approves. How Software Factory works.
Centralise Docker Scout results in Vulnesis
Upload Docker Scout SARIF, CycloneDX, SPDX output to the Vulnesis platform to deduplicate findings, prioritise them with EPSS, CISA KEV and Coalition ESS exploit intelligence, and track remediation across every scanner in a single queue.