PCI DSS 4.0 12.8.5: 12.8.5 Responsibility allocation between entity and TPSPs
The entity must keep information showing which PCI DSS requirements each TPSP manages, which the entity manages itself, and which are shared between them. The guidance describes a responsibility matrix as a common way to record this and says entities should understand any nested relationships where a primary TPSP relies on secondary TPSPs. Customized approach objective: the entity keeps, and periodically reviews, records showing which requirements and associated components each TPSP owns alone or shares.
This control maps to 64 controls across 25 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
NIST-CSF-GV.SC-02 Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally
NIST-CSF-GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties
NIST-CSF-GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship
NIST-CSF-ID.AM-04 Inventories of services provided by suppliers are maintained
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 12.8.5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.