When PCI DSS version 4.0 was released, many of its new requirements were marked "best practice until March 31, 2025." That date has come and gone. For merchants and service providers, the formerly future-dated requirements are now simply requirements — and assessments are showing where organizations are still catching up.
Where things stand
The PCI Security Standards Council published PCI DSS 4.0.1 in June 2024 as a limited revision that clarified wording and guidance without adding new requirements. Version 4.0 was retired at the end of 2024, so 4.0.1 is the version organizations assess against today.
The requirements organizations struggle with most
Targeted risk analyses
Version 4.x lets organizations set the frequency of certain activities — such as reviewing some logs or rotating some credentials — based on a targeted risk analysis. That flexibility comes with an obligation: the analysis must be documented, reviewed at least annually and available to the assessor. Organizations that "just picked a number" are finding that assessors expect the reasoning.
Authenticated internal vulnerability scanning
Internal vulnerability scans must now be performed using authenticated scanning with sufficient privileges, so the scanner can see missing patches and misconfigurations that unauthenticated scans miss. Credential management for the scanning tool and handling systems that can't accept credentials both need attention.
MFA for all access into the CDE
Multi-factor authentication is now required for all access into the cardholder data environment, not just remote or administrative access. Organizations with flat networks or shared administrative workflows often find this requirement drives broader architecture changes.
Payment page scripts
E-commerce merchants must maintain an inventory of scripts on payment pages, justify each one, ensure their integrity and implement a mechanism to detect unauthorized changes to payment pages and security-relevant headers. These requirements target web-skimming attacks, and they often require coordination between security, marketing and web development teams.
Automated log review and phishing protection
Audit log reviews must be performed using automated mechanisms, and organizations must have processes and automated mechanisms to detect and protect personnel against phishing attacks. Both are reasonable expectations — but they require tooling and evidence that manual processes can't provide.
Practical steps
- Revisit scope. Tokenization, point-to-point encryption, hosted payment pages and segmentation can shrink the cardholder data environment dramatically — and every system removed from scope is a system you don't have to assess.
- Build a targeted risk analysis library. Document each flexible-frequency decision once, review it annually and keep it with your evidence.
- Close the MFA gaps. Map every path into the CDE and confirm MFA is enforced on each.
- Get your payment pages under control. Inventory scripts, remove what isn't needed and deploy change detection.
- Automate evidence. Choose tools that produce the logs and reports your assessor will request.
- Run a readiness assessment before your formal ROC or SAQ to avoid surprises.
Choosing between a ROC and an SAQ
Whether you need a Report on Compliance from a QSA or can validate with a Self-Assessment Questionnaire depends on your merchant or service provider level and on what your acquirer or the card brands require. If you're unsure, ask your acquiring bank — and make sure you're using the correct version of the correct SAQ.
The bottom line
PCI DSS 4.0.1 rewards organizations that treat compliance as a continuous security program rather than an annual event. Reduce scope where you can, document your risk-based decisions and invest in automation — and next year's assessment will be far less painful.