PAN must be made unreadable wherever it is stored, using one of these methods: (1) one-way hashes of the whole PAN based on strong cryptography; (2) truncation, where hashing may not substitute for the removed segment, and where hashed and truncated forms, or differing truncation formats, of the same PAN coexist in an environment, added controls must stop them being correlated to rebuild the original; (3) index tokens; (4) strong cryptography with supporting key-management processes and procedures. Applicability: covers PAN in primary storage (databases, flat files such as text files or spreadsheets) and non-primary storage (backups, audit, exception or troubleshooting logs); temporary files holding cleartext PAN during encryption and decryption are not prohibited. Customized approach objective: PAN held on any storage media is never readable in the clear.
This control maps to 40 controls across 20 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 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.