PCI DSS 4.0 12.8.4: 12.8.4 Annual monitoring of TPSP compliance status
The entity must run a program that checks, at least every 12 months, where each TPSP stands on PCI DSS compliance. Applicability: where a TPSP meets PCI DSS requirements on the entity's behalf (a firewall service, for example), the entity must work with it to ensure those requirements are met; if the TPSP falls short, those requirements also count as not in place for the entity. Customized approach objective: each TPSP's compliance standing gets checked periodically.
This control maps to 71 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-DE.CM-06 External service provider activities and services are monitored to find potentially adverse events
NIST-CSF-GV.SC-04 Suppliers are known and prioritized by criticality
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.RA-10 Critical suppliers are assessed prior to acquisition
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.4 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.