PCI DSS 4.0 Compliance
Compliance · PCI DSS

PCI DSS 4.0 Compliance

Overview

What it is & who needs it

PCI DSS 4.0 is the card schemes' security standard for anyone touching payment card data, and it tightens the requirements on authentication, encryption and continuous control monitoring. We take you from scoping and gap assessment through remediation to a successful validation.

Who needs it: Any business that stores, processes or transmits payment card data.

What PCI DSS 4.0 broadly requires

  • Accurate scoping of the cardholder data environment, with segmentation
  • Strong access control: MFA and least privilege around card data
  • Encryption of cardholder data in transit and at rest
  • Logging and monitoring across every in-scope system
  • Regular testing: vulnerability scans and penetration tests
  • Annual validation via SAQ or a formal assessment, per your merchant / provider level

How Virtual Caim helps

  1. Scope the cardholder data environment and confirm your validation path
  2. Gap assessment against the PCI DSS 4.0 requirements
  3. Remediation support across segmentation, encryption, access control and logging
  4. Vulnerability scanning and penetration testing of in-scope systems
  5. Assessment support and evidence packaging for your SAQ or RoC
  6. Free re-test of closed findings and help sustaining compliance year-round
PCI DSS FAQ

PCI DSS 4.0.1: versions, SAQ changes and what is now mandatory

PCI DSS v4.0.1 is the current version. It is a limited revision of v4.0 that adds no new requirements; it clarifies wording, corrects formatting and aligns the text with other PCI publications. Examples include changing sensitive authentication data language from not retained to not stored after authorisation and clarifying that requirement 11.2.1 on wireless access points applies even where policy prohibits wireless. Assess against 4.0.1, not 4.0.

Yes. PCI DSS v4.0 introduced 64 new requirements, which were either effective immediately or best practice only until 31 March 2025. Since that date they must be fully considered in every assessment. The PCI SSC's own FAQ also says requirements that a third-party service provider meets on your behalf must be fully considered in your assessment, so an outsourced control still needs evidence.

Yes. In January 2025 the PCI SSC removed requirements 6.4.3 and 11.6.1 (payment page script management and tamper detection) from SAQ A, along with the targeted risk analysis in 12.3.1 that was tied to 11.6.1. In their place, a merchant using SAQ A must confirm its e-commerce site is not susceptible to attacks from malicious scripts. Merchants who cannot confirm that must use SAQ A-EP or SAQ D, and service providers, SAQ A-EP and SAQ D merchants still meet 6.4.3 and 11.6.1 in full. Sources differ on how far the new condition reaches, so settle it with your acquirer or QSA.

PCI DSS is a card-brand standard enforced through acquirers and payment partners, not an Indian statute. RBI's Master Direction on payment aggregators does expect aggregators to ensure merchants' infrastructure meets security standards such as PCI DSS as applicable, and bars merchants from storing payment data. Whether you validate by an SAQ or a formal Report on Compliance depends on your merchant or service provider level, which your acquirer or the card brands assign.

No. Using a compliant gateway or processor reduces the cardholder data environment, but it does not remove your obligations. You still validate the requirements that apply to your site, such as the script-protection condition for SAQ A, and you still own the contract, the responsibility matrix and the evidence that the provider's controls cover the requirements assigned to it.

Let's get you PCI DSS 4.0 compliant.

Scope your cardholder data environment with us and get a fixed-scope route to validation.