Global

PCI DSS: Requirements Overview

Requirements Overview [Req 1-12]

Rule: PCI DSS contains 12 high-level requirements organized into 6 control objectives. Each requirement has detailed sub-requirements that must be implemented.

Control Objectives and Requirements

ObjectiveRequirements
Build and Maintain a Secure Network and Systems1, 2
Protect Account Data3, 4
Maintain a Vulnerability Management Program5, 6
Implement Strong Access Control Measures7, 8, 9
Regularly Monitor and Test Networks10, 11
Maintain an Information Security Policy12

Requirement 1: Network Security Controls

Install and maintain network security controls.

Sub-requirementFocus
1.1Processes and mechanisms defined and understood
1.2Network security controls configured and maintained
1.3Network access to/from CDE restricted
1.4Network connections between trusted and untrusted controlled
1.5Risks from untrusted networks mitigated

Requirement 2: Secure Configurations

Apply secure configurations to all system components.

Sub-requirementFocus
2.1Processes and mechanisms defined and understood
2.2System components configured and managed securely
2.3Wireless environments configured and managed securely

Requirement 3: Protect Stored Account Data

Protect stored account data.

Sub-requirementFocus
3.1Processes and mechanisms defined and understood
3.2Storage of account data minimized
3.3SAD not stored after authorization
3.4PAN masked when displayed
3.5PAN secured wherever stored
3.6Cryptographic keys managed
3.7Where cryptography protects PAN, keys managed

Requirement 4: Protect Data in Transit

Protect cardholder data with strong cryptography during transmission over open, public networks.

Sub-requirementFocus
4.1Processes and mechanisms defined and understood
4.2PAN protected with strong cryptography during transmission

Requirement 5: Protect from Malware

Protect all systems and networks from malicious software.

Sub-requirementFocus
5.1Processes and mechanisms defined and understood
5.2Malicious software prevented or detected and addressed
5.3Anti-malware mechanisms active, maintained, monitored
5.4Anti-phishing mechanisms protect against phishing

Requirement 6: Develop Secure Systems

Develop and maintain secure systems and software.

Sub-requirementFocus
6.1Processes and mechanisms defined and understood
6.2Bespoke and custom software developed securely
6.3Security vulnerabilities identified and addressed
6.4Public-facing web applications protected
6.5Changes managed securely

Requirement 7: Restrict Access

Restrict access to system components and cardholder data by business need to know.

Sub-requirementFocus
7.1Processes and mechanisms defined and understood
7.2Access to system components and data appropriately defined
7.3Access to system components and data managed via access control systems

Requirement 8: Identify and Authenticate

Identify users and authenticate access to system components.

Sub-requirementFocus
8.1Processes and mechanisms defined and understood
8.2User identification and accounts managed
8.3Strong authentication established
8.4MFA implemented for CDE access
8.5MFA systems configured properly
8.6Application/system accounts managed

Requirement 9: Physical Security

Restrict physical access to cardholder data.

Sub-requirementFocus
9.1Processes and mechanisms defined and understood
9.2Physical access controls manage entry
9.3Physical access for personnel and visitors authorized
9.4Media with cardholder data securely stored, accessed, distributed, destroyed
9.5POI devices protected from tampering and substitution

Requirement 10: Log and Monitor

Log and monitor all access to system components and cardholder data.

Sub-requirementFocus
10.1Processes and mechanisms defined and understood
10.2Audit logs implemented
10.3Audit logs protected
10.4Audit logs reviewed
10.5Audit log history retained
10.6Time-synchronization technology
10.7Failures of critical security systems detected and responded to

Requirement 11: Test Security

Test security of systems and networks regularly.

Sub-requirementFocus
11.1Processes and mechanisms defined and understood
11.2Wireless access points identified and monitored
11.3External and internal vulnerabilities identified and addressed
11.4External and internal penetration testing performed
11.5Network intrusions and file changes detected and responded to
11.6Unauthorized changes on payment pages detected

Requirement 12: Security Policies

Support information security with organizational policies and programs.

Sub-requirementFocus
12.1Information security policy established
12.2Acceptable use policies defined
12.3Risks to CDE formally identified, evaluated, managed
12.4PCI DSS compliance managed
12.5PCI DSS scope documented and validated
12.6Security awareness education
12.7Personnel screened
12.8Third-party service provider relationships managed
12.9Service providers acknowledge responsibilities
12.10Incidents detected and responded to

Citation

PCI DSS v4.0.1 Requirements

Contains public sector information licensed under the Open Government Licence v3.0 where applicable. This is not legal advice. Always refer to official sources for authoritative text.

llms.txt