Skip to content
Financial ServicesInternational

PCI DSS v4.0

What is PCI DSS v4.0?

PCI DSS v4.0 is the global security standard for organisations that store, process, or transmit cardholder data, published by the PCI Security Standards Council. Version 4.0, released in March 2022 with full enforcement from 31 March 2025, introduced a customised approach to validation, expanded multi-factor authentication requirements, and added 64 new requirements. It contains 249 controls across 12 requirement areas. It comprises 280 controls organised across 16 domains, published by PCI Security Standards Council, and applies in International.

What PCI DSS v4.0 asks an organisation to do

What is PCI DSS v4.0?

The Payment Card Industry Data Security Standard (PCI DSS) v4.0 is the mandatory security standard for any organisation that stores, processes, or transmits payment card data from the major card brands (Visa, Mastercard, American Express, Discover, JCB). Published by the PCI Security Standards Council, it replaced version 3.2.1 with full enforcement from 31 March 2025. Compliance is validated through Self-Assessment Questionnaires (SAQs) or on-site assessments by Qualified Security Assessors (QSAs), depending on transaction volume.

What are the 12 PCI DSS requirements?

PCI DSS v4.0 is organised into 12 top-level requirements grouped under 6 goals:

  1. Install and Maintain Network Security Controls: Implement and maintain firewall/security configurations to protect cardholder data
  2. Apply Secure Configurations: Do not use vendor-supplied defaults for system passwords and security parameters
  3. Protect Stored Account Data: Protect stored cardholder data through encryption, masking, and retention policies
  4. Protect Cardholder Data in Transit: Encrypt transmission of cardholder data across open, public networks
  5. Protect from Malicious Software: Protect all systems and networks from malicious software
  6. Develop Secure Systems and Software: Develop and maintain secure systems and applications
  7. Restrict Access by Business Need: Restrict access to cardholder data to authorised personnel only
  8. Identify Users and Authenticate Access: Identify and authenticate access to system components
  9. Restrict Physical Access: Restrict physical access to cardholder data and systems
  10. Log and Monitor All Access: Log and monitor all access to cardholder data and network resources
  11. Test Security Regularly: Regularly test security systems and processes including vulnerability scans and penetration tests
  12. Maintain an Information Security Policy: Maintain a policy that addresses information security for all personnel

What changed in PCI DSS v4.0?

Version 4.0 introduced several major changes from v3.2.1:

  • Customised Approach: A new validation method allowing organisations to meet security objectives using controls different from those in the defined approach, provided they demonstrate equivalent security
  • Expanded MFA: Multi-factor authentication now required for all access to the cardholder data environment, not just remote access
  • Targeted Risk Analysis: Organisations must perform targeted risk analyses to determine the frequency of certain periodic activities
  • Enhanced Authentication: Increased password length requirements (minimum 12 characters) and stricter authentication controls
  • 64 New Requirements: Added requirements addressing emerging threats including phishing, e-commerce skimming, and automated security testing

Map this against the frameworks you already hold

The compliance knowledge graph holds cross-framework control mappings for hundreds of standards, including the ones you are likely to be certified against already.

Browse the framework graph →

Key controls, from the 280 PCI DSS v4.0 defines

IDControl
1.1Network Security Controls Defined
3.1Account Data Protection
4.1Transmission Encryption
6.1Secure Development
8.1User Identification
8.4Multi-Factor Authentication
11.1Security Testing
12.1Information Security Policy

The 16 domains PCI DSS v4.0 groups its controls into

Req 12: Information Security Policies
Req 11: Test Security Regularly
Req 10: Logging and Monitoring
Req 9: Restrict Physical Access
Req 8: Identify and Authenticate Users
Req 7: Restrict Access by Need to Know
Req 6: Secure Systems and Software
Req 5: Anti-Malware

Where PCI DSS v4.0 overlaps with the standards you already hold

Step-by-step implementation of PCI DSS v4.0

More PCI DSS v4.0 comparisons

Analysis of PCI DSS v4.0

How to Execute PCI DSS v4.0 Requirements 8.2 User Authentication Integration with NIST SP 800-63B Digital Identity Guidelines for Cloud Payment ProcessingPCI DSS v4.0 Requirement 8.2 mandates multi-factor authentication for all access to cardholder data environments, but implementing this alongside NIST SP 800-63B guidelines creates additional complexity for cloud-based payment processors. This integration approach addresses authentication assurance levels while maintaining PCI compliance for distributed payment infrastructure.
How to Execute PCI DSS v4.0 Multi-Party Authentication Requirements with NIST SP 800-63B Identity Verification for Enterprise Payment Gateway OperationsPCI DSS v4.0 introduces enhanced multi-party authentication requirements that must align with NIST SP 800-63B digital identity guidelines for comprehensive payment security. This integration creates a robust framework for enterprise payment gateways handling high-volume card transactions while meeting both regulatory compliance and operational security objectives.
How to Execute PCI DSS v4.0 Cryptographic Requirements Integration with FIPS 140-2 Validation for Enterprise Payment Processing SecurityPCI DSS v4.0 introduces enhanced cryptographic requirements that must align with FIPS 140-2 validated modules for enterprise payment processing environments. Organizations need structured approaches to implement cryptographic controls that satisfy both PCI DSS customized approach options and FIPS validation requirements for comprehensive payment security.
How to Execute PCI DSS v4.0 Network Security Testing Requirements with Penetration Testing Methodology for Multi-Site Card Processing InfrastructurePCI DSS v4.0 introduces enhanced network security testing requirements that demand more rigorous penetration testing methodologies for multi-site card processing environments. Organizations must implement comprehensive testing programs that address both internal and external network security controls while maintaining continuous assessment capabilities across distributed payment processing infrastructure.

Training that covers PCI DSS v4.0

What PCI DSS v4.0 means in your sector

What PCI DSS v4.0 means for your job

Questions people ask about PCI DSS v4.0

What is PCI DSS v4.0?
Payment Card Industry Data Security Standard for protecting cardholder data.
How many controls does PCI DSS v4.0 have?
PCI DSS v4.0 contains 280 controls organized across 16 domains.
Where does PCI DSS v4.0 apply?
PCI DSS v4.0 is applicable in International. Organizations operating in or serving customers in this jurisdiction should evaluate its requirements.
What frameworks does PCI DSS v4.0 map to?
PCI DSS v4.0 has control-to-control mappings with 208 other compliance frameworks in our database. Use our compliance platform to explore these mappings interactively.
How do I get started with PCI DSS v4.0 compliance?
Start by understanding the framework's key controls and domains. Our compliance platform provides AI-powered gap analysis and mapping tools to help you assess your current posture and build a remediation plan.

Query PCI DSS v4.0 programmatically

PCI DSS v4.0, its 280 controls and every mapping into other standards are available over a REST endpoint and an MCP server, so an agent can read them directly. The free tier is 10 calls a day and needs no signup.

PCI DSS v4.0 API reference and MCP config →

How ready are you for PCI DSS v4.0?

Answer 25 questions and get a professional readiness report with gap analysis, maturity scores, and prioritised action items. Results in 5 minutes.

Written and maintained by Gerard Blokdyk, The Art of Service.Last updated .