← PCI DSS 4.0.1 · Req 4 — Cryptography in transmission
4.2 — Strong cryptography for PAN transmitted over open, public networks
Requirement
PAN is protected with strong cryptography whenever it is transmitted over open, public networks: only trusted keys and certificates are accepted, certificates are valid and not expired, and PAN is never sent unprotected through end-user messaging technologies such as email or chat.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| HIPAA | 164.312(e)(1) | Transmission security (R/A) | encryption-in-transit |
| SOC 2 | CC6.6 | Boundary protection | encryption-in-transit |
| ISO 27001 | A.5.14 | Information transfer | encryption-in-transit |
| GLBA | 314.4(c)(3) | Encryption of customer information in transit and at rest | encryption-in-transit |
| NIST CSF 2.0 | PR.DS-02 | Confidentiality, integrity and availability of data in transit | encryption-in-transit |
| GDPR | Art.5(1)(f) | Integrity and confidentiality | encryption-in-transit |
| SOC 2 | CC6.7 | Restriction of information transmission, movement and removal | encryption-in-transit |
| ISO 27001 | A.8.24 | Use of cryptography | encryption-in-transit |