PCI DSS v4 requirement 6.3.2

A software component inventory your QSA can check

Requirement 6.3.2 asks for an inventory of bespoke and custom software and the third-party components incorporated into it, to support vulnerability and patch management. An SBOM per in-scope application, kept current and monitored, is the most direct way to meet it.

The problem

What makes this hard today

How SBOMBox helps

Evidence, not just a file

Generate SBOMs where your code lives

The sbombox CLI and CI action generate CycloneDX or SPDX SBOMs in your environment. Only the SBOM and its provenance are uploaded, never source code.

Monitor for new vulnerabilities

Stored SBOMs are matched against OSV, GitHub Security Advisories, NVD and CISA KEV, so a newly exploited component shows up against the releases that contain it.

Record VEX decisions

Mark findings as not affected, affected, fixed or under investigation, with a justification, and keep that decision with the release it applies to.

Keep signed, per-release history

Every release's SBOM is stored immutably with its score and findings, so you can show what shipped in a version from two years ago.

Enforce policy in CI

Set a minimum quality score, licence allow and deny lists and required metadata. GitHub and GitLab integrations post the result as a commit status.

Score every SBOM at requirement level

Each upload is validated and scored against BSI TR-03183-2, CISA, NTIA and CRA readiness checks, with each requirement shown as pass, partial or missing.

Getting started

How teams roll it out

  1. Scope your applicationsCreate a project for each bespoke application in the cardholder data environment.
  2. Generate on every deployProduce an SBOM from the artifact you deploy, so the inventory matches production.
  3. Show the patch trailUse findings and VEX decisions as the evidence that the inventory drives patching.
Common questions

PCI DSS 6.3.2: questions we hear

Does PCI DSS require an SBOM?

Not by name. It requires an inventory of bespoke software and its third-party components; an SBOM is a common, machine-readable way to provide it.

Does SBOMBox replace our vulnerability scanner?

No. It complements it by keeping the component inventory per release and matching it against vulnerability sources.

Is this a PCI certification?

No. Assessment remains with your QSA.

Book a demo

See it with your own SBOM.

A 30-minute walkthrough focused on PCI DSS 6.3.2. Bring a CycloneDX or SPDX file and we will score it live against BSI TR-03183-2, CISA, NTIA and CRA checks.