Course contentsShow
← Security
Lesson 2572 of 3,05249. Compliance and RegulatoryFree lesson

Requirement 2: Secure Configurations

Applying secure configurations to all system components, removing vendor defaults, and maintaining configuration standards.

Requirement 2: Secure Configurations

What you'll learn: How PCI-DSS Requirement 2 mandates hardening all systems by replacing insecure vendor defaults with secure, documented configurations to protect cardholder data.

The Problem with Defaults

When you buy a new router, database, or application, it arrives with vendor default settings: default passwords like "admin/admin," pre-configured services you don't need, and sample accounts for testing. Attackers know these defaults — they're published in manuals and exploit databases.

Think of it like moving into an apartment where the previous tenant's keys still work. You wouldn't leave those locks unchanged, yet many organizations deploy systems without changing their "factory settings."

Core Requirements of Secure Configuration

PCI-DSS Requirement 2 mandates that you:

  1. Remove or disable all vendor-supplied defaults before deploying systems that store, process, or transmit cardholder data
  2. Develop configuration standards for all system components that address known security vulnerabilities
  3. Enable only necessary services, protocols, and daemons — if you don't need it, turn it off
  4. Document and implement secure settings for all security parameters

This applies to operating systems, network devices, databases, web servers, applications — everything in your cardholder data environment (CDE).

Configuration Standards in Practice

Your secure configuration standards should specify: hardened OS settings, disabled unnecessary accounts, encrypted communication protocols only, documented security parameters, and regular configuration reviews. These standards must be version-controlled and approved through your change management process (Requirement 6's territory, but the configurations themselves live here).

Regular audits verify systems remain configured securely — configuration drift is real, and systems can revert or be misconfigured during maintenance.

Key Takeaway: Requirement 2 eliminates low-hanging fruit for attackers by replacing insecure defaults with hardened, documented configurations across every system component that touches cardholder data.