12.5.2 PCI DSS scope documented and confirmed annually
PCI DSS scope is documented and confirmed at least once every 12 months by identifying all data flows, system components, and segmentation controls in use.
5
artefacts
0
held by a system
1
at each review
hard
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
none for this control
periodic reviewEvidence produced at each review
- Annual scoping exercise minutes and sign-off · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Scope document with named components · Policy repository / GRC workspace
- Data flow diagrams covering all CHD flows · Policy repository / GRC workspace
- Network and segmentation diagrams · Policy repository / GRC workspace
- Inventory cross-references · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Diagrams stale
- Annual scoping skipped
- Flows incomplete
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.5.1 Inventory of system components in scope · 12.5.2.1 Service provider scope confirmed every 6 months