BlogBest Practices

PCI DSS 4.0 Compliance: What Changed and How to Prepare

PCI DSS 4.0 is the most significant update to the Payment Card Industry Data Security Standard in over a decade. It introduces a customized approach to compliance, strengthens authentication requirements, expands encryption mandates, and requires targeted risk analysis. If you process, store, or transmit cardholder data, here is what you need to know.

20 min readUpdated June 2026

What Is PCI DSS 4.0?

PCI DSS (Payment Card Industry Data Security Standard) is a set of security requirements for any organization that handles payment card data. Version 4.0, released in March 2022 and enforced starting March 2025, replaces version 3.2.1 with modernized requirements that reflect current threat landscapes, cloud-native architectures, and continuous security monitoring.

The standard is organized into 12 requirements across six goals: build and maintain a secure network, protect cardholder data, maintain a vulnerability management program, implement strong access control, regularly monitor and test networks, and maintain an information security policy.

Key Changes in PCI DSS 4.0

Customized Approach

Organizations can now design their own controls that meet the intent of each requirement, rather than following prescriptive controls. Requires documented risk analysis and validation.

Targeted Risk Analysis

Several requirements now mandate targeted risk analysis to determine frequency of activities (scanning, log review, etc.) based on the organization's specific risk profile.

Enhanced Authentication

MFA required for all access to the cardholder data environment (not just remote access). Password length increased to 12 characters minimum. Phishing-resistant MFA recommended.

Expanded Encryption

Encryption of cardholder data on trusted internal networks now required (not just public networks). Disk-level encryption alone no longer meets the requirement.

Continuous Monitoring

Automated mechanisms to detect and alert on security-relevant events in real time. Periodic manual reviews are no longer sufficient for many requirements.

Web Application Security

WAF or equivalent automated technical solution required for public-facing web applications. Annual manual reviews of web apps are no longer an alternative.

Enforcement Timeline

DateMilestoneImpact
March 2022PCI DSS 4.0 publishedOrganizations can begin adopting v4.0
March 2024PCI DSS 3.2.1 retiredAll assessments must use v4.0
March 2025Future-dated requirements enforced64 new requirements become mandatory
OngoingAnnual assessmentsContinuous compliance validation required

PCI DSS 4.0 Checklist for Cloud-Native

Network Security (Req 1–2)

Define and enforce network segmentation between CDE and non-CDE workloads
Implement security groups and network policies with deny-all defaults
Use VPC/VNet isolation for cardholder data environments
Document and validate all network flows crossing trust boundaries

Data Protection (Req 3–4)

Encrypt cardholder data at rest with AES-256 or equivalent
Encrypt all data in transit with TLS 1.2+ (including internal networks)
Implement key management with automated rotation
Minimize data retention — delete cardholder data when no longer needed

Vulnerability Management (Req 5–6)

Deploy automated vulnerability scanning (SAST, SCA, container scanning) in CI/CD
Remediate critical vulnerabilities within 30 days, high within 90 days
Implement WAF or equivalent for all public-facing web applications
Maintain secure development practices with security training for developers

Access Control & Monitoring (Req 7–12)

Enforce MFA for all access to cardholder data environments
Implement RBAC with least-privilege access — review quarterly
Deploy continuous security monitoring with automated alerting
Maintain audit trails for all access to cardholder data and system components
Conduct regular penetration testing and security assessments
Document and maintain an information security policy

Automate PCI DSS Compliance with TigerGate

TigerGate maps your security controls to PCI DSS 4.0 requirements automatically. CSPM scans cloud configurations, SAST/SCA scans code, and eBPF provides continuous runtime monitoring evidence.