PCI v4.0 - 2.2.1: Configuration Standards Are Developed, Implemented, and Maintained
PCI Requirement 2.2 - Develop Configuration Standards for all System Components
PCI Requirement 2.2.1 - Implement Only One Primary Function Per Server
PCI Requirement 2.1 - Always Change Vendor-Supplied Defaults
PCI Requirement 2.2.2 - Enable Only Necessary Services, Protocols and Daemons
Introduction to PCI Requirement 2
PCI Requirement 2.2.5 - Remove all Unnecessary Functionality
PCI Requirement 2.1.1 - Change all Wireless Vendor Defaults
PCI DSS Req 2.2.1 Implement One Function per Server
PCI DSS Requirement 1.2.1 Restrict Traffic to that which is Necessary
PCI Requirement 6.1 – Establish a Process to Identify Security Vulnerabilities
PCI DSS Requirement 1.2.2 Secure and Synchronize Router Configuration Files
PCI Requirement 2.2.3 - Implement Additional Security Features
PCI Requirement 6.5.2 – Buffer Overflow
PCI Requirement 5.1.2 – Perform Evaluations to Identify & Evaluate Evolving Malware Threats
PCI Requirement 2.5 - Ensure Security Policies Are Known to All Affected Parties
PCI Requirement 6.3.1 – Remove Development and Test Accounts, User IDs, and Passwords Before Release
PCI Requirement 3.3 Mask PAN when Displayed
PCI Requirement 5.2 – Ensure Anti-Virus Mechanisms are Current, Perform Scans, & Generate Audit Logs
PCI DSS Requirement 1.3.6 Segregate the CDE from the DMZ