PCI DSS v4.0
Payment Card Industry Data Security Standard for protecting cardholder data
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (12)
Req 1 - Network Security Controls
Install and maintain network security controls
| Code | Title |
|---|---|
| PCI-1.1 | Processes and mechanisms for network security controls are defined and understood |
| PCI-1.2 | Network security controls are configured and maintained |
| PCI-1.3 | Network access to and from the cardholder data environment is restricted |
| PCI-1.4 | Network connections between trusted and untrusted networks are controlled |
| PCI-1.5 | Risks to the CDE from computing devices connecting to untrusted networks are mitigated |
Req 10 - Log and Monitor
Log and monitor all access to system components and cardholder data
| Code | Title |
|---|---|
| PCI-10.1 | Processes for logging and monitoring access are defined and understood |
| PCI-10.2 | Audit logs are implemented to support detection of anomalies and suspicious activity |
| PCI-10.3 | Audit logs are protected from destruction and unauthorized modifications |
| PCI-10.4 | Audit logs are reviewed to identify anomalies or suspicious activity |
| PCI-10.5 | Audit log history is retained and available for analysis |
| PCI-10.6 | Time-synchronization mechanisms support consistent time settings |
| PCI-10.7 | Failures of critical security control systems are detected and reported promptly |
Req 11 - Test Security
Test security of systems and networks regularly
| Code | Title |
|---|---|
| PCI-11.1 | Processes for regular testing of security are defined and understood |
| PCI-11.2 | Wireless access points are identified and monitored |
| PCI-11.3 | External and internal vulnerabilities are regularly identified and addressed |
| PCI-11.4 | External and internal penetration testing is regularly performed |
| PCI-11.5 | Network intrusions and unexpected file changes are detected and responded to |
| PCI-11.6 | Unauthorized changes on payment pages are detected and responded to |
Req 12 - Organizational Policies
Support information security with organizational policies and programs
| Code | Title |
|---|---|
| PCI-12.1 | A comprehensive information security policy is known and current |
| PCI-12.10 | Security incidents and vulnerabilities are responded to promptly |
| PCI-12.2 | Acceptable use policies for end-user technologies are defined and implemented |
| PCI-12.3 | Risks to the cardholder data environment are formally identified and managed |
| PCI-12.4 | PCI DSS compliance is managed |
| PCI-12.5 | PCI DSS scope is documented and validated |
| PCI-12.6 | Security awareness education is an ongoing activity |
| PCI-12.7 | Personnel are screened to reduce risks from insider threats |
| PCI-12.8 | Risk to information assets from third-party service providers is managed |
| PCI-12.9 | Third-party service providers support PCI DSS compliance of their customers |
Req 2 - Secure Configuration
Apply secure configurations to all system components
| Code | Title |
|---|---|
| PCI-2.1 | Processes and mechanisms for secure configuration are defined and understood |
| PCI-2.2 | System components are configured and managed securely |
| PCI-2.3 | Wireless environments are configured and managed securely |
Req 3 - Protect Stored Account Data
Protect stored account data
| Code | Title |
|---|---|
| PCI-3.1 | Processes and mechanisms for protecting stored account data are defined |
| PCI-3.2 | Storage of account data is kept to a minimum |
| PCI-3.3 | Sensitive authentication data is not stored after authorization |
| PCI-3.4 | Access to displays of full PAN and ability to copy cardholder data are restricted |
| PCI-3.5 | Primary account number is secured wherever it is stored |
| PCI-3.6 | Cryptographic keys used to protect stored account data are secured |
| PCI-3.7 | Where cryptography is used to protect stored account data, key management processes are defined |
Req 4 - Protect Data in Transit
Protect cardholder data with strong cryptography during transmission
| Code | Title |
|---|---|
| PCI-4.1 | Processes for protecting cardholder data in transit are defined and understood |
| PCI-4.2 | PAN is protected with strong cryptography during transmission |
Req 5 - Malware Protection
Protect all systems and networks from malicious software
| Code | Title |
|---|---|
| PCI-5.1 | Processes for protecting against malicious software are defined and understood |
| PCI-5.2 | Malicious software is prevented or detected and addressed |
| PCI-5.3 | Anti-malware mechanisms and processes are active, maintained, and monitored |
| PCI-5.4 | Anti-phishing mechanisms protect users against phishing attacks |
Req 6 - Secure Development
Develop and maintain secure systems and software
| Code | Title |
|---|---|
| PCI-6.1 | Processes for developing secure systems and software are defined and understood |
| PCI-6.2 | Bespoke and custom software are developed securely |
| PCI-6.3 | Security vulnerabilities are identified and addressed |
| PCI-6.4 | Public-facing web applications are protected against attacks |
| PCI-6.5 | Changes to all system components are managed securely |
Req 7 - Restrict Access
Restrict access to system components and cardholder data by business need to know
| Code | Title |
|---|---|
| PCI-7.1 | Processes for restricting access to cardholder data are defined and understood |
| PCI-7.2 | Access to system components and data is appropriately defined and assigned |
| PCI-7.3 | Access to system components and data is managed via an access control system |
Req 8 - Identify Users and Authenticate Access
Identify users and authenticate access to system components
| Code | Title |
|---|---|
| PCI-8.1 | Processes for identification and authentication are defined and understood |
| PCI-8.2 | User identification and related accounts are strictly managed |
| PCI-8.3 | Strong authentication for users and administrators is established and managed |
| PCI-8.4 | Multi-factor authentication is implemented for access into the CDE |
| PCI-8.5 | Multi-factor authentication systems are configured to prevent misuse |
| PCI-8.6 | Use of application and system accounts is strictly managed |
Req 9 - Restrict Physical Access
Restrict physical access to cardholder data
| Code | Title |
|---|---|
| PCI-9.1 | Processes for restricting physical access to cardholder data are defined |
| PCI-9.2 | Physical access controls manage entry into facilities with cardholder data |
| PCI-9.3 | Physical access for personnel and visitors is authorized and managed |
| PCI-9.4 | Media with cardholder data is securely stored, accessed, distributed, and destroyed |
| PCI-9.5 | Point-of-interaction devices are protected from tampering and unauthorized substitution |
Maps to 577 other frameworks
Frequently Asked Questions
What is PCI DSS v4.0?
PCI DSS v4.0 is a compliance framework from International with 12 domains and 63 controls. Payment Card Industry Data Security Standard for protecting cardholder data It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does PCI DSS v4.0 have?
PCI DSS v4.0 has 63 controls organised across 12 domains. The largest domains are Req 12 - Organizational Policies (10 controls), Req 10 - Log and Monitor (7 controls), Req 3 - Protect Stored Account Data (7 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does PCI DSS v4.0 map to?
PCI DSS v4.0 maps to 577 other compliance frameworks. The top mapping partners are ASD Information Security Manual (ISM) (44% coverage), CSA CCM v4 (43% coverage), AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) (43% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with PCI DSS v4.0 compliance?
Start your PCI DSS v4.0 compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about PCI DSS v4.0 requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 63 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 692 frameworks.
Get Started Free →Free forever — no credit card required