LATEST ARTICLES Breaking archive
Friday, November 13, 2026 · Your local date
Wade Bush
Apps, plugins & creator toolsPractical digital products, instant access. Built by WadeBush.
Visit marketplace

PCI DSS v4.0 compliance checklist for 2026

Tarptautinis saugumo technologijų ir procesų standartas. Šis saugumo standartas reglamentuoja reikalavimus bendrovėms priimančioms atsiskaitymus kortelėmis ir tvarkančioms klientų

Use this PCI DSS v4.0 compliance checklist to focus your 2026 priorities. Version 4.0 retired PCI DSS v3.2.1 and made previously future‑dated controls fully effective, so this year’s assessments should reflect the new requirements and templates.

Why 2026 matters for PCI DSS v4.0

PCI DSS v4.0 became the sole active standard after the retirement of v3.2.1 on March 31, 2024. Future‑dated v4.0 requirements then took full effect on March 31, 2025, and now apply in all 2026 validations. (blog.pcisecuritystandards.org)

Card brands continue to enforce compliance through their own programs. Visa’s Core Rules require acquirers to report merchant PCI DSS status, and Mastercard’s Site Data Protection (SDP) program sets validation expectations for merchants and service providers. Coordinate early with your acquirer to confirm level and due dates. (cis.visa.com)

PCI DSS v4.0 compliance checklist: the essentials

Use these focused steps to organize work and document evidence for your 2026 assessment.

1) Confirm scope and validation approach

  • Map your cardholder data environment (CDE) and clarify in‑scope systems. Use network‑level controls where appropriate, but verify coverage. (pcisecuritystandards.org)
  • Choose the defined or customized approach per control. If you use the customized approach, complete targeted risk analyses (TRAs) for each customized requirement and retain Appendix E2 evidence. (blog.pcisecuritystandards.org)
  • Ensure you are using v4.0.1 SAQs/ROC templates for 2026 assessments. (blog.pcisecuritystandards.org)

2) Lock down e‑commerce payment pages (Reqs 6.4.3 and 11.6.1)

  • Inventory every script that executes on payment pages, justify its business need, and implement a method to assure each script’s integrity. (pcisecuritystandards.org)
  • Deploy change‑and‑tamper detection that alerts on unauthorized modification to HTTP headers and page contents as received by the consumer’s browser. (pcisecuritystandards.org)
  • Use the Council’s information supplement to align controls and monitoring with current e‑skimming threats. (blog.pcisecuritystandards.org)
  • Validating via SAQ A? The Council removed 6.4.3 and 11.6.1 from SAQ A; confirm your setup truly qualifies and follow the updated eligibility notes. (blog.pcisecuritystandards.org)

3) Perform and document Targeted Risk Analyses (Req. 12.3.x)

  • Complete TRAs where v4.0 allows risk‑based frequencies (for example, some logging reviews) and when using the customized approach. Keep the official TRA artifacts with rationale and frequency. (blog.pcisecuritystandards.org)
  • Update your security awareness program to reflect v4.0 emphasis, including social‑engineering risks. (blog.pcisecuritystandards.org)

4) Update “firewalls” to network security controls (Req. 1)

  • v4.0 adopts the broader term network security controls (NSCs) to reflect modern technologies. Review rulesets, segmentation, and configuration standards accordingly. (pcisecuritystandards.org)

5) Align logging and monitoring

  • Automate reviews for specified events and set documented, TRA‑driven frequencies for others. Ensure retention and alerting meet your risk posture and program requirements. (blog.pcisecuritystandards.org)

6) Verify third‑party service provider compliance (Reqs 12.8–12.9)

  • Maintain a current inventory of third‑party service providers (TPSPs) that can impact account data. Obtain confirmations of their PCI DSS compliance aligned to your services in scope. (pcisecuritystandards.org)
  • Confirm brand‑specific reporting to your acquirer, including validation evidence for required merchant levels. (cis.visa.com)

7) Refresh policies, training, and incident response

  • Ensure responsibilities are assigned, 24/7 breach response contacts are designated, and procedures reflect v4.0 terms and control objectives. (blog.pcisecuritystandards.org)

Common pitfalls to avoid in 2026

  • Using v3.2.1 documents or language in policies and evidence. Migrate to the v4.0.1 reporting materials and terminology. (blog.pcisecuritystandards.org)
  • Assuming hosted checkout removes all web risks. Even with outsourced payments, merchants must protect their own pages from script attacks unless they meet the updated SAQ A scope. (pcisecuritystandards.org)
  • Leaving e‑commerce monitoring to periodic scans only. 11.6.1 expects alerting on unauthorized changes as pages are delivered to consumers. (pcisecuritystandards.org)

Make brand compliance part of your plan

PCI SSC publishes the standard and templates, but card brands enforce compliance. Build milestones around what your acquirer needs for Visa’s AIS reporting and Mastercard’s SDP validation to avoid non‑compliance assessments or processing issues. (cis.visa.com)

Next steps

  • Schedule a 2026 internal readiness review against this checklist.
  • Close gaps for 6.4.3, 11.6.1, and TRA documentation.
  • Confirm SAQ/ROC version and submission timeline with your acquirer.
  • Brief executives on brand reporting and third‑party dependencies.

Sources

Featured image: Payment Card Industry Data Security Standard, CC BY-SA 4.0, via Wikimedia Commons