Service providers only: TPSPs must give customers written agreements containing an acknowledgment that the TPSP answers for protecting account data it holds, stores, processes or transmits for the customer, or to whatever extent it could affect the cardholder data or sensitive authentication data of that customer. Applicability: applies only when the assessed entity is a service provider. The wording depends on the service and allocated responsibilities and need not copy the requirement text. An AOC, website declaration, policy statement, responsibility matrix or any evidence sitting outside a written agreement does not qualify as the acknowledgment. Customized approach objective: each TPSP formally accepts, toward its customers, its security obligations.
This control maps to 16 controls across 10 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
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.
PCI DSS 4.0 12.9.1 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.
The graph holds this control, the 16 it maps to, and the evidence behind each claim, over MCP and REST.