PCI DSS 4.0 12.8.3: 12.8.3 Due diligence before engaging TPSPs
An established process must be in place and used for engaging TPSPs, including appropriate due diligence before the engagement starts. The guidance suggests due diligence consider how the provider reports, how it notifies breaches and handles incidents, how PCI DSS responsibilities are split, and how the TPSP validates compliance and what evidence it supplies. Customized approach objective: before engagement, a prospective TPSP's capability, intent and resources to protect account data are assessed.
This control maps to 69 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.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders
NIST-CSF-GV.SC-04 Suppliers are known and prioritized by criticality
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-06 Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships
NIST-CSF-ID.RA-10 Critical suppliers are assessed prior to acquisition
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 12.8.3 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.