12.5.3 Additional requirement for service providers only
Defined Approach Requirements
12.5.3 Additional requirement for service providers only: Significant changes to organizational structure result in a documented (internal) review of the impact to PCI DSS scope and applicability of controls, with results communicated to executive management.
Customized Approach Objective
PCI DSS scope is confirmed after significant organizational change.
Applicability Notes
This requirement applies only when the entity being assessed is a service provider.
This requirement is a best practice until 31 March 2025, after which it will be required and must be fully considered during a PCI DSS assessment.
Defined Approach Testing Procedures
12.5.3.a Additional testing procedure for service provider assessments only: Examine policies and procedures to verify that processes are defined such that a significant change to organizational structure results in a documented review of the impact to PCI DSS scope and applicability of controls, with results communicated to executive management.
12.5.3.b Additional testing procedure for service provider assessments only: Examine documentation (for example, meeting minutes) and interview responsible personnel to verify that significant changes to organizational structure resulted in documented reviews of the impact to PCI DSS scope and applicability of controls, with results communicated to executive management.
Purpose
An organization's structure and management define the requirements and protocol for effective and secure operations. Changes to this structure could have negative effects to existing controls and frameworks by reallocating or removing resources that once supported PCI DSS controls or inheriting new responsibilities that may not have established controls in place. Therefore, it is important to revisit PCI DSS scope and controls when there are changes to an organization's structure and management to ensure controls are in place and active.
Examples
Changes to organizational structure include, but are not limited to, company mergers or acquisitions, and significant changes or reassignments of personnel with responsibility for security controls.
purpose
Maintain documentation of PCI DSS scope confirmation activities.
compliance strategies
- Scope review logs
- Documentation retention
typical policies
- Scope Review Documentation Policy
common pitfalls
- No evidence of scope confirmation
type
Documentation Control
difficulty
Low
key risks
- Inability to demonstrate compliance
recommendations
- Centralize scope documentation
Eligible SAQ
- SAQ-D SERVICE PROVIDER
Your perspective on this PCI DSS requirement matters! Share your implementation experiences, challenges, or questions below. Your insights help other organizations improve their compliance journey and build a stronger security community.Comment Policy