
Last updated 8 November 2026: the future-dated requirements of PCI DSS v4.x, including 6.3.2 and 11.3.1.1, have been mandatory since 31 March 2025, and PCI DSS v4.0.1 is still the only active version of the Standard. The PCI Security Standards Council ran a request for comments on v4.0.1 from 3 June to 20 July 2026 to help decide whether and how to revise the Standard; no new version has been published yet.
PCI DSS v4.0 was the first major update to the Standard in over a decade, and it added a lot of new requirements. Of the 64 new requirements, 51 were future-dated and became mandatory on 31 March 2025. PCI DSS v4.0.1, a limited revision published in June 2024, added clarifications and guidance but no new requirements.
| New control | SBOM connection | Mandatory since |
|---|---|---|
| 6.3.2: Inventory of bespoke & custom software | Keep an SBOM for every in-house app (plus every third-party component it embeds) so you can patch quickly. |
31 March 2025 PCI Security Standards Council |
| 11.3.1.1: Manage all scan findings | Even medium/low vulnerabilities, whether flagged by scanners or revealed by your SBOM, must be remediated or formally risk-accepted (VEXed). |
31 March 2025 PCI Security Standards Council |
Before that date each control was a best practice; since then assessors score them as required.
PCI DSS 6.3.2 requires organizations to maintain an up-to-date inventory of all bespoke and custom software, including any third-party software components integrated into that custom software. In other words, for every in-house or custom application in the cardholder data environment, you need to know exactly what’s inside it, from custom-developed code to open-source libraries, APIs, runtime platforms, and other dependencies. This inventory is essentially a Software Bill of Materials for your in-scope applications. The goal is to facilitate vulnerability and patch management by ensuring no component is overlooked.
This was a new requirement in v4.0 and a best practice until 31 March 2025. Since then it has been required and must be fully considered during every PCI DSS assessment. By maintaining an SBOM for each custom application, organizations can quickly identify if a newly disclosed vulnerability (for example, in a popular open-source library like Log4j) is present in their environment, and then take action to remediate or patch it.
What does an SBOM for PCI DSS include? At minimum, it should list all custom applications and all components within those applications, whether first-party or third-party. This includes things like external libraries, frameworks, modules, APIs used, and even the underlying platforms or services the software relies on. The PCI DSS testing procedures for 6.3.2 make it clear that assessors will expect to see a documented inventory and will verify it against the software in use. In fact, testing procedure 6.3.2.a notes that “the inventory is used to identify and address vulnerabilities”, meaning it’s not enough to just catalog components: you must actively use this SBOM in your vulnerability management program. The SBOM should be kept current (e.g. updated when software is updated) and should be leveraged to track the patch status or known vulnerabilities of each component.
Implementation Tip: To comply with 6.3.2, organizations should establish a process (potentially using automated Software Composition Analysis tools) to generate and maintain SBOMs for all custom applications. Ensure that for each SBOM entry (each component) there is a mapped owner or process to monitor for vulnerabilities and apply updates. This could involve:
PCI DSS has long required regular internal and external vulnerability scans (Requirement 11.3.1 and 11.3.2). In PCI DSS 4.0, Requirement 11.3.1.1 is a new control that ensures a more comprehensive approach to scan results. In the Standard’s words, 11.3.1.1 requires that “all other applicable vulnerabilities (those not ranked as high-risk vulnerabilities or critical vulnerabilities according to the entity’s vulnerability risk rankings defined at Requirement 6.3.1)” are addressed based on the risk defined in the entity’s targeted risk analysis, with rescans as needed. Like 6.3.2, it has been required since 31 March 2025. This closes a potential gap where previously an entity might focus only on high-severity findings and neglect medium/low findings. Under 4.0, no discovered vulnerability can be simply ignored; even lower-risk issues need to be evaluated and addressed (through remediation or risk mitigation).
By addressing all vulnerabilities (with priority and timing commensurate with risk), organizations reduce their attack surface and meet the stricter expectations of PCI DSS 4.0. In summary, requirement 11.3.1.1 reinforces that security teams can’t ignore “minor” vulnerabilities: these must be managed, and SBOM-driven visibility can help ensure nothing slips through the cracks.
| Must-have feature | Why |
|---|---|
| CI/CD plug-ins | Auto-generates SBOMs per build, eliminating manual effort and cutting audit prep time. |
| Continuous monitoring of SBOM components & alerts | Detects new CVEs within hours, reducing mean-time-to-remediation and avoiding expensive emergency patch cycles. |
| Diff for builds & releases | Shows exactly what changed, speeding root-cause analysis and preventing unplanned downtime from regressions. |
| CPE / CVE enrichment | Prioritises fixes by exploitability; teams focus on high-impact issues first, lowering breach probability and cost. |
| OSS licence policy & conformance analysis | Flags non-compliant licences early, avoiding legal exposure and reducing remediation time during M&A or audits. |
| Multi-tenant, role-based access, audit trails | Lets security and dev teams share one platform securely, shrinking tool sprawl and saving admin overhead. |
| IdP / MFA support | Uses existing identity stack; no new passwords to manage, lowering help-desk load and access-breach risk. |
| API endpoints & webhooks for reports & data | Feeds SBOM intelligence into SIEM/SOAR, automating reporting and shaving hours off compliance evidence gathering. |
(Table rationale: each feature translates directly into time saved, risk reduced, or audit costs lowered.)
PCI DSS applies to entities that store, process or transmit card data, or could affect its security. The PCI Software Security Framework (SSF) is aimed at payment software vendors and has two standards: the Secure Software Standard, for the security of the software itself, and the Secure Software Lifecycle (Secure SLC) Standard, for the vendor’s development lifecycle. The Council published version 2.0 of both in 2026, and both v2.0 standards require a bill of materials.
Secure Software Standard v2.0 (January 2026): Requirement 1-2 states that “the composition of the software, including its software and hardware dependencies, is documented in a bill of materials.” The vendor chooses the format. The Council’s guidance names CycloneDX and SPDX as examples of industry standards, and notes that an SBOM can cover the software side, while the bill of materials must also record any hardware dependencies. Requirement 1-4 adds provenance for each component (the original source or supplier, its name, and its version or unique identifier) so components can be tracked across the supply chain and mapped to vulnerability information. Requirement 10-2 requires unsupported dependencies to be avoided or their risk demonstrably mitigated.
Secure SLC Standard v2.0 (September 2026): Requirement 2-1, under a new Security Objective 2 (Software Composition and Versioning), requires the vendor’s lifecycle to include processes “to document and maintain the composition of each unique software product version, including all software and hardware dependencies and third-party elements, in a bill of materials, regarding sensitive assets.” The Council’s guidance explains that the focus is on components and dependencies that involve, or can affect, the protection of sensitive assets. The format is again the vendor’s choice, though industry-recognized standards or formats are encouraged. Requirement 2-4 adds provenance for every component and subcomponent, to support traceability, vulnerability tracking and change management.
Transition: Each v2.0 standard replaces its predecessor (Secure Software v1.2.1 and Secure SLC v1.1) after a 12-month transition that starts once assessor training is available. At release, the Council said Secure Software v2.0 training would be available in the first half of 2026 (PCI Perspectives on Secure Software v2.0) and Secure SLC v2.0 training in Q4 2026 (PCI Perspectives on Secure SLC v2.0). Until each transition ends, products can still be validated against the earlier version.
How SBOMs in SSF benefit PCI DSS entities: A vendor whose payment application is validated against Secure Software v2.0 has had to document that application’s bill of materials for the assessment. Ask the vendor for it, together with the known vulnerabilities in its components, and feed both into your own 6.3.2 inventory and your 6.3.1 and 11.3.1.1 vulnerability management. Check which version of the standard the application was validated against, because the bill of materials requirement arrives with v2.0. Separately, for bespoke and custom software, PCI DSS v4.0.1 Appendix F, “Leveraging the PCI Software Security Framework to Support Requirement 6”, explains that software developed and maintained under either SSF standard can help meet parts of Requirement 6 without additional detailed testing: Requirement 6.2.4 under the Secure Software Standard, and all of 6.2 under the Secure SLC Standard. Requirement 6.3, which includes the 6.3.2 inventory, still applies as usual, though such software may support a customized-approach assessment of 6.3.
For software vendors: Under the v2.0 SSF standards, a bill of materials is an assessed requirement, not just a market expectation. Build the capability to produce one for every product version in a standard format such as CycloneDX or SPDX, keep provenance for every component and share it with clients. Sharing it helps your customers meet PCI DSS v4.0.1 (they can plug your SBOM into their 6.3.2 inventory and use it in their vulnerability management), and it demonstrates transparency and due diligence in your secure development practices.
Implementing SBOM practices for PCI compliance may seem daunting, but it can be broken down into manageable steps. Here are some actionable insights for technical teams:
The transition period ended on 31 March 2025. If these processes are not fully in place yet, start by building SBOMs for your applications and integrating them with your vulnerability management workflow. If you’re a software vendor in the payments space, align with PCI SSF expectations now: it not only prepares you for potential future validation, but also makes your product more trustworthy to clients who must meet PCI DSS. The PCI Security Standards Council’s guidance and resource hub provide clarity on these new controls, and it’s clear that SBOMs are here to stay as a foundational element of software security compliance.
By approaching SBOM requirements as an opportunity to strengthen software governance, developers and cybersecurity professionals can both meet PCI DSS 4.0/SSF obligations and significantly reduce risk in their environments. In the end, an up-to-date SBOM coupled with diligent vulnerability management is a powerful tool to protect cardholder data in today’s complex ecosystem of software and services.
This guide is general information about PCI DSS v4.0.1 and the PCI Software Security Framework, not legal advice. Both standards, and how assessors interpret them, can change. Confirm your own obligations with your Qualified Security Assessor (QSA), acquiring bank or qualified legal counsel before acting on anything here.
We shortened our vulnerability review timeframe from a day to under an hour. It is our go-to tool and we now know where to focus our limited security resources next.

SBOM Studio saves us approximately 500 hours per project on vulnerability analysis and prioritization for open-source projects.
