2.1 Secure configuration processes and roles
Requirement 2.1 asks for current, known policies and procedures for applying secure configurations to all system components, and documented roles for the people who build and harden systems.
Requirement 2 Secure configurations
Requirement 2 covers secure configuration and hardening of every system component, including vendor defaults and wireless environments. Each page covers one second-level requirement.
2.2 System component configuration and management
Requirement 2.2 is the hardening requirement: configuration standards for every system component, vendor default accounts, one primary function per server or isolation, disabling unnecessary services, and strong cryptography for non-console admin access.
2.3 Wireless environment configuration
Requirement 2.3 covers wireless environments connected to the CDE or transmitting account data: changing vendor defaults at installation and changing wireless encryption keys when people leave or keys are compromised.
