12.5.1 Inventory of system components in scope
An inventory of system components in scope for PCI DSS is maintained and kept current, including a description of function or use.
5
artefacts
2
held by a system
0
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
system holds itEvidence a system already holds
- CMDB or asset inventory export covering CDE · Policy repository / GRC workspace
- Sample reconciliation with discovery scans · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Function or use field per asset · Policy repository / GRC workspace
- Update procedure and change control · Policy repository / GRC workspace
- Inventory owner assignment · Policy repository / GRC workspace
First move
Start with the 2 of 5 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
- Inventory stale
- Function field empty
- No reconciliation
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 sheet12.4.2.1 Documentation of quarterly reviews (SP) · 12.5.2 PCI DSS scope documented and confirmed annually