Framework · Payment security · Validation
PCI DSS v4.0.1 requirements, compliance levels and validation
PCI DSS is the Payment Card Industry Data Security Standard, set by the PCI Security Standards Council for anyone who stores, processes or transmits cardholder data. Version 4.0.1 has 12 requirements in 6 goals. You validate compliance each year with a QSA Report on Compliance or a Self-Assessment Questionnaire.
What you need to know about PCI DSS
Who needs PCI DSS?
Anyone in the card payment chain, though the depth of validation differs.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does PCI DSS v4.0.1 require?
PCI DSS requires you to protect cardholder data with 12 requirements grouped into 6 goals, scoped to your cardholder data environment. Version 4 adds a customised approach and targeted risk analyses so you can meet objectives in your own way.
Secure network
Network security controls and secure configurations.
In QULDEX: Firewall rule reviews scheduledProtect account data
Minimise, encrypt and protect stored and transmitted data.
In QULDEX: Data flow diagrams kept currentVulnerability management
Anti-malware, secure software, patching, payment page scripts.
In QULDEX: Patch evidence per releaseAccess control
Need-to-know access, MFA and physical security.
In QULDEX: Six-monthly access reviewsMonitor and test
Logging, scans, penetration tests, change detection.
In QULDEX: Quarterly ASV scans trackedSecurity policy
Policies, risk analyses, training, vendors, incident response.
In QULDEX: Targeted risk analyses in one placeDefined or customised
Meet each requirement as written, or design your own control with a risk analysis.
In QULDEX: Customised approach documented per requirementWhat are the 12 PCI DSS requirements?
The 12 principal requirements are grouped into 6 goals. The last group lists key requirements that were future-dated in v4.0 and became mandatory on 31 March 2025. Select any item to see what it asks for, typical evidence and the matching ISO 27001 and SOC 2 controls.
Showing up to 6 per group. Search, filter, or open a group to see all 22.
Secure network 2
Req 1Install and maintain network security controlsControl traffic into and out of the cardholder data environment (CDE) with firewalls or equivalent controls, and review the rules.
In QULDEXQULDEX gives this requirement an owner and test steps, collects evidence on the cadence PCI DSS sets, and maps it to ISO 27001 and SOC 2.
- Typical evidence
- Network diagrams, firewall rule reviews
- Maps to
- ISO 27001 A.8.20A.8.22SOC 2 CC6.6
Req 2Apply secure configurations to all system componentsChange vendor defaults, remove unnecessary services and harden every system in scope.
In QULDEXQULDEX gives this requirement an owner and test steps, collects evidence on the cadence PCI DSS sets, and maps it to ISO 27001 and SOC 2.
- Typical evidence
- Hardening standards, config scans
- Maps to
- ISO 27001 A.8.9
Protect account data 2
Req 3Protect stored account dataKeep stored account data to a minimum, never store sensitive authentication data after authorisation, and render PAN unreadable.
In QULDEXData retention and encryption evidence is collected per data store.
- Typical evidence
- Data flow diagrams, encryption and key management records
- Maps to
- ISO 27001 A.8.24A.8.11SOC 2 C1.1
Req 4Protect cardholder data in transitUse strong cryptography when cardholder data travels over open, public networks.
In QULDEXQULDEX gives this requirement an owner and test steps, collects evidence on the cadence PCI DSS sets, and maps it to ISO 27001 and SOC 2.
- Typical evidence
- TLS configuration, certificate inventory
- Maps to
- ISO 27001 A.8.24SOC 2 CC6.7
Vulnerability management 2
Req 5Protect systems from malicious softwareDeploy and maintain anti-malware on systems commonly affected, and guard against phishing.
In QULDEXQULDEX gives this requirement an owner and test steps, collects evidence on the cadence PCI DSS sets, and maps it to ISO 27001 and SOC 2.
- Typical evidence
- Anti-malware console exports
- Maps to
- ISO 27001 A.8.7SOC 2 CC6.8
Req 6Develop and maintain secure systems and softwareBuild software securely, patch vulnerabilities, protect public web apps and manage payment page scripts.
In QULDEXPatch and secure-development evidence attach per release.
- Typical evidence
- Patch records, code reviews, WAF configuration
- Maps to
- ISO 27001 A.8.25–A.8.29SOC 2 CC8.1
Access control 3
Req 7Restrict access by business need to knowGrant access to system components and cardholder data only to those whose job needs it.
In QULDEXAccess reviews run as recurring tasks; revocations become tracked actions.
- Typical evidence
- Role definitions, access reviews
- Maps to
- ISO 27001 A.5.15A.8.3SOC 2 CC6.3
Req 8Identify users and authenticate accessGive every user a unique ID, enforce strong authentication and MFA.
In QULDEXQULDEX gives this requirement an owner and test steps, collects evidence on the cadence PCI DSS sets, and maps it to ISO 27001 and SOC 2.
- Typical evidence
- IdP settings, MFA enforcement
- Maps to
- ISO 27001 A.5.17A.8.5SOC 2 CC6.1
Req 9Restrict physical access to cardholder dataControl physical access to the CDE, media and point-of-interaction devices.
In QULDEXQULDEX gives this requirement an owner and test steps, collects evidence on the cadence PCI DSS sets, and maps it to ISO 27001 and SOC 2.
- Typical evidence
- Visitor logs, POI device inventory
- Maps to
- ISO 27001 A.7.1–A.7.4SOC 2 CC6.4
Monitor and test 2
Req 10Log and monitor all accessLog access to system components and cardholder data, protect the logs and review them.
In QULDEXLog review evidence is collected on schedule and sampled by the QSA.
- Typical evidence
- Log settings, daily review records
- Maps to
- ISO 27001 A.8.15A.8.16SOC 2 CC7.2
Req 11Test security of systems and networks regularlyRun internal and ASV external scans each quarter, penetration tests, and change-detection on payment pages.
In QULDEXQuarterly scans and annual tests are scheduled tasks with results attached.
- Typical evidence
- ASV scan reports, pen test reports
- Maps to
- ISO 27001 A.8.8SOC 2 CC7.1
Security policy 1
Req 12Support security with policies and programsKeep an information security policy, risk analyses, awareness training, vendor management and an incident response plan.
In QULDEXPolicies, targeted risk analyses and vendor records live in one place.
- Typical evidence
- Policies, TRAs, training records, IR plan
- Maps to
- ISO 27001 A.5.1A.5.24SOC 2 CC1–CC5
Key v4.0 requirements 10
5.4.1Anti-phishing mechanismsMandatory since Mar 2025Detect and protect personnel against phishing attacks with automated mechanisms.
In QULDEXQULDEX flags this as a v4.0 requirement and tracks its evidence separately so assessors can find it fast.
- Typical evidence
- Email security configuration
6.4.3Payment page script managementMandatory since Mar 2025Inventory, authorise and check the integrity of every script on payment pages loaded in the consumer's browser.
In QULDEXQULDEX flags this as a v4.0 requirement and tracks its evidence separately so assessors can find it fast.
- Typical evidence
- Script inventory with justifications
7.2.4Six-monthly user account reviewsMandatory since Mar 2025Review all user accounts and their privileges at least once every six months.
In QULDEXQULDEX flags this as a v4.0 requirement and tracks its evidence separately so assessors can find it fast.
- Typical evidence
- Account review sign-off
8.3.6Password length and complexityMandatory since Mar 2025Require passwords of at least 12 characters (or 8 where systems can't support 12) with numbers and letters.
In QULDEXQULDEX flags this as a v4.0 requirement and tracks its evidence separately so assessors can find it fast.
- Typical evidence
- Password policy settings
8.4.2MFA for all access into the CDEMandatory since Mar 2025Use multi-factor authentication for all non-console access into the CDE.
In QULDEXQULDEX flags this as a v4.0 requirement and tracks its evidence separately so assessors can find it fast.
- Typical evidence
- MFA enforcement evidence
10.4.1.1Automated log reviewsMandatory since Mar 2025Use automated mechanisms to perform audit log reviews.
In QULDEXQULDEX flags this as a v4.0 requirement and tracks its evidence separately so assessors can find it fast.
- Typical evidence
- SIEM correlation rules
11.3.1.1Managing non-critical vulnerabilitiesMandatory since Mar 2025Address lower-risk vulnerabilities based on a targeted risk analysis.
In QULDEXQULDEX flags this as a v4.0 requirement and tracks its evidence separately so assessors can find it fast.
- Typical evidence
- TRA and remediation records
11.6.1Payment page change and tamper detectionMandatory since Mar 2025Detect unauthorised changes to HTTP headers and payment page content as received by the browser.
In QULDEXQULDEX flags this as a v4.0 requirement and tracks its evidence separately so assessors can find it fast.
- Typical evidence
- Change-detection alerts
12.3.1Targeted risk analysisMandatory since Mar 2025Perform targeted risk analyses for requirements that allow flexible frequency.
In QULDEXQULDEX flags this as a v4.0 requirement and tracks its evidence separately so assessors can find it fast.
- Typical evidence
- Targeted risk analyses
12.5.2.1Service provider scope confirmationMandatory since Mar 2025Service providers confirm PCI DSS scope at least every six months and after significant change.
In QULDEXQULDEX flags this as a v4.0 requirement and tracks its evidence separately so assessors can find it fast.
- Typical evidence
- Scope confirmation records
Nothing matches that search.
Requirement numbers follow PCI DSS v4.0.1. Names and summaries are QULDEX paraphrases; the PCI SSC text is the authority. The last group is a selection, not the full list of new requirements.
How do you validate PCI DSS compliance?
Define and reduce your scope, close the gaps, then validate each year with either a QSA Report on Compliance or a Self-Assessment Questionnaire, plus an Attestation of Compliance. Your acquirer or the card brands decide which.
Scope the cardholder data environment
Map where card data flows, which systems store, process or transmit it, and which connected systems affect it.
Reduce scope
Use segmentation, tokenisation, or hosted payment pages to shrink the CDE before you assess it.
Gap assessment against v4.0.1
Compare controls with all requirements, including those that were future-dated until March 2025.
Remediate and document targeted risk analyses
Close gaps, write targeted risk analyses where requirements allow flexible frequency, and document any customised approach.
Quarterly scans and annual testing
Pass quarterly ASV external scans and internal scans, and run penetration tests.
Assessment: ROC or SAQ, plus AOC
A QSA writes a Report on Compliance, or you complete the right SAQ; both end with an Attestation of Compliance for your acquirer.
Repeat every year
Every quarterASV and internal scansEvery 6 monthsAccount reviews, segmentation tests for providersEvery yearROC or SAQ and AOC
Durations are typical planning ranges from QULDEX delivery. Your acquirer confirms your level and validation method.
Which documents prove PCI DSS compliance?
Acquirers and customers ask for your Attestation of Compliance. Behind it sit the assessment and the evidence a QSA samples.
| Document | Who produces it | Where it lives in QULDEX |
|---|---|---|
| Report on Compliance (ROC) | QSA (or ISA for some merchants) | Auditor workspace |
| Self-Assessment Questionnaire (SAQ A, A-EP, B, C, D …) | You | Control library by SAQ type |
| Attestation of Compliance (AOC) | QSA or you | Secure report sharing |
| ASV quarterly scan reports | Approved Scanning Vendor | Evidence vault |
| Penetration test reports | Qualified tester | Evidence vault |
| Network and data flow diagrams | You | Evidence vault |
| Targeted risk analyses | You | Risk register |
| Responsibility matrix with service providers | You and providers | Vendor register |
SAQ types depend on how you accept cards; your acquirer confirms which applies.
How long does PCI DSS take and what drives the cost?
A first validation usually takes 3 to 9 months; scope reduction is the biggest lever. Cost depends on your level, CDE size and whether a QSA is required.
Where the time goes
Bars show the upper end of each range on one scale (7.5 months = full width).
What changes the effort
- Level: Level 1 merchants and service providers need a QSA ROC
- CDE size: every in-scope system adds testing and evidence
- Scope reduction: tokenisation or hosted payment pages can cut scope sharply
- Payment pages: 6.4.3 and 11.6.1 add script inventory and tamper detection
- Service providers: responsibility matrices and their AOCs must line up
Are you ready for your PCI DSS assessment?
QSAs check these eight things early. Nothing you enter leaves this page.
How PCI DSS maps to ISO 27001, SOC 2 and NIST CSF 2.0
Most PCI DSS requirements have counterparts in ISO 27001 and SOC 2, though PCI DSS is more prescriptive about how often and how exactly. One tested control can support all three when it meets the strictest version.
ROC vs SAQ
| Report on Compliance (ROC) | Self-Assessment Questionnaire (SAQ) | |
|---|---|---|
| Who completes it | A QSA, or an internal ISA for some merchants | You |
| Who needs it | Level 1 merchants and service providers, or when your acquirer asks | Lower-level merchants, by SAQ type |
| Depth | Full on-site or remote assessment with testing | Self-attestation against the questions for your SAQ type |
| Output | ROC plus AOC | SAQ plus AOC |
| Effort | Highest | Lower, depends on SAQ type |
| In QULDEX | QULDEX holds requirements by SAQ type and by ROC testing procedure, so you only see what applies. | |
Requirements crosswalk
| PCI DSS v4.0.1 | ISO 27001:2022 | SOC 2 | NIST CSF 2.0 | Shared evidence |
|---|---|---|---|---|
| Req 1 Network security | A.8.20 · A.8.22 | CC6.6 | PR.IR-01 | Firewall reviews |
| Req 2 Secure configuration | A.8.9 | CC8.1 | PR.PS-01 | Hardening standards |
| Req 3 Stored data | A.8.11 · A.8.24 | C1.1 | PR.DS-01 | Encryption records |
| Req 4 Data in transit | A.5.14 · A.8.24 | CC6.7 | PR.DS-02 | TLS configuration |
| Req 5 Malware | A.8.7 | CC6.8 | DE.CM-09 | Anti-malware exports |
| Req 6 Secure software | A.8.25–A.8.29 | CC8.1 | PR.PS-06 | Code reviews, patching |
| Req 7 Need to know | A.5.15 · A.8.3 | CC6.3 | PR.AA-05 | Access reviews |
| Req 8 Authentication | A.5.17 · A.8.5 | CC6.1 | PR.AA-03 | MFA settings |
| Req 10 Logging | A.8.15 · A.8.16 | CC7.2 | DE.CM-01 | Log reviews |
| Req 11 Testing | A.8.8 · A.8.29 | CC7.1 | ID.RA-01 | Scans, pen tests |
| Req 12 Policy | A.5.1 · A.5.24 | CC1–CC5 | GV.PO | Policies, IR plan |
Indicative mapping for planning. PCI DSS frequency and detail requirements usually set the bar. The full crosswalk is in the QULDEX control library.
How QULDEX runs PCI DSS from scoping to AOC
QULDEX is PCI DSS compliance and audit management software built from EGV Group's audit delivery, used by the entity being assessed and by the QSAs who test it. Pick your role to see who does what.
For organisations preparing a ROC or SAQ.
- ScopeMap the CDEData flows and in-scope systems linked to requirements
- GapsClose the gapsRequirements by SAQ type or ROC procedure with owners
- RecurringRun quarterly and six-monthly tasksScans, reviews and TRAs scheduled with reminders
- AssessmentSupport the QSAControlled, logged evidence sharing
- AOCShare with acquirersSecure, expiring AOC links
- Next yearStay compliantLive readiness view between assessments
For PCI consultants and internal security assessors.
- ScopeRun the scoping workshopReusable scoping templates
- GapsAssess against v4.0.1Gap list per requirement
- RecurringTrack remediationGaps become CAPA items
- AssessmentPre-assessmentMock testing in the audit workspace
- AOCPrepare the clientAn assessment-ready pack
- Next yearStay on retainerOne dashboard across clients
For Qualified Security Assessors performing ROCs.
- PlanningConfirm scopeCDE and segmentation evidence in a standard format
- TestingRun testing proceduresEvidence mapped to each testing procedure
- SamplingSample systems and recordsView-only evidence access with download control and an access log
- FindingsRecord not-in-place itemsFindings per requirement
- ROCWrite the reportTraceable workpapers for the ROC
- Next yearRoll forwardHistory for the next assessment
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →PCI DSS questions people ask
What is the current version of PCI DSS?
PCI DSS v4.0.1, published in June 2024. v4.0 was retired on 31 December 2024, and requirements that were future-dated became mandatory on 31 March 2025.
Is PCI DSS a law?
No. It is an industry standard. Card brands and acquiring banks enforce it through contracts, and some laws reference it.
What are the 4 PCI compliance levels?
Card brands set merchant levels 1 to 4, mostly by annual card transaction volume. Level 1 usually needs a QSA Report on Compliance; lower levels usually complete an SAQ. Service providers have levels 1 and 2.
What is the difference between a ROC and an SAQ?
A ROC is a full assessment written by a QSA. An SAQ is a self-assessment questionnaire you complete. Both end with an Attestation of Compliance.
What are PCI DSS 6.4.3 and 11.6.1?
Two v4.0 requirements for e-commerce: 6.4.3 requires an inventory and authorisation of payment page scripts, and 11.6.1 requires detecting unauthorised changes to payment pages.
How can we reduce PCI DSS scope?
Segment the network, tokenise card data, or use hosted payment pages so card data never touches your systems.
Can QULDEX run PCI DSS alongside ISO 27001 and SOC 2?
Yes. Requirements are mapped once in the control library, and the strictest version of each control is tracked so one evidence set supports all three.
Go deeper on PCI DSS
PCI DSS 6.4.3 and 11.6.1: payment page scripts
What the two e-commerce requirements need in practice.
blog.quldex.comAudit sampling size for compliance
How many samples assessors pull, and why.
blog.quldex.comAudit evidence naming convention
A file-naming scheme that lets assessors sample without asking.
References
- PCI Security Standards Council, PCI DSS v4.0.1 (June 2024). pcisecuritystandards.org
- PCI SSC, Summary of Changes from v4.0 to v4.0.1. pcisecuritystandards.org
- PCI SSC, Self-Assessment Questionnaire instructions and guidelines. pcisecuritystandards.org
- PCI SSC, Information Supplement: Guidance for PCI DSS Scoping and Network Segmentation. pcisecuritystandards.org
- ISO/IEC 27001:2022. iso.org
Reviewed by
Page history
- : Rebuilt with requirements explorer, v4.0 key requirements, validation path, ROC vs SAQ and readiness check
- : Page first published
Find your PCI DSS gaps before your QSA does
Answer a short readiness check and get a gap summary by requirement. No sales call needed to see the result.