12.5.2.1 Service provider scope confirmed every 6 months
Additional requirement for service providers: PCI DSS scope is documented and confirmed at least once every six months and upon significant change.
5
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
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
- Semi-annual scoping records with sign-off · Document repository
- Change-triggered scoping reviews · Document repository
governing documentDocuments that govern the control
- Updated diagrams per cycle · Document repository
- Inventory reconciliation · Policy repository / GRC workspace
- Customer notification of scope changes if applicable · 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
- Annual only
- Change-triggered reviews missed
- No customer notification
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.2 PCI DSS scope documented and confirmed annually · 12.5.3 Impact analysis on org structure changes (SP)