WithPCI Logo
WithPCI.com
Original requirement from PCI DSS v4.0.1

# 4.2.1.2 Wireless networks transmitting PAN or connected to the CDE use industry best practices to implement strong cryptography for authentication and transmission.

Defined Approach Requirements

4.2.1.2 Wireless networks transmitting PAN or connected to the CDE use industry best practices to implement strong cryptography for authentication and transmission.

Customized Approach Objective

Cleartext PAN cannot be read or intercepted from wireless network transmissions.

Defined Approach Testing Procedures

4.2.1.2 Examine system configurations to verify that wireless networks transmitting PAN or connected to the CDE use industry best practices to implement strong cryptography for authentication and transmission.

Purpose

Since wireless networks do not require physical media to connect, it is important to establish controls limiting who can connect and what transmission protocols will be used. Malicious users use free and widely available tools to eavesdrop on wireless communications. Use of strong cryptography can help limit disclosure of sensitive information across wireless networks. Wireless networks present unique risks to an organization; therefore, they must be identified and protected according to industry requirements. Strong cryptography for authentication and transmission of PAN is required to prevent malicious users from gaining access to the wireless network or utilizing wireless networks to access other internal networks or data.

Good Practice

Wireless networks should not permit fallback or downgrade to an insecure protocol or lower encryption strength that does not meet the intent of strong cryptography.

Further Information

Review the vendor's specific documentation for more details on the choice of protocols, configurations, and settings related to cryptography.

purpose

Ensure trusted keys and certificates are used for secure transmission.

compliance strategies

  • Certificate management
  • Automated certificate renewal and monitoring

typical policies

  • Certificate Management Policy

common pitfalls

  • Expired or self-signed certificates
  • Weak key management

type

Technical Control

difficulty

Moderate

key risks

  • Man-in-the-middle attacks

recommendations

  • Use public CA-signed certificates and monitor expiration

Eligible SAQ

  • SAQ-C
  • SAQ-C-VT
  • 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