Tool integration

Docker Scout Integration Guide

Docker's built-in image vulnerability scanning with SARIF and SBOM output

Get a Free API Key

Integrate Docker Scout with Vulnetix. Scan container images for CVEs using Docker Scout and export SARIF findings or CycloneDX SBOMs for upload to Vulnetix.

CLI toolSARIFCycloneDXSPDX

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: warn

Then one publish job hands every artifact in the run to Vulnetix, recorded under Docker Scout's own name and version. Written once per workflow, however many scanners you run:

publish:
  name: Publish to Vulnetix
  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 Vulnetix CLI
      run: |
        curl -fsSL https://cli.vulnetix.com/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" --json

After the run, vulnetix gha status reports what was actually recorded.

How Vulnetix compares: better together

Vulnetix does not replace Docker Scout. Keep running it. Vulnetix 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 Vulnetix spans categories.

CapabilityVulnetixDocker Scout
Security coverage
SAST (static code analysis)Built-in rules + Semgrep augmentation
SCA / dependencies40+ ecosystems, transitive graphDetects application-dependency vulnerabilities within images, not just OS packages
DAST (dynamic testing)~ Ingests DAST results; no native dynamic engine
Container & imageImage CVEs, base image, DockerfileCore: CVE scanning of image OS + app packages across ~23 advisory DBs
IaC / misconfigurationTerraform, k8s, CloudFormation
Secret scanning1,000+ rules, source + binary + git history
Cloud / CSPMCloud-posture findings, compliance tab
Mobile (MAST)~ Ingests mobile scanner output; no native mobile engine
License complianceSPDX, copyleft/AGPL/SSPL policy~ Surfaces package license metadata as part of image inventory
SBOM generationCycloneDX 1.7 + SPDX 2.3, cosign-signableGenerates SBOMs in CycloneDX and SPDX formats
Malware / supply-chainDe-duplicated corpus + install-time firewall (25+ registries)
Network / infra vuln~ Ingests network scanner output; no native network scanner
FuzzingIngests fuzzing crashes; no native fuzzer
Pentest / bug bountyIngests pentest/bug-bounty findings; not a testing service
The Vulnetix orchestration layer
Cross-scanner dedup & one queue (ASPM)Correlates every scanner into one prioritised queue with ownership routing
Exploit-intel prioritisationEPSS, CISA KEV, Coalition ESS, CWSS, Vulnetix LEV~ Surfaces CVSS (v4 preferred), EPSS scoring and CISA KEV flags for prioritisation
Reachability analysisTree-sitter + CVEAffected; direct/transitive/semantic
Versioned VEX + audit trailImmutable OpenVEX/CycloneDX, cosign-signable~ Consumes/authors VEX statements to filter non-exploitable CVEs; not immutable-versioned VEX
Safe Harbour autofixResolves + applies the nearest safe version~ Actionable remediation + base-image upgrade suggestions; not automated fix PRs
End-of-life policyFlags/blocks past-EOL runtimes & packages~ Flags out-of-date/end-of-support base images via recommendations
SSVC / risk-based policySSVC v2 + CISA/FedRAMP/Essential-8 presets

✓ full · ~ partial · ✗ not covered

What Docker Scout does well

Where Vulnetix adds to it: Docker Scout is a strong container-native scanner but stays inside the Docker ecosystem and one image at a time. Vulnetix sits above it and every other scanner (SAST, IaC, secrets, cloud, SCA) to dedup findings into one prioritised queue, add Coalition ESS / CWSS / Vulnetix 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, Vulnetix 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; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.

Centralise Docker Scout results in Vulnetix

Upload Docker Scout SARIF, CycloneDX, SPDX output to the Vulnetix 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.

Docker Scout documentation ↗

Wire Docker Scout into your CI/CD pipeline →