PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.9.2: 12.9.2 TPSP support for customer information requests

Service providers only: TPSPs must support customer requests for information they need under Requirement 12.8.4 and Requirement 12.8.5, supplying, on request: PCI DSS compliance status information (12.8.4); and information on which requirements are the TPSP's responsibility, which are the customer's, and any shared responsibilities (12.8.5), for every service that meets a requirement for customers or can influence how well the cardholder data or sensitive authentication data of customers is protected. Applicability: applies only when the assessed entity is a service provider. Customized approach objective: TPSPs supply information as needed to back customers' compliance efforts.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 24 controls across 14 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

ISO 27001:2022 · 4 controls

  • 5.19 Information security in supplier relationships
  • 5.20 Addressing information security within supplier agreements
  • 5.22 Monitoring, review and change management of supplier services
  • 5.31 Legal, statutory, regulatory and contractual requirements

ISO 27701:2019 · 3 controls

  • 6.12.1 Information security in supplier relationships
  • 6.15.1 Compliance with legal and contractual requirements
  • 8.5.6 Disclosure of subcontractors used to process PII

C5 (Germany) · 2 controls

  • C5-PI-02 Contractual agreements for the provision of data
  • C5-PSS-01 Guidelines and Recommendations for Cloud Customers

HIPAA Security Rule · 2 controls

  • 164.308(b)(1) Business Associate Contracts and Other Arrangements (Standard)
  • 164.314(a)(1) Business Associate Contracts or Other Arrangements (Standard)

ISO 27002:2022 · 2 controls

  • 5.20 Addressing information security within supplier agreements
  • 5.22 Monitoring, review and change management of supplier services

SOC 2 · 2 controls

  • SOC2-CC2.3 CC2.3 Communication with external parties about internal control (COSO principle 15)
  • SOC2-P6.4 P6.4 Privacy commitments from vendors and third parties

APRA CPS 234 · 1 control

  • CPS234-P28 Assessment of Reliance on Third Party Control Testing

FedRAMP High · 1 control

  • SA-9 External System Services

FedRAMP Moderate · 1 control

  • SA-9 External System Services

ISO/IEC 42001:2023 · 1 control

  • A.8.5 Information for interested parties
  • 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
  • 164.308(b)(1) Business Associate Contracts and Other Arrangements (Standard)

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Req 12: Information Security Policies

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 12.9.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.

Query this from an agent

The graph holds this control, the 24 it maps to, and the evidence behind each claim, over MCP and REST.