What evidence do auditors commonly ask for on 12.5.1 Inventory of in-scope system components?

In-scope system component inventory with function/use field; Inventory owner assignment; Change or update history of the inventory; Reconciliation against discovery scans or CMDB.

What is the most common gap auditors find on 12.5.1?

Cloud workloads or container images missing from the inventory

PCI DSS v4.0.1 · Req 12: Information Security Policies

`12.5.1` Inventory of in-scope system components

The entity must keep a current inventory covering every system component within PCI DSS scope, with a description of each component's function or use. The guidance suggests making in-scope components clearly identifiable within a broader asset inventory, including container images that could be spun up, and giving the inventory an owner. Customized approach objective: every system component within PCI DSS scope is identified and known.

Source: PCI DSS v4.0.1, 12.5.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

artefacts

held by a system

at each review

moderate

to go live

Policy repository / GRC workspace

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Change or update history of the inventory · Policy repository / GRC workspace

periodic reviewEvidence produced at each review

Reconciliation against discovery scans or CMDB · Vulnerability scanner / patch tooling

governing documentDocuments that govern the control

In-scope system component inventory with function/use field · Policy repository / GRC workspace
Inventory owner assignment · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Policy repository / GRC workspace); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Cloud workloads or container images missing from the inventory
No description of function for many entries
Inventory not updated after decommissioning or new builds

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

12.4.2.1 Documentation of quarterly operational reviews · 12.5.2 Annual and change-driven scope confirmation