PCI DSS requirement 12.5.2: confirming your scope every year
By Sam Rivera, Founder, SentinelPanda · October 24, 2026 · 2 min read · PCI DSS
Scope used to be negotiated at the start of an assessment. Now it is a document you own and re-confirm.
What changed in 4.0
In earlier versions, scoping guidance sat in the introduction to the standard, and in practice the assessor often drew the boundary during fieldwork. Version 4.0 turned scoping into requirement 12.5.2, which you perform, document and can fail. The assessor now validates your scope rather than defining it.
What the confirmation must include
- Every data flow, across payment stages (authorisation, capture, settlement, chargebacks, refunds) and acceptance channels (card-present, card-not-present, e-commerce).
- Updated data-flow diagrams, as required by 1.2.4.
- Every location where account data is stored, processed or transmitted — including any outside the CDE you currently define, and backups.
- Every system component in the CDE, connected to it, or able to affect its security.
- Every segmentation control in use, and the justification for each environment you treat as out of scope.
- Every connection from a third party with access to the CDE.
- Confirmation that all of the above are included in scope.
What counts as a significant change
The standard gives examples rather than a definition, so set your own triggers and write them down. Reasonable ones: a new acceptance channel, a new payment service provider, a cloud or data-centre migration, a change to segmentation, an acquisition, and any new application that touches account data. Each should prompt a scope review before the change goes live, not at the next annual cycle.
Finding data outside the CDE
The element that most often surprises people is the requirement to look outside the boundary you have drawn. Account data turns up in support tickets, email inboxes, call recordings, analytics exports, debug logs and old database backups. A data-discovery scan across file shares and data stores is the practical way to check, and when it does find PAN, requirement 12.10.7 sets out what your incident response procedure has to do about it.
Service providers
Requirement 12.5.2.1 shortens the cycle to every six months for service providers, plus after any significant change. Requirement 12.5.3 adds that a significant change to organisational structure — a merger, a reorganisation, a new parent company — triggers a documented review of its effect on scope and on control applicability, with the results communicated to executive management.
Making it repeatable
- Keep the scope statement as a living document with a date, an owner and an approver.
- Compare each confirmation with the previous one and record what changed and why.
- Tie it to the system component inventory under 12.5.1, so the two cannot drift apart.
- Version the data-flow diagrams alongside it.