1.3.3 NSCs are installed between all wireless networks and the CDE, regardless of whether the wireless network is a CDE
Defined Approach Requirements
1.3.3 NSCs are installed between all wireless networks and the CDE, regardless of whether the wireless network is a CDE, such that:
- All wireless traffic from wireless networks into the CDE is denied by default.
- Only wireless traffic with an authorized business purpose is allowed into the CDE.
Customized Approach Objective
Unauthorized traffic cannot traverse network boundaries between any wireless networks and wired environments in the CDE.
Defined Approach Testing Procedures
1.3.3 Examine configuration settings and network diagrams to verify that NSCs are implemented between all wireless networks and the CDE, in accordance with all elements specified in this requirement.
Purpose
The known (or unknown) implementation and exploitation of wireless technology within a network is a common path for malicious individuals to gain access to the network and account data. If a wireless device or network is installed without the entity's knowledge, a malicious individual could easily and "invisibly" enter the network. If NSCs do not restrict access from wireless networks into the CDE, malicious individuals that gain unauthorized access to the wireless network can easily connect to the CDE and compromise account information.
purpose
Prevent unauthorized access to the CDE from wireless networks.
whats required for compliance
- NSCs between all wireless and CDE segments.
- Default deny for wireless-to-CDE traffic.
- Allow only justified exceptions.
compliance strategies
- Wireless DMZ
- Segmentation firewalls
- Wireless access control policies
typical policies procedures
- Wireless Security Policy
- Rogue AP Detection Process
common pitfalls failures
- Shared credentials for guest/Wi-Fi
- Missing NAC for IoT devices
type
Technical Control
difficulty
High
key risks
- Rogue APs bridging networks
product vendor recommendations
- Use wireless intrusion prevention (Aruba)
Eligible SAQ
- SAQ-A-EP
- SAQ-B-IP
- 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