Skip to content
Services
PCI DSSISO 27001SOC 2GDPRPenetration TestingNIST CSFvCISODORA
Company
Case StudiesPartnersTrust CenterBlogGlossaryFAQFree AssessmentContact
Industries
FintechHealthcarePaymentsSaaS
AboutResourcesVeedar

PCI DSS v4.0.1: What Changed and What You Need to Do Now

PCI DSScompliancev4.0.1payment security

The Biggest PCI Overhaul in a Decade

PCI DSS v4.0 — released in March 2022, with the clarifying v4.0.1 update in June 2024 — represents the most comprehensive revision to the Payment Card Industry Data Security Standard since its inception. After nearly a decade on v3.2.1, the payment security landscape demanded a framework that addresses modern threats: sophisticated phishing, API-based attacks, cloud-native architectures, and the relentless growth of e-commerce.

The shift is not merely a longer checklist. v4.0 changes the philosophy of the standard. Where earlier versions told you precisely how to implement a control, v4.0 increasingly tells you what the control must achieve and asks you to prove you have achieved it. That is a more demanding posture for the organizations being assessed, and it rewards those who genuinely understand their own risk rather than those who simply tick boxes.

If your organization processes, stores, or transmits cardholder data, this is not a future concern — it is a present one. The transition period for the new requirements introduced in v4.0 has closed, and the controls that were initially treated as future-dated best practices are now mandatory and must be fully considered during a PCI DSS assessment.

Why v4.0 Matters

Three forces drove the rewrite, and understanding them helps explain almost every change in the standard.

  • Threats moved client-side and into the supply chain. Magecart-style skimming attacks inject malicious JavaScript into payment pages — code that never touches your servers but harvests card data straight from the browser. Traditional network controls do nothing against this. v4.0 responds with explicit script-integrity and tamper-detection expectations.
  • Authentication became the front line. Credential theft, phishing, and password reuse are now the most common entry points for attackers. v4.0 raises the bar on authentication across the board, not just at the network perimeter.
  • One-size-fits-all stopped fitting anyone. A fixed quarterly cadence makes no sense for a 10-person SaaS and a 30,000-employee bank alike. v4.0 introduces risk-based flexibility — but pairs it with an obligation to justify and document your decisions.

The result is a standard that is harder to fake your way through and easier to align with how a mature security programme actually operates.

What Actually Changed

1. The Customized Approach

The most fundamental shift in v4.0 is the introduction of the Customized Approach alongside the traditional Defined Approach.

Under the Defined Approach, you implement the prescriptive requirement exactly as written and your assessor tests against the stated testing procedures — the model every organization knows from earlier versions.

Under the Customized Approach, you design your own controls to meet each requirement's stated Customized Approach Objective, provided you can demonstrate equivalence. Throughout v4.0.1 each requirement carries an explicit objective — for example, that "systems not known to be at risk from malware are re-evaluated at a frequency that addresses the entity's risk," or that "bespoke and custom software is developed in accordance with PCI DSS and secure development processes throughout the software lifecycle." These objectives are the bar your custom control must clear.

This is not a shortcut. The Customized Approach demands a targeted risk analysis for every control you customize, documented evidence that your alternative meets the security intent of the objective, and independent validation by your QSA. The evidence burden is real, and the assessor cannot simply follow a pre-written test plan — they must derive bespoke testing procedures for each customized control.

For mature organizations with strong, well-documented security programmes, the Customized Approach offers welcome flexibility to use the controls they already run. For everyone else, the Defined Approach remains the faster, safer path. You can also mix the two, requirement by requirement.

2. Authentication Overhaul (Requirement 8)

Multi-factor authentication (MFA) is now required for all access to the cardholder data environment — not just remote access from outside the network. Key changes include:

  • MFA for all CDE access, including on-premises console access
  • Minimum password length increased from 7 to 12 characters (or 8 where a system genuinely cannot support 12)
  • Dynamic analysis of password strength permitted as an alternative to static complexity rules
  • Service and application accounts must now follow defined password policies, with managed credentials and periodic rotation

For most organizations, "MFA everywhere inside the CDE" is the single largest engineering lift in the entire transition. It touches identity architecture, legacy systems, and operational habits — which is precisely why it should not be left until an assessment is imminent.

3. E-Commerce and Client-Side Protections (Requirements 6 & 11)

In direct response to Magecart-style attacks, v4.0 introduces requirements that many organizations have never addressed:

  • Requirement 6.4.3: All payment page scripts must be inventoried, authorized, and monitored for integrity. Every JavaScript file loaded on your checkout page needs to be justified and tracked.
  • Requirement 11.6.1: A change-and-tamper detection mechanism must alert on unauthorized modifications to payment pages — including HTTP headers and the content of scripts received by the consumer's browser.

These requirements alone will force a rethink of how most e-commerce operations manage their payment pages, especially where third-party tags, analytics, and chat widgets are loaded onto the same page as the card-entry form.

4. Targeted Risk Analyses

Gone are many of the one-size-fits-all frequency mandates. v4.0 requires organizations to perform a targeted risk analysis (TRA) to determine the frequency of certain recurring activities — for example, periodic evaluations of system components not known to be at risk from malware, where the standard requires that those evaluations are "performed at the frequency defined in the entity's targeted risk analysis performed for this requirement."

A TRA is not a paragraph of hand-waving. It must identify the asset being protected, the threats, the likelihood and impact, and the reasoning that leads to your chosen frequency — and it must be reviewed periodically. You are trading a fixed number for the obligation to defend your number. Assessors will ask to see the analysis, not just the schedule it produced.

5. Roles and Responsibilities

Every requirement area now opens with a sub-requirement to define roles and responsibilities for performing the relevant activities. This is not cosmetic. Assessors will verify that personnel are formally assigned, that the assignment is documented, and that the people named understand their obligations. Ambiguity about "who owns this control" is now itself a finding.

6. Secure Software Development

v4.0.1 reinforces secure-by-design expectations for bespoke and custom software, requiring that information security is considered at each stage of the software development lifecycle and that staff are knowledgeable in secure coding methods. The Customized Approach Objective is clear: software developed for or by the entity for its own use is built "in accordance with PCI DSS and secure development processes throughout the software lifecycle." Note the scope — this applies to bespoke and custom software you develop, not to third-party software you merely consume.

7. The Future-Dated Requirements Are Now Live

A large block of v4.0's new requirements were introduced as "best practice" with a future effective date, giving organizations time to prepare. The grounding language in the standard is unambiguous: such a requirement "is a best practice until 31 March 2025, after which it will be required and must be fully considered during a PCI DSS assessment."

That window has now closed. The future-dated controls — the client-side protections, expanded MFA, targeted risk analyses, and the rest — are simply requirements today. Critically, a requirement is not considered in place if the control has not yet been implemented, or is only scheduled for a future date. "We're planning to roll that out next quarter" does not satisfy an assessor; the control must actually be operating.

Scoping and Evidence: The Quiet Difficulties

Two themes run underneath every change above and deserve their own attention.

Scoping. v4.0 expects you to confirm, at least annually, exactly what is in your cardholder data environment and what connects to it. Cloud workloads, ephemeral infrastructure, third-party scripts, and SaaS integrations make scope harder to pin down than it was in 2015. Getting scope wrong in either direction is costly — too wide and you over-engineer controls; too narrow and you have unprotected exposure that surfaces at the worst possible moment.

Evidence. The Customized Approach, targeted risk analyses, and roles-and-responsibilities expectations all multiply the volume of documentation an assessor must review. v4.0 rewards organizations that capture evidence continuously rather than scrambling for it in the weeks before an assessment. Evidence that is collected as controls operate — rather than reconstructed afterwards — is both more credible and far less painful to produce.

What You Need to Do Now

1. Gap assessment against v4.0.1. Compare your current controls against the full v4.0.1 requirement set, with particular attention to the formerly future-dated requirements that are now mandatory. Treat "best practice" notes in older planning documents as obligations today.

2. Prioritize e-commerce controls. Requirements 6.4.3 and 11.6.1 require tooling and process changes that take time to implement properly. If you operate a payment page, start here — script inventory and tamper detection are not things you stand up overnight.

3. Overhaul authentication. MFA for all CDE access is non-negotiable. Audit your current access architecture, including console and service accounts, and plan the rollout against your real legacy constraints.

4. Document your targeted risk analyses. Every frequency-based control that allows a risk-based cadence needs a documented TRA. This is paperwork-intensive but assessor-critical, and it cannot be back-filled convincingly.

5. Assign roles and responsibilities formally. Map each requirement area to a named owner and make sure those people can describe their duties. Update job descriptions or RACI matrices where needed.

6. Confirm and document your scope. Re-baseline the CDE, connected systems, and all third-party code loaded on payment pages. Make scope confirmation a repeatable annual exercise, not a one-off.

7. Train your people. Security awareness training must reflect v4.0-era threats — phishing and social engineering tailored to your environment — and the training itself is subject to the targeted-risk-analysis logic for frequency.

Migration Checklist

StepActionOwnerStatus
1Confirm CDE scope and inventory connected systemsSecurity / Compliance
2Run a full gap assessment against v4.0.1QSA / Internal
3Inventory and authorize all payment-page scripts (6.4.3)Engineering
4Deploy payment-page tamper/change detection (11.6.1)Engineering
5Extend MFA to all CDE access, including consoleIdentity / IT
6Apply password and credential policies to service accountsIT
7Write targeted risk analyses for all risk-based frequenciesCompliance
8Assign and document roles and responsibilitiesLeadership
9Update secure-SDLC procedures and developer trainingEngineering
10Stand up continuous evidence collectionCompliance

Frequently Asked Questions

Is v4.0.1 a new standard I have to re-implement? No. v4.0.1, published in June 2024, is a clarifying update to v4.0 (March 2022). It corrects and clarifies wording; it does not add a fresh wave of obligations. Plan against v4.0.1 as the current authoritative text.

Are the "best practice" requirements optional? Not any more. Requirements that were best practice until 31 March 2025 are now required and must be fully considered during an assessment. A control that is only planned or scheduled for the future is not considered in place.

Should we use the Customized Approach? Only if you have the security maturity and documentation to defend it. It offers flexibility but increases your evidence burden and requires bespoke testing by your QSA. Many organizations sensibly use the Defined Approach for most requirements and the Customized Approach selectively.

What is a targeted risk analysis, in practical terms? A documented, repeatable analysis that justifies how often you perform a given activity, based on the assets, threats, likelihood, and impact specific to your environment. It replaces a fixed mandated frequency with a defensible, evidence-backed one.

Does Requirement 6.2.1 apply to the software we buy? No. The secure-development requirements apply to bespoke and custom software developed for or by your organization for its own use, not to third-party software you purchase.

The Takeaway

v4.0 is less a longer checklist than a change in mindset: from prescriptive controls to demonstrated outcomes, from fixed cadences to justified ones, and from network-perimeter thinking to protecting data wherever it actually lives — including the customer's browser. The organizations that adapt fastest are those that treat compliance as a continuous, evidence-rich operating discipline rather than an annual fire drill.

How Mölnir Accelerates PCI DSS v4.0 Readiness

As a PCI SSC Certified QSA company, Mölnir has been preparing clients for v4.0 since its draft stages, and has delivered 100+ audits across 12+ countries for banks, fintechs, and SaaS providers. Our approach combines Veedar — our proprietary, AI-powered compliance platform — with hands-on QSA expertise to cut assessment timelines from months to weeks.

Veedar automates evidence collection, maps your existing controls to v4.0.1 requirements, surfaces gaps in real time, and generates remediation roadmaps prioritized by risk. When paired with our experienced assessors, the result is a certification process that is faster, less painful, and more thorough than traditional approaches — and one that holds up under the heightened evidence expectations v4.0 brings.

The future-dated requirements are now live, and a control that isn't yet in place won't pass. If you have not finished your v4.0 transition, the time to act is now. Schedule a PCI DSS v4.0 readiness assessment with Mölnir.

Comments

Be the first to comment.

Leave a comment