On March 31, 2022, the Payment Card Industry (PCI) Security Standards Council released version 4.0 of the Data Security Standard (DSS), updating what has been a long-running standard that needed some refreshing based on the newest technologies on the market. The increased focus on eCommerce and reliance on mobile devices has introduced several major security threats to consumers and merchants, and version 4.0 serves as the PCI DSS way of addressing them.
Merchants and credit card processors don’t, as of yet, need to update their infrastructure to 4.0 standards, but with the release of the initial documentation, the clock for meeting new compliance standards is ticking.
What Is PCI v. 3.2.1?
Released May 17, 2018, the 3.2.1 PCI DSS standard was the final minor revision to the larger 3.0 version of the PCI DSS standard. At the time, this version was considered the end of life for this particular version and remained in place until March 2022.
By the time these revisions took effect, PCI DSS had covered several different aspects of credit card processing security, including:
- Scope: PCI DSS standards apply to “all system components included in or connected to the cardholder data environment.” Before assessments, and at a minimum of once per year, a company must inventory all systems connected to cardholder information and document them for assessment and compliance.
- Requirements: This standard maintains and defines the 12 core requirements of this security standard across six procedures (build and maintain secure networks, protect cardholder data, maintain vulnerability management programs, implement strong access control, monitor and test networks, and maintain information security policies).
- Additional Requirements: The standard also includes additional requirements for specific systems. These include requirements for shared hosting providers, upgrading requirements for outdated SSL and TLS encryption, and reporting security requirements for companies that must undergo Designated Entities Supplemental Validation–that is, those that process large volumes of cardholder data, those who have had previous or repeat security breaches, and those who serve as aggregation points for cardholder data.
The Transition to PCI DSS 4.0
With the onset of PCI DSS 4.0, these requirements are not immediately rendered obsolete. Instead, a transition period is provided to all companies moving from version 3.2.1 to 4.0.
Based on the timeline provided by the Security Standards Council, we’ve already passed the release of the initial PCI DSS 4.0 standard and the ISA/QSA training documentation for auditors.
Following that, the slated retirement date for PCI DSS v. 3.2.1 is March 31, 2024, and all companies under PCI DSS jurisdiction must move to version 4.0.
However, the Security Standards Council has also created a designation of “future-dated new requirements” up until March 31, 2025. After this data, future-dated requirements will shift from suggested “best practices” to full compliance requirements. This window is intended to help organizations implement these changes effectively.
What’s New in PCI DSS 4.0?
As with any major change of a piece of software, security standard, or another piece of technology, there are some significant updates in 4.0. Over the next few months (and up until the complete switch to 4.0), we will provide more in-depth coverage of these changes. For the time being, here are some of the major shifts in the PCI DSS landscape.
Customized Approaches
In version 3.2.1, organizations that could not meet security requirements were allowed to substitute different controls they could meet, so long as they could justify that decision through risk assessment. This requirement is in effect immediately for any PCI DSS 4.0 assessments.
In 4.0, merchants and processors can still do this. Still, they are allowed what is known as a “customized” approach where they have more control over the types of security they implement based on their infrastructure and the spirit of the framework.
The difference here is subtle but significant. Previously, implementing custom controls was a matter of necessity and required extensive justification through risk analysis. With PCI DSS 4.0, customers have more flexibility in selecting controls, and PCI DSS auditors can assess that customized approach for long-term deployment.
Expanded Risk Assessment
On top of requiring risk analysis as part of compliance, PCI DSS now provides a specific Sample Targeted Risk Analysis Template to guide risk management for processors better.
Due Diligence
PCI DSS increases the assessment load for companies to promote cyberhealth, including:
- Annual audits of all encryption protocols and ciphers
- Annual risk analysis of any customized controls
- Annual (at least) review of hardware and software to inform retiring or remediating outdated systems.
- Annual review and updating of PCI DSS scope.
These requirements are in effect immediately for any PCI DSS 4.0 assessments.
Updated Authentication and Authorization Requirements
Version 4.0 significantly increases identity and access management standards, leveraging National Institute of Standards and Technology (NIST) Special Publication 800-63B, “Digital Identity Guidelines”.
These requirements include:
- Increased MFA Requirements: Any account with access to cardholder data in any compliant system must implement multifactor authentication.
- Password Updating: All user passwords must be changed annually and upon any potential that passwords have been compromised.
- Strong Password Requirements: All passwords must contain at least 15 characters and be compared against a list of known bad passwords to avoid reuse or weak password creation.
- Access Privileges and Vendor Accounts: Merchants and processors must review access privileges at least once every six months and limit third-party vendor access to cardholder systems only as needed and under regular monitoring.
Roles and Responsibilities
All companies under the jurisdiction of PCI DSS must have well-defined roles and responsibilities around critical areas like
- Data Retention
- Cryptographic Key Management
- Management of Encryption Policies
- Anti-Malware Management and Configuration
- Anti-Phishing Efforts
- Software/Web Application Security
- Vulnerability Management
- Authentication and User Management
- MFA Implementation
- Physical Access Security and Logging
And other security and logistical areas.
Furthermore, upon customer request, third-party vendors must provide a responsibility and role matrix representing the relationships between themselves and their clients.
These requirements are in effect immediately for any PCI DSS 4.0 assessments.
Prepared for the PCI DSS 4.0 Switch with Lazarus Alliance
While version 3.2.1 is still in effect, the date has been set to set the standard and move into version 4.0. This isn’t just a business choice–PCI DSS 4.0 is intended to help merchants and processors better understand and resist modern security threats in the wild. The longer they wait, the more they will watch their current standards fail to address these issues.
That doesn’t mean you have to jump on the process right now. But, there is no time like the present to get the ball rolling and understand your business’s expectations.
Trust Lazarus Alliance, a security firm with years of experience in PCI DSS compliance, to help.
Getting Ready for PCI DSS 4.0?
Call Lazarus Alliance at 1-888-896-7580 or fill in this form.
What Is Autonomous Malware?
We’re reaching the end of 2025, and looking ahead to 2026, most experts are discussing the latest threats that will shape the year ahead. This year, we’re seeing a new, but not unexpected, shift to autonomous threats driven by state-sponsored actors and AI. With that in mind, a new generation of threats, broadly known as...Continue reading→
What CISA’s Emergency Directive 26-01 Means for Everyone
In mid-October 2025, the CISA issued one of its most urgent orders yet: Emergency Directive 26-01. The directive calls on all Federal Civilian Executive Branch (FCEB) agencies to immediately mitigate vulnerabilities in devices from F5 Networks following a state-sponsored breach of F5’s systems and access to portions of BIG-IP source code and vulnerability data. The event...Continue reading→
Cybersecurity and Vetting AI-Powered Tools
A recent exploit involving a new AI-focused browser shone a light on a critical problem–namely, that browser security is a constant issue, and AI is just making that threat more pronounced. Attackers discovered a way to use that browser’s memory features to implant hidden instructions inside an AI assistant. Once stored, those instructions triggered unwanted...Continue reading→
Shutdown Security And Cyber Vulnerability
When the federal government shuts down, the public sees closed monuments, unpaid workers, and halted programs. What they do not see is the silent surge of cyberattacks targeting agencies already operating on fumes. During the most recent shutdown, attacks against U.S. government systems spiked by nearly 85%. Cybersecurity failures during government disruptions rarely start with...Continue reading→
Identity and the Shift from Malware
The world of cyber threats is rapidly evolving, and while we can see these changes more generally, it’s always crucial to understand them concretely. As the 2025 CrowdStrike Global Threat Report shows us, the landscape of our industry is changing. We’re digging into this report to discuss a challenging trend: the move of hackers foregoing...Continue reading→
Maintaining Compliance Against Prompt Injection Attacks
The increasing adoption of AI by businesses introduces security risks that current cybersecurity frameworks are not prepared to address. A particularly complex emerging threat is prompt injection attacks. These attacks manipulate the integrity of large language models and other AI systems, potentially compromising security protocols and legal compliance. Organizations adopting AI must have a plan...Continue reading→
Are We Already Talking About CMMC 3.0?
The ink has barely dried on the CMMC final rule, and already the defense contracting community is buzzing with speculation about what comes next. Just when contractors thought they had a moment to catch their breath after years of regulatory limbo, whispers of CMMC 3.0 have begun circulating through the industry. But is this just...Continue reading→
Centralizing Identity-Based Risk
As the traditional network boundary dissolves and remote work becomes standard practice, identities are the major frontier for security. Whether we’re talking about human users, service accounts, or machine identities, these have emerged as both the primary access mechanism and the most targeted attack vector. It has become imperative for providers to centralize identity management...Continue reading→
Deviation and Significant Change Requests in FedRAMP: A Comprehensive Guide
FedRAMP provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services used by federal agencies. While the program’s rigorous baseline requirements ensure consistent security, the reality is that this consistency calls for a little flexibility. This is where deviation requests and significant change requests come into play. These two...Continue reading→
The Costs of Compliance and Data Breaches
Data is possibly one of the most valuable assets any organization holds. Customer information, employee records, and proprietary business intelligence present challenges because the data flowing through modern enterprises represents both significant opportunities and serious risks. Businesses face a challenging balance: investing in compliance measures to protect sensitive information while also preparing for the real...Continue reading→
Related Posts