PCI DSS v4.0.1: the 12 requirements and how to stay compliant all year
PCI DSS is the contractual standard every organisation that stores, processes or transmits payment card data must meet, enforced through the card brands and your acquirer. Version 4 changed the emphasis from an annual assessment to continuous security, and its future-dated requirements are now mandatory. This guide covers the requirements, the assessment routes and what to automate.
PCI DSS applies to the cardholder data environment: every system component that stores, processes or transmits cardholder data or sensitive authentication data, plus anything connected to it or that could affect its security. Scope is therefore the first and most consequential decision. Segmentation, tokenisation and point-to-point encryption exist largely to shrink it.
Version 4 added targeted risk analyses that let an organisation set its own frequency for certain controls, a customised approach for meeting a requirement’s objective by other means, and a set of new requirements that became mandatory in March 2025: among them multi-factor authentication for all access to the cardholder data environment, automated log review, management of payment page scripts, and detection of unauthorised changes to payment pages.
The 12 requirements
1. Install and maintain network security controls
Firewalls and equivalent controls between untrusted networks and the cardholder data environment, with documented rule sets reviewed at least every six months.
2. Apply secure configurations to all system components
No vendor defaults; hardening standards for every component type; one primary function per server.
3. Protect stored account data
Minimise storage, never store sensitive authentication data after authorisation, render the PAN unreadable wherever stored, manage keys properly.
4. Protect cardholder data with strong cryptography during transmission
Strong cryptography on open public networks; certificates validated; no unprotected PANs in messaging.
5. Protect all systems and networks from malicious software
Anti-malware on all in-scope systems, kept current, with periodic scans and anti-phishing mechanisms.
6. Develop and maintain secure systems and software
Secure development, vulnerability management with risk ranking, critical patches within one month, change control, and management of scripts on payment pages.
7. Restrict access to system components and cardholder data by business need to know
Least privilege, role-based access, reviewed at least every six months.
8. Identify users and authenticate access to system components
Unique IDs, MFA for all access into the cardholder data environment, password rules, lockout, session timeouts.
9. Restrict physical access to cardholder data
Facility controls, visitor management, media handling, and protection of point-of-interaction devices from tampering.
10. Log and monitor all access to system components and cardholder data
Audit logs for all components, protected, reviewed daily with automated tooling, retained twelve months with three months immediately available.
11. Test security of systems and networks regularly
Wireless detection, quarterly internal and ASV external scans, annual penetration testing, intrusion detection, change-detection on critical files and payment pages.
12. Support information security with organisational policies and programs
Security policy, risk management, acceptable use, awareness training, incident response plan tested annually, third-party service provider management, and PCI scope confirmed at least annually.
Merchant and service provider levels
- Level 1 merchant. More than 6 million card transactions a year (brand thresholds vary): annual on-site assessment by a QSA, ROC and AOC, quarterly ASV scans.
- Level 2 and 3 merchants. 1–6 million and 20,000–1 million e-commerce transactions respectively: annual SAQ (some brands require a QSA for Level 2) and quarterly ASV scans.
- Level 4 merchant. Fewer than 20,000 e-commerce or up to 1 million total transactions: annual SAQ and ASV scans as the acquirer requires.
- Service providers. Level 1 (more than 300,000 transactions) requires a QSA ROC; Level 2 may use SAQ D. Providers are also listed by the brands once validated.
Who it applies to
Every merchant that accepts payment cards, from an online store to a bank, and every service provider that can affect the security of cardholder data: payment processors, hosting providers, managed security providers, call centres and software vendors in the payment flow. Obligations arrive through the merchant agreement with the acquirer rather than by law, but fines, higher fees and loss of the ability to accept cards follow non-compliance.
From scope to evidence, in one system
Scope that is recorded, not remembered
The cardholder data environment is defined as a scope with its system components, data flows, segmentation and connected systems, and confirmed annually as requirement 12 demands.
All requirements with testing procedures
Every sub-requirement carries its testing procedure, an owner, status and evidence, so the SAQ or the material a QSA samples for a ROC is produced from the record.
Continuous evidence for the technical requirements
Adapters for AWS, Azure, Google Cloud, Kubernetes, Entra ID, Intune, CrowdStrike, Tenable or Qualys, and your SIEM collect configuration, scan and log-review evidence on a schedule, which is the continuous compliance v4 expects between assessments.
Targeted risk analyses and the customised approach
Where v4 lets you set a frequency or meet an objective another way, the analysis and its justification are stored against the requirement, where an assessor looks for them.
Crosswalk to ISO 27001 and SOC 2
PCI DSS requirements are mapped to ISO 27001 and SOC 2 controls, so evidence collected for a certification or attestation counts toward the SAQ or ROC.
Frequently asked questions
Which SAQ applies to us?
It depends on how you accept cards. SAQ A for fully outsourced e-commerce, A-EP where your site affects the payment page, B and B-IP for standalone terminals, C and C-VT for connected systems and virtual terminals, P2PE for validated point-to-point encryption, and D for everyone else including service providers. Your acquirer confirms the type.
What were the biggest changes in version 4?
MFA for all access to the cardholder data environment, automated log review, control of payment page scripts and change detection on payment pages, targeted risk analyses, the customised approach, and stronger authentication rules. Most were best practice until 31 March 2025 and are now mandatory.
How often do we need to do this?
Formal validation is annual, but v4 is explicit that compliance is continuous: quarterly ASV scans, six-monthly reviews of firewall rules and access, daily log review, and immediate response to critical vulnerabilities.
Does tokenisation take us out of scope?
It reduces scope substantially by removing stored PANs, but the systems that handle cards before tokenisation and the tokenisation provider remain in scope. Confirm the resulting scope with your QSA or acquirer.
Related frameworks
Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.