WithPCI Logo
WithPCI.com

11.2.1 Authorized and unauthorized wireless access points are managed as follows:

Original requirement from PCI DSS v4.0.1

Defined Approach Requirements

11.2.1 Authorized and unauthorized wireless access points are managed as follows:

  • The presence of wireless (Wi-Fi) access points is tested for,
  • All authorized and unauthorized wireless access points are detected and identified,
  • Testing, detection, and identification occurs at least once every three months.
  • If automated monitoring is used, personnel are notified via generated alerts.

Customized Approach Objective

Unauthorized wireless access points are identified and addressed periodically.

Applicability Notes

The requirement applies even when a policy exists that prohibits the use of wireless technology.

Methods used to meet this requirement must be sufficient to detect and identify both authorized and unauthorized devices, including unauthorized devices attached to devices that themselves are authorized.

Defined Approach Testing Procedures

11.2.1.a Examine policies and procedures to verify processes are defined for managing both authorized and unauthorized wireless access points with all elements specified in this requirement.

11.2.1.b Examine the methodology(ies) in use and the resulting documentation, and interview personnel to verify processes are defined to detect and identify both authorized and unauthorized wireless access points in accordance with all elements specified in this requirement.

11.2.1.c Examine wireless assessment results and interview personnel to verify that wireless assessments were conducted in accordance with all elements specified in this requirement.

11.2.1.d If automated monitoring is used, examine configuration settings to verify the configuration will generate alerts to notify personnel.

Purpose

Implementation and/or exploitation of wireless technology within a network are common paths for malicious users to gain unauthorized access to the network and cardholder data. Unauthorized wireless devices could be hidden within or attached to a computer or other system component. These devices could also be attached directly to a network port, to a network device such as a switch or router, or inserted as a wireless interface card inside a system component.

Even if a company has a policy prohibiting the use of wireless technologies, an unauthorized wireless device or network could be installed without the company's knowledge, allowing an attacker to enter the network easily and "invisibly." Detecting and removing such unauthorized access points reduces the duration and likelihood of such devices being leveraged for an attack.

Good Practice

The size and complexity of an environment will dictate the appropriate tools and processes to be used to provide sufficient assurance that a rogue wireless access point has not been installed in the environment.

For example, performing a detailed physical inspection of a single stand-alone retail kiosk in a shopping mall, where all communication components are contained within tamper-resistant and tamper-evident casings, may be sufficient to provide assurance that a rogue wireless access point has not been attached or installed. However, in an environment with multiple nodes (such as in a large retail store, call center, server room or data center), detailed physical inspection can be difficult. In this case, multiple methods may be combined, such as performing physical system inspections in conjunction with the results of a wireless analyzer.

Definitions

This is also referred to as rogue access point detection.

Examples

Methods that may be used include but are not limited to wireless network scans, physical/logical inspections of system components and infrastructure, network access control (NAC), or wireless IDS/IPS. NAC and wireless IDS/IPS are examples of automated monitoring tools.

purpose

Detect and identify all authorized and unauthorized wireless access points on a quarterly basis.

compliance strategies

  • Quarterly wireless scans
  • Wireless IDS/IPS deployment

typical policies

  • Wireless Security Policy
  • Wireless Scanning Procedures

common pitfalls

  • Missed rogue APs
  • No documentation of scans

type

Technical Control

difficulty

Moderate

key risks

  • Rogue wireless access compromising CDE

recommendations

  • Use enterprise wireless monitoring tools

Eligible SAQ

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