Where encryption applied to a whole disk or partition, instead of encrypting at database file, column or field level, is what makes PAN unreadable, it may be relied on only (1) on removable electronic media, OR (2) on non-removable electronic media where PAN is additionally made unreadable by another mechanism that satisfies Requirement 3.5.1. Applicability: covers any encryption that automatically presents cleartext PAN when a system runs without a specific user request; such encryption may remain but cannot be the sole protection, so stored PAN also needs truncation or data-level encryption; full disk encryption suits only removable media; data centre media such as hot-swappable drives and bulk tape backups count as non-removable; implementations still have to satisfy every remaining encryption and key-management rule in the standard; for card issuers and issuing-service firms it does not apply to PAN accessed for real-time transaction processing but does apply to PAN stored for other purposes. Objective under the customized approach: encrypted PAN is decrypted only when a legitimate business need to access it exists. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 40 controls across 15 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.5.1.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.
The graph holds this control, the 40 it maps to, and the evidence behind each claim, over MCP and REST.