The entity must keep an up-to-date inventory of its own trusted keys and certificates that protect PAN while it is transmitted. A useful inventory records key custodians, key strength, protocols, algorithms and expiry dates, and for certificates the issuing CA and expiration date, so the entity can react quickly when a weakness is found in encryption software, certificates or algorithms. Applicability: this was advisory only up to 31 March 2025 and is now required and fully assessed. Objective under the customized approach: every key and certificate that protects PAN in transit is known and confirmed as trusted. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 26 controls across 16 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 4.2.1.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 26 it maps to, and the evidence behind each claim, over MCP and REST.