Extra requirement applying to service providers alone: if cryptographic keys for storing or transmitting account data are shared between the provider and its customers, it must document guidance on securely transmitting, storing and updating those keys and distribute that guidance to its customers. Applicability: applies only when the assessed entity is a service provider. Objective under the customized approach: customers receive suitable key management guidance whenever they are given shared keys.
This control maps to 13 controls across 8 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 3.7.9 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 13 it maps to, and the evidence behind each claim, over MCP and REST.