← NIST CSF 2.0 · PROTECT — Data Security
PR.DS-02 — Confidentiality, integrity and availability of data in transit
critical
encryption-in-transitnetwork-security
Requirement
The confidentiality, integrity and availability of data in transit are protected.
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.
Required element 1 — any one of
in transittransmissionnetwork
Required element 2 — any one of
tlshttpsencryptvpnmtls
Supporting terms — specificity signals
tls 1.2tls 1.3hstscertificatecipher suiteinternal traffic
Contradiction markers
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
http only
unencrypted traffic
tls 1.0
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| SOC 2 | CC6.6 | Boundary protection | network-security encryption-in-transit |
| ISO 27001 | A.5.14 | Information transfer | encryption-in-transit |
| ISO 27001 | A.8.21 | Security of network services | network-security |
| ISO 27001 | A.8.22 | Segregation of networks | network-security |
| PCI DSS 4.0.1 | 1.2 | Network security control configuration and review | network-security |
| PCI DSS 4.0.1 | 1.3 | Restrict network access to and from the cardholder data environment | network-security |
| PCI DSS 4.0.1 | 1.4 | Controls between trusted and untrusted networks | network-security |
| PCI DSS 4.0.1 | 4.2 | Strong cryptography for PAN transmitted over open, public networks | encryption-in-transit |