PCI DSS requirement 6.3.2: the bespoke software inventory
By Sam Rivera, Founder, SentinelPanda · October 24, 2026 · 2 min read · PCI DSS
You cannot patch a library you do not know you ship.
What 6.3.2 says
Maintain an inventory of bespoke and custom software, and of the third-party software components incorporated into that software, to facilitate vulnerability and patch management. It was a best practice until 31 March 2025 and is now assessed.
"Bespoke and custom" means software developed by you or specifically for you. Commercial off-the-shelf products are covered elsewhere — by your system component inventory under 12.5.1 and by patching under 6.3.3. The new requirement is about the code you are responsible for and everything it pulls in.
Why it exists
When Log4Shell was disclosed in December 2021, the hard question for most organisations was not how to patch. It was whether they used Log4j at all, and where — often as a dependency of a dependency nobody had chosen directly. Requirement 6.3.1 already asked you to identify new vulnerabilities, and 6.3.3 asks you to install critical patches within a month. Without an inventory there is nothing connecting the two.
Build it from the pipeline
- Generate a software bill of materials in a standard format, CycloneDX or SPDX, as part of every build.
- Include transitive dependencies. Lockfiles are a starting point, not the inventory.
- Keep one per release, so you can answer what was running in production on a given date.
- Feed it to a dependency scanner so new advisories are matched against it automatically.
- Cover container base images and anything vendored into the repository, which scanners reading package manifests will miss.
Front-end code counts too
JavaScript bundled into your own payment or account pages is bespoke software with third-party components, and it belongs in the inventory. This is distinct from requirement 6.4.3, which covers the scripts a payment page loads in the browser, including ones served by third parties. The two overlap at the bundle you build and ship, so it is worth managing them together.
What assessors look for
- An inventory that covers every in-scope bespoke application, with component names and versions.
- A date showing it is current, ideally generated automatically.
- Evidence that it is used: an advisory that was matched against the inventory and resulted in a patch.