PCI DSS v4.0.1 has 12 principal requirements, grouped under six goals. Together they cover secure networks and systems, account data protection, vulnerability management, access control, monitoring and testing, and security policy. The detailed requirements that apply to you depend on your scope and how you validate.
Explore the 12 requirements
Filter by goal, then open a requirement to see its purpose and a few key references. These references are starting points. The standard itself holds the full wording, testing procedures, and applicability notes.
| Requirement | In plain terms | Key sub-requirements |
|---|---|---|
| 1. Install and maintain network security controls | Control what traffic can reach the cardholder data environment, and keep the rules documented and reviewed. | 1.2.3: Maintain an accurate network diagram 1.2.4: Maintain an accurate account data flow diagram 1.2.7: Review network security control configurations at least every six months 1.4: Control connections between trusted and untrusted networks |
| 2. Apply secure configurations to all system components | Harden every in-scope system, and change the passwords on vendor default accounts or remove or disable those accounts. | 2.2.1: Develop and maintain configuration standards 2.2.2: Manage vendor default accounts 2.3: Securely configure wireless environments |
| 3. Protect stored account data | Keep as little account data as possible, don’t keep sensitive authentication data after authorization (issuers have a limited exception), and make any stored PAN unreadable. | 3.2.1: Limit retention with defined policies and secure deletion 3.3.1: Do not retain sensitive authentication data after authorization 3.4.1: Mask PAN when displayed 3.5.1: Render stored PAN unreadable |
| 4. Protect cardholder data with strong cryptography during transmission over open, public networks | Encrypt PAN whenever it crosses a public network, and know which certificates and protocols you rely on. | 4.2.1: Use strong cryptography and trusted certificates 4.2.1.1: Maintain an inventory of trusted keys and certificates 4.2.2: Secure PAN sent through end-user messaging |
| 5. Protect all systems and networks from malicious software | Run active anti-malware protection, and defend people as well as machines against phishing. | 5.2.1: Deploy anti-malware except on components periodic evaluations find are not at risk from malware 5.3.2: Run periodic and real-time scans, or continuous behavioral analysis 5.4.1: Use processes and automated mechanisms to protect against phishing |
| 6. Develop and maintain secure systems and software | Build software securely, patch what you run, and protect web applications and payment pages. | 6.3.3: Install patches for critical vulnerabilities within one month of release 6.4.2: Protect public-facing web applications with an automated technical solution 6.4.3: Authorize, verify, and inventory payment page scripts 6.5: Manage changes to system components securely |
| 7. Restrict access to system components and cardholder data by business need to know | Give people and applications only the access their role requires, and review that access regularly. | 7.2.1: Define an access control model 7.2.4: Review user accounts and access at least every six months 7.2.5: Limit application and system account access |
| 8. Identify users and authenticate access to system components | Give every user a unique identity, use strong authentication, and require multi-factor authentication for non-console access into the CDE. | 8.2.1: Assign unique IDs 8.3.6: Set minimum password length and complexity 8.4.2: Require multi-factor authentication for all non-console access into the CDE 8.6: Manage application and system account authentication |
| 9. Restrict physical access to cardholder data | Control who can physically reach systems, media, and payment devices, and watch for device tampering. | 9.2.1: Control facility entry to the CDE 9.4: Secure, track, and destroy media containing cardholder data 9.5.1: Protect point-of-interaction devices from tampering and substitution |
| 10. Log and monitor all access to system components and cardholder data | Record who did what, review it automatically, and keep enough history to investigate an incident. | 10.2.1: Enable audit logs for in-scope components 10.4.1.1: Use automated mechanisms for audit log reviews 10.5.1: Retain audit log history for at least 12 months 10.7.2: Detect and respond to critical security control failures |
| 11. Test security of systems and networks regularly | Scan, penetration test, and watch for unauthorized change, including on payment pages. | 11.3.1: Run internal vulnerability scans at least every three months 11.3.2: Run ASV external vulnerability scans at least every three months 11.4: Perform and act on penetration tests 11.6.1: Detect unauthorized changes to payment pages |
| 12. Support information security with organizational policies and programs | Run security as a program: policies, scope reviews, training, vendor oversight, and incident response. | 12.5.2: Document and confirm PCI DSS scope at least every 12 months 12.6: Run a security awareness program 12.8: Manage third-party service provider risk 12.10: Be ready to respond to suspected and confirmed incidents |
The six goals behind the requirements
Build and maintain a secure network and systems
Requirements 1 and 2 cover network security controls and secure configurations. You document your network, review control configurations at least once every six months (1.2.7), and manage vendor default accounts (2.2.2).
Protect account data
Requirements 3 and 4 protect account data in storage and in transit. Most entities cannot keep sensitive authentication data after authorization, even if it is encrypted (3.3.1). Stored primary account number (PAN) must be unreadable (3.5.1), and PAN needs strong cryptography over open, public networks (4.2.1).
Maintain a vulnerability management program
Requirements 5 and 6 address malware, phishing, and software security. Critical patches go on within one month of release (6.3.3). Public-facing web applications sit behind an automated solution that detects and prevents web-based attacks (6.4.2).
Implement strong access control measures
Requirements 7, 8, and 9 limit who can reach systems and data. Access follows business need to know, and you review user access at least once every six months (7.2.4). Users get strong authentication, and physical controls protect facilities, media, and payment devices.
Regularly monitor and test networks
Requirements 10 and 11 confirm that controls keep working. You log activity, review those logs, scan for vulnerabilities, run penetration tests, and watch for unauthorized change.
Maintain an information security policy
Requirement 12 ties the program together. It covers policy, targeted risk analysis, scope confirmation, training, third-party oversight, and incident response.
How to tell what applies to you
Start with scope, because PCI DSS applies wherever account data is stored, processed, or transmitted. It also reaches systems that could affect the security of that data. Then check these four factors:
- Your validation route. An SAQ includes only the requirements for its eligible environment. Our guide on how to prepare covers this choice.
- Your role. Some requirements are marked for service providers only, such as 12.4.2. Appendix A1 adds requirements for multi-tenant service providers.
- Your approach. Most requirements can be met through the defined or customized approach. See our comparisons for the differences.
- The date. Requirements that were best practices until March 31, 2025 now count fully in assessments.
Merchant and service provider levels sit outside the standard. Payment brands define those levels and decide who must validate. Our page on who needs PCI DSS explains more.
High-interest requirements
Requirements 6.4.3 and 11.6.1: payment page scripts
These two requirements address skimming code that runs in a customer’s browser. Requirement 6.4.3 asks you to manage every payment page script loaded and executed in the browser:
- Confirm that each script is authorized.
- Assure the integrity of each script.
- Keep an inventory with a written business or technical justification for each script.
Requirement 11.6.1 adds a change- and tamper-detection mechanism. It alerts personnel to unauthorized changes to security-impacting HTTP headers and script contents as the browser receives them. It runs at least weekly, or at a frequency set in your targeted risk analysis. You do not need to install anything on customers’ devices.
Responsibility depends on how your page is built:
| Payment page scenario | You manage | Your provider manages |
|---|---|---|
| Merchant-posted or direct-post payment | Scripts on your webpages | Scripts it includes for its services |
| Embedded iframe | Scripts on your page that includes the iframe | Scripts inside its iframe |
| Redirection | Scripts on your page that includes the redirect | Scripts it includes for its services |
| Fully outsourced website | Nothing for these two requirements | Scripts it includes for its services |
SAQ A-EP, both versions of SAQ D, and the Report on Compliance (ROC) template include both requirements. SAQ A does not. Since January 2025, SAQ A has taken a different route. E-commerce merchants confirm that their site is not susceptible to script attacks that could affect their e-commerce systems.
Requirement 8.4.2: MFA into the CDE
Requirement 8.4.2 calls for multi-factor authentication on all non-console access into the CDE. Non-console access means logical access over a network interface. You can apply MFA at the network level or the system and application level, and you do not need both.
Requirement 8.4.3 separately covers remote access from outside your network that could access or impact the CDE. A user who connects remotely and then enters the CDE authenticates with MFA twice. Requirement 8.5.1 adds design rules, including at least two different factor types and protection against replay attacks. Using two passwords does not count as MFA.
The 8.4.2 exclusions are narrow. They cover automated application and system accounts, point-of-sale accounts with access to one card number at a time, and accounts using only phishing-resistant factors.
Requirement 8.3.6: passwords
Where passwords or passphrases serve as authentication factors, they need at least 12 characters and both letters and numbers. A system that cannot support 12 characters may use a minimum of eight. Application and system accounts follow section 8.6 instead.
Rotation depends on how you authenticate. If a password is the only factor, Requirement 8.3.9 gives you two options. Change it at least once every 90 days, or dynamically analyze each account’s security posture. That rule does not apply to in-scope system components where MFA is used.
Requirement 10: logging and log review
Audit logs must be active for all system components and cardholder data (10.2.1). Each entry records the user, event type, date and time, success or failure, origin, and affected resource (10.2.2).
Review happens at two speeds. Security events, and logs from systems that store, process, or transmit account data, critical systems, and security-function systems, get reviewed at least daily (10.4.1), using automated mechanisms (10.4.1.1). Logs from other components are reviewed at a frequency set by your targeted risk analysis (10.4.2, 10.4.2.1).
You keep at least 12 months of history, with the latest three months immediately available (10.5.1). Requirement 10.7.2 also calls for prompt detection of failures in critical security controls.
Requirements 1.2.3 and 1.2.4: network and data flow diagrams
These diagrams do different jobs, and you need both. The network diagram (1.2.3) shows all connections between the CDE and other networks, including wireless networks. The data flow diagram (1.2.4) shows all account data flows across systems and networks, and you update it as your environment changes.
PCI SSC’s guidance says the data flow diagram should reconcile with the network diagram. It should also cover every acceptance channel and include file backups. A current technical or topological tool can serve in place of a hand-drawn diagram.
Other topics readers often ask about
| Topic | Requirement | What it asks |
|---|---|---|
| Masking | 3.4.1 | Display no more than the BIN and last four digits, except to staff with a business need |
| Key management | 3.6, 3.7 | Protect cryptographic keys and follow key-management procedures |
| Physical security | 9.2.1, 9.4.6 | Control facility entry and destroy hard-copy data when no longer needed |
| Vulnerability scans | 11.3.1, 11.3.2 | Run internal scans and external Approved Scanning Vendor (ASV) scans at least every three months |
| Penetration testing | 11.4.1 to 11.4.3 | Follow a defined methodology, and test internally and externally at least every 12 months |
| Awareness training | 12.6.3 | Train personnel upon hire and at least once every 12 months |
For the recurring tasks in one place, see our guide to maintaining compliance.
Frequently asked questions
Work with RSI Security
RSI Security is a PCI Qualified Security Assessor (QSA) company and an Approved Scanning Vendor (ASV). It performs PCI DSS assessments and quarterly ASV scans. Organizations that need help with scoping or readiness can work with RSI Security through a separate advisory engagement. RSI Security provides either advisory or assessment to a given client, never both.
Schedule a PCI DSS assessment · Talk to an advisor about readiness
Sources
- PCI DSS v4.0.1 (Section 1, Table 1: Principal PCI DSS Requirements)
- PCI DSS v4.0.1 (Requirements 1.2.3, 1.2.4, 3.3.1, 3.4.1, 3.5.1, 4.2.1, 6.3.3, 6.4.2, and 6.4.3)
- PCI DSS v4.0.1 (Requirements 8.3.6, 8.3.9, 8.4.2, 8.4.3, and 8.5.1)
- PCI DSS v4.0.1 (Requirements 10.2.1, 10.2.2, 10.4.1, 10.4.1.1, 10.4.2, 10.5.1, 10.7.2, 11.3.1, 11.3.2, 11.4, and 11.6.1)
- Guidance for PCI DSS Requirements 6.4.3 and 11.6.1 (r1, April 2025) (Table 3: Applicability and Responsibility)
- PCI DSS v4.0.1 SAQ A (r1, January 2025) (Eligibility Criteria and Summary of Changes)
- PCI QSA Program Guide v4.1 (Section 2.1: Participating Payment Brands)
