PCI DSS 4.0
Req 4: Protect Cardholder Data in Transit

PCI DSS 4.0 4.2.1.2: 4.2.1.2 Wireless networks use strong cryptography

Any wireless network that either carries PAN or links into the CDE must follow recognised industry practice to implement strong cryptography for both authentication and transmission. Wireless setups should never drop back to a weaker protocol or to encryption strength below what strong cryptography requires; vendor documentation informs protocol and setting choices. Applicability: applies to every entity with such wireless networks; no further notes. Objective under the customized approach: cleartext PAN cannot be read or captured from wireless traffic.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 26 controls across 15 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 5 controls

CIS Controls v8 · 2 controls

  • CIS-12.6 Use of Secure Network Management and Communication Protocols
  • CIS-3.10 Encrypt Sensitive Data in Transit

CMMC 2.0 · 2 controls

HIPAA Security Rule · 2 controls

ISO 27001:2022 · 2 controls

  • 8.20 Networks security
  • 8.24 Use of cryptography

ISO 27701:2019 · 2 controls

  • 6.10.2 Information transfer
  • 6.7.1 Cryptographic controls

NIST SP 800-66 Rev 2 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal
  • ANSSI-HYG-20 Secure Wi-Fi Access Networks and Separate Usage

FedRAMP High · 1 control

FedRAMP Moderate · 1 control

ISO 27002:2022 · 1 control

  • 8.21 Security of network services
  • NIST-CSF-PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected

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.

Other controls in Req 4: Protect Cardholder Data in Transit

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 4.2.1.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.

Query this from an agent

The graph holds this control, the 26 it maps to, and the evidence behind each claim, over MCP and REST.