2.3: 1. For wireless environments connected to the CDE or transmitting account data, all wireless vendor defaults are changed at installation or are confirmed to be secure, including but not limited to: (a) Default wireless encryption keys, (b) Passwords on wireless access points, (c) SNMP defaults, (d) Any other security-related wireless vendor defaults.
  • Examine policies and procedures and interview responsible personnel to verify that processes are defined for wireless vendor defaults to either change them upon installation or to confirm them to be secure in accordance with all elements of this requirement.
  • Examine vendor documentation and observe a system administrator logging into wireless devices to verify:
  • • SNMP defaults are not used.
  • • Default passwords/passphrases on wireless access points are not used.
  • Examine vendor documentation and wireless configuration settings to verify other security-related wireless vendor defaults were changed, if applicable.

Description

Purpose

If wireless networks are not implemented with sufficient security configurations (including changing default settings), wireless sniffers can eavesdrop on the traffic, easily capture data and passwords, and easily enter and attack the network.

Good Practice

Wireless passwords should be constructed so that they are resistant to offline brute force attacks.

2.3: 2. For wireless environments connected to the CDE or transmitting account data, wireless encryption keys are changed as follows: (a) Whenever personnel with knowledge of the key leave the company or the role for which the knowledge was necessary, (b) Whenever a key is suspected of or known to be compromised.
  • Interview responsible personnel and examine key-management documentation to verify that wireless encryption keys are changed in accordance with all elements specified in this requirement.

Description

Purpose

Changing wireless encryption keys whenever someone with knowledge of the key leaves the organization or moves to a role that no longer requires knowledge of the key, helps keep knowledge of keys limited to only those with a business need to know.

Also, changing wireless encryption keys whenever a key is suspected or known to be comprised makes a wireless network more resistant to compromise.

Good Practice

This goal can be accomplished in multiple ways, including periodic changes of keys, changing keys via a defined “joiners-movers-leavers” (JML) process, implementing additional technical controls, and not using fixed pre-shared keys.

In addition, any keys that are known to be, or suspected of being, compromised should be managed in accordance with the entity’s incident response plan at Requirement 12.10.1.