Tool integration

Docker Scout SBOM integration guide

Docker Scout SBOM generation for container images

Get a Free API Key

Generate CycloneDX or SPDX SBOMs from container images using Docker Scout sbom command and upload to Vulnesis.

CLI toolSPDXCycloneDX

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
$ # Generate CycloneDX SBOM from container image
docker scout sbom myimage:latest --format cyclonedx --output scout-sbom.cdx.json

# Generate SPDX SBOM
docker scout sbom myimage:latest --format spdx-json --output scout-sbom.spdx.json

Run Docker Scout SBOM in CI

Scan on every push and upload the report as a workflow artifact:

- name: Generate SBOM with Docker Scout
  run: docker scout sbom myapp:${{ github.sha }} --format cyclonedx --output scout-sbom.cdx.json

- name: Upload report
  uses: actions/upload-artifact@v6
  with:
    name: docker-scout-sbom
    path: scout-sbom.cdx.json
    if-no-files-found: warn

Then one publish job hands every artifact in the run to Vulnesis, recorded under Docker Scout SBOM'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" --json

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

How Vulnesis compares: better together

Vulnesis does not replace Docker Scout SBOM. Keep running it. Vulnesis sits on top of Docker Scout SBOM (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.

Docker Scout SBOM is strongest at its core category and also carries features in Container & Image Scanning, SCA, just as Vulnesis spans categories.

CapabilityVulnesisDocker Scout SBOM
Security coverage
SAST (static code analysis)✓ Built-in rules + Semgrep augmentation✗
SCA / dependencies✓ 40+ ecosystems, transitive graph~ Scout cves matches image packages (incl language deps) against multiple advisory sources; container-centric, not a general repo SCA
DAST (dynamic testing)~ Ingests DAST results; no native dynamic engine✗
Container & image✓ Image CVEs, base image, Dockerfile✓ Purpose-built for container images: analyzes image layers and surfaces base-image update paths
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✗
SBOM generation✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable✓ docker scout sbom emits CycloneDX and SPDX for images, OCI dirs, tarballs and local paths
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✗
Reachability analysis✓ Tree-sitter + CVEAffected; direct/transitive/semantic✗
Versioned VEX + audit trail✓ Immutable OpenVEX/CycloneDX, cosign-signable✗
Safe Harbour autofix✓ Resolves + applies the nearest safe version~ Recommends updated/patched base images and layer-specific fixes, but suggestions are not automated fix PRs
End-of-life policy✓ Flags/blocks past-EOL runtimes & packages✗
SSVC / risk-based policy✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets✗

✓ full · ~ partial · ✗ not covered

What Docker Scout SBOM does well

Where Vulnesis adds to it: Vulnesis ingests Docker Scout's CycloneDX/SPDX SBOMs and CVE output and folds them into a cross-scanner deduplicated queue, then layers exploit-intel prioritisation (EPSS/KEV/ESS/LEV), reachability, versioned VEX, SSVC and Safe Harbour autofix on top. Scout stays the container SBOM/CVE engine; Vulnesis does not replace its image analysis, it consolidates and prioritises it alongside SAST, IaC, secrets and cloud findings.

No migration, no rip-and-replace. Docker Scout SBOM 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 SBOM results in Vulnesis

Upload Docker Scout SBOM SPDX, CycloneDX 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.

Docker Scout SBOM documentation ↗

Wire Docker Scout SBOM into your CI/CD pipeline →