PCI DSS v4.0.1, published in June 2024, is the current version in the PCI SSC documents reviewed for this page. Requirements that v4.0 introduced as best practices became required after 31 March 2025. In January 2025, PCI SSC also revised SAQ A, removing three requirements and adding a script-related eligibility criterion.
Dated timeline
Each row comes from a PCI SSC change table or the document itself.
| Date | Document | What changed |
|---|---|---|
| March 2022 | PCI DSS v4.0 | Published as the update from v3.2.1, under the new title Requirements and Testing Procedures |
| April 2022 | SAQs | Aligned with v4.0, with appendices added for new reporting responses |
| October 2022 | PA-DSS | Program retired, per Section 3 of the standard |
| December 2022 | SAQs and ROC Template | “In Place with Remediation” removed; SAQs gained guidance on future-dated requirements |
| September 2023 | SAQ SPoC | New SAQ for software-based PIN entry on commercial off-the-shelf solutions |
| November 2023 | TRA guidance | New supplement on targeted risk analysis |
| January 2024 | SAQ B-IP | Requirement 4.2.1 restored after inadvertent removal |
| June 2024 | PCI DSS v4.0.1 | Published as the update from v4.0 |
| August 2024 | ROC Template | Aligned with v4.0.1 |
| October 2024 | SAQs | Aligned with v4.0.1; further form-specific edits below |
| January 2025 | SAQ A Revision 1 | Requirements 6.4.3, 11.6.1, and 12.3.1 removed; script eligibility criterion added |
| 31 March 2025 | Future-dated requirements | Best-practice period ended |
| March and April 2025 | Payment page guidance | Supplement released, then corrected on redirection mechanisms |
What v4.0 introduced
PCI DSS v4.0 introduced targeted risk analysis. The TRA guidance explains how Requirement 12.3.1 differs from the general risk assessment in v3.2.1. Other new requirements arrived with a future effective date, so organizations had time to prepare.
Requirements that took effect after 31 March 2025
These carry a note that they were best practices until that date. That date has passed, so they now apply in full. Examples include:
- Requirement 3.5.1.2: disk-level encryption alone can’t protect PAN on non-removable media.
- Requirement 5.4.1: automated controls to detect and protect personnel against phishing.
- Requirements 6.4.2, 6.4.3, and 11.6.1: web application protection and payment page script controls.
- Requirement 8.3.6: a 12-character password minimum, or eight where a system can’t support 12.
- Requirement 8.4.2: MFA for all non-console access into the CDE.
- Requirement 10.4.1.1: automated audit log reviews.
- Requirement 12.3.1: documented targeted risk analyses.
What v4.0.1 changed
The standard’s change table refers readers to a separate PCI SSC document, Summary of Changes from PCI DSS Version 4.0 to 4.0.1, for the details. Its forms followed, and their tables show some specific edits from October 2024:
- SAQ A and SAQ A-EP merchants now confirm that their TPSPs are compliant for the services used, rather than reviewing the TPSPs’ AOCs.
- SAQ C dropped Requirement 10.3.3 as not relevant to its merchants.
- SAQ C-VT restored an eligibility bullet on network segmentation.
- The SAQs added the ASV Resource Guide to their resource lists.
The January 2025 SAQ A revision
This revision matters most to e-commerce merchants that outsource all account data handling. SAQ A Revision 1 removed Requirements 6.4.3, 11.6.1, and 12.3.1. In their place, merchants confirm that their “site is not susceptible to attacks from scripts that could affect the merchant’s e-commerce system(s).”
The two script requirements still appear in SAQ A-EP, both versions of SAQ D, and the ROC Template. SAQ A also notes that requirements outside the form may signal it isn’t suitable. PCI SSC’s payment page supplement points merchants to its Best Practices for Small Merchants section for confirming this criterion.
Your acquirer or payment brand decides which validation applies to you. For the requirements themselves, see the PCI DSS requirements overview or the PCI DSS hub.
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 (Document Changes; Section 3; Section 14; Applicability Notes for the requirements cited)
- PCI DSS v4.0.1 SAQ A, Revision 1 (Document Changes; Merchant Eligibility Criteria)
- PCI DSS v4.0.1 SAQs A-EP, B-IP, C, C-VT, and SPoC (Document Changes)
- PCI DSS v4.0.1 ROC Template, Revision 3 (Document Changes)
- PCI DSS v4.x: Targeted Risk Analysis Guidance (Introducing Targeted Risk Analyses; FAQ 4)
- Payment Page Security and Preventing E-Skimming: Guidance for PCI DSS Requirements 6.4.3 and 11.6.1 (Document Changes; SAQ discussion under Applicability and Responsibilities)
