The entity must hold written agreements with every TPSP that receives its account data or could influence CDE security, and each agreement must contain the TPSP's acknowledgment that it answers for protecting the account data it holds, stores, processes or transmits for the entity, or to whatever extent it could affect the entity's sensitive authentication data or cardholder data. Applicability: exact wording depends on the service and allocated responsibilities and need not match the requirement text. An AOC, website declaration, policy statement, responsibility matrix or other evidence outside a written agreement does not count as a written acknowledgment. Objective under the customized approach: records exist of every TPSP's acknowledgment of its duty to protect account data.
This control maps to 75 controls across 26 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.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
NIST-CSF-GV.RM-05 Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties
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-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 12.8.2 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.