PCI SSC’s documents fall into three groups. The standard sets the requirements, the reporting forms record the results, and information supplements explain how to apply the requirements. Supplements never replace or supersede the standard, so read them alongside it.
Start with the standard
PCI DSS v4.0.1, published in June 2024, is the document everything else points back to. Its full title is Payment Card Industry Data Security Standard: Requirements and Testing Procedures. Each requirement lists what must be in place, how an assessor tests it, and any applicability notes. The PCI DSS requirements overview walks through the 12 requirements themselves.
A few sections repay close reading before anyone opens a requirement:
- Section 4 defines scope and explains segmentation.
- Section 7 defines timeframes such as “periodically.”
- Section 8 explains the defined and customized approaches.
- Section 12 outlines the assessment process.
- Appendices B through E cover compensating controls and the customized approach.
- Appendix G is the glossary.
The Guidance column helps, but it is not binding. The standard says guidance does not replace or extend any requirement.
The reporting documents
These forms record an assessment. Section 11 says the organizations that manage compliance programs, such as payment brands and acquirers, decide who must validate and how.
| Document | What it is for | Where to look first |
|---|---|---|
| ROC Template (v4.0.1, Revision 3, January 2025) | Required format for a Report on Compliance | ROC Template Instructions, including the four findings: In Place, Not Applicable, Not Tested, and Not in Place |
| SAQs (A, A-EP, B, B-IP, C, C-VT, D, P2PE, and SPoC) | Self-assessment forms, each scoped to a type of environment | The opening sections, which state who the form is for |
| AOCs | The official form for attesting to the results of a ROC or SAQ | Section 12 of the standard, which explains submission |
SAQ D comes in separate merchant and service provider versions. The SAQs also point to a separate document, SAQ Instructions and Guidelines, for choosing the right form.
The information supplements
Supplements carry the same notice: they provide supplemental information and don’t replace or supersede any PCI SSC standard.
Scoping and segmentation
Guidance for PCI DSS Scoping and Network Segmentation dates from May 2017. Section 3 sorts systems into three categories: CDE systems, connected-to or security-impacting systems, and out-of-scope systems. Section 4 works through shared-services examples. Because it predates v4.x, check its direction against Section 4 of the standard and Requirement 12.5.2.
Targeted risk analysis
PCI DSS v4.x: Targeted Risk Analysis Guidance (November 2023) explains the two TRA types, under Requirements 12.3.1 and 12.3.2. It also tabulates suggested frequencies for requirements that allow flexibility. Its FAQ is clear on one point: a TRA for activity frequency can’t justify doing an activity less often than a requirement states. The alternative it gives is a customized control under the customized approach.
Payment page scripts
Payment Page Security and Preventing E-Skimming (Version 1.0, Revision 1, April 2025) covers Requirements 6.4.3 and 11.6.1. It walks through payment page scenarios, including iframes and redirects, and assigns responsibilities for each. Table 4 summarizes controls and techniques. It also confirms that SAQ A doesn’t include either requirement but does include a related eligibility criterion.
Cloud and containers
The PCI SSC Cloud Computing Guidelines (April 2018) address provider and customer roles in Section 3, and PCI DSS responsibilities, segmentation, and scoping in Section 4. Guidance for Containers and Container Orchestration Tools (September 2022) pairs threats with best practices in Section 3.1, then applies them to use cases in Section 3.2.
How the documents fit together
A practical reading order follows the assessment process:
- Define scope using Section 4 and the scoping supplement.
- Ask your acquirer or payment brand how you must validate, then confirm eligibility in the form itself.
- Work through the applicable requirements, using supplements for specific topics.
- Complete the ROC or SAQ, then the AOC.
If a supplement and the standard seem to differ, follow the standard. The QSA Program Guide assigns compliance enforcement to the payment brands, so program questions belong with your acquirer or payment brand. For the wider picture, see 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 (Sections 4, 7, 8, 11, and 12; Appendices B through E and G)
- PCI DSS v4.0.1 ROC Template, Revision 3 (ROC Template Instructions)
- PCI DSS v4.0.1 SAQ A, Revision 1 (Merchant Eligibility Criteria; Additional PCI SSC Resources)
- Guidance for PCI DSS Scoping and Network Segmentation (Sections 3 and 4)
- PCI DSS v4.x: Targeted Risk Analysis Guidance (Frequently Asked Questions; TRA Requirements and Frequency Recommendations)
- Payment Page Security and Preventing E-Skimming: Guidance for PCI DSS Requirements 6.4.3 and 11.6.1 (Common Payment Page Scenarios; Table 4)
- QSA Program Guide v4.1 (Sections 2.1 and 2.2)
- PCI SSC Cloud Computing Guidelines (Sections 3 and 4)
- Guidance for Containers and Container Orchestration Tools (Section 3)
