4.2.2 PAN is secured with strong cryptography whenever it is sent via end-user messaging technologies.
Defined Approach Requirements
4.2.2 PAN is secured with strong cryptography whenever it is sent via end-user messaging technologies.
Customized Approach Objective
Cleartext PAN cannot be read or intercepted from transmissions using end-user messaging technologies.
Applicability Notes
This requirement also applies if a customer, or other third party, requests that PAN is sent to them via end-user messaging technologies.
There could be occurrences where an entity receives unsolicited cardholder data via an insecure communication channel that was not intended for transmissions of sensitive data. In this situation, the entity can choose to either include the channel in the scope of their CDE and secure it according to PCI DSS or delete the cardholder data and implement measures to prevent the channel from being used for cardholder data.
Defined Approach Testing Procedures
4.2.2.a Examine documented policies and procedures to verify that processes are defined to secure PAN with strong cryptography whenever sent over end-user messaging technologies.
4.2.2.b Examine system configurations and vendor documentation to verify that PAN is secured with strong cryptography whenever it is sent via end-user messaging technologies.
Purpose
End-user messaging technologies typically can be easily intercepted by packet-sniffing during delivery across internal and public networks.
Good Practice
The use of end-user messaging technology to send PAN should only be considered where there is a defined business need and should be controlled through the Acceptable Use Policies for end-user technologies defined by the entity according to Requirement 12.2.1.
Examples
E-mail, instant messaging, SMS, and chat are examples of the type of end-user messaging technology that this requirement refers to.
purpose
Ensure PAN is not sent via end-user messaging technologies (e.g., email, SMS, chat) unless rendered unreadable.
compliance strategies
- Block PAN in messaging systems
- DLP monitoring
- User training
typical policies
- Messaging Security Policy
- Data Loss Prevention Policy
common pitfalls
- Unmonitored messaging channels
- User circumvention of policy
type
Technical/Process Control
difficulty
Moderate
key risks
- Accidental or intentional data leakage
recommendations
- Deploy DLP solutions and conduct user awareness campaigns
Eligible SAQ
- SAQ-A-EP
- SAQ-C
- SAQ-D MERCHANT
- SAQ-D SERVICE PROVIDER
Your perspective on this PCI DSS requirement matters! Share your implementation experiences, challenges, or questions below. Your insights help other organizations improve their compliance journey and build a stronger security community.Comment Policy