Whenever PAN is sent through end-user messaging channels (e-mail, instant messaging, SMS, chat and the like), it must be protected with strong cryptography. Sending PAN this way should only happen where a documented business need exists, governed by the acceptable use policies set under Requirement 12.2.1. Applicability: the obligation still applies when a customer or other third party asks for PAN to be sent to them by messaging. If cardholder data arrives unsolicited over an insecure channel not meant for sensitive data, the entity may either bring that channel into CDE scope and secure it to PCI DSS, or delete the data and put measures in place to stop the channel being used for cardholder data. Objective under the customized approach: cleartext PAN cannot be read or captured from messages sent over end-user messaging channels.
This control maps to 28 controls across 18 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.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 28 it maps to, and the evidence behind each claim, over MCP and REST.