trio.so
Templates

PCI Compliance Checklist for PCI DSS v4.0.1 (PDF + Excel)

PCI compliance checklist for PCI DSS v4.0.1: the 12 requirements, the 51 future-dated items, CDE scoping and SAQ vs ROC, with a free PDF and Excel tracker.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

A PCI compliance checklist turns the Payment Card Industry Data Security Standard (PCI DSS) into tasks you can assign and prove. This one follows PCI DSS v4.0.1, the only version in force, and covers all 12 requirements, their 63 sections and the 51 requirements that became mandatory on 31 March 2025.

It is written for IT managers, security leads and MSPs at merchants and service providers that take, process or store card payments. Use it to scope your cardholder data environment, run a gap analysis and get ready for an SAQ or a QSA assessment.

The free download has a PDF guide and an Excel tracker. The tracker lists every requirement section with a future-dated flag, owner, status and evidence columns, and comes with a scope inventory, a device controls sheet, an SAQ selector and a progress dashboard.

Preview of the PCI DSS v4.0.1 checklist PDF and Excel tracker
Preview of the PCI DSS v4.0.1 checklist PDF and Excel tracker

TL;DR

In short

  • PCI DSS v4.0.1 was published in June 2024. v3.2.1 retired on 31 March 2024 and v4.0 on 31 December 2024.
  • All 51 future-dated requirements, such as MFA for all CDE access and 12-character passwords, have been required since 31 March 2025.
  • PCI DSS is not a law. The card brands and your acquirer require it through their rules and your merchant agreement.
  • There is no PCI certificate. You validate with a Report on Compliance (ROC) or a Self-Assessment Questionnaire (SAQ), plus an Attestation of Compliance (AOC), every year.
  • Scope comes first: every system that stores, processes or sends card data, or could affect its security, is in scope.

What Is PCI DSS?

PCI DSS is a set of technical and operational security requirements for anyone that stores, processes or transmits payment card data, or could affect its security. The PCI Security Standards Council (PCI SSC) publishes it. American Express, Discover, JCB International, Mastercard and Visa founded the council, and each of them runs its own compliance program.

It is an industry standard, not a law. PCI SSC writes the standard and trains assessors, but it does not enforce compliance or decide who has to validate. The card brands and acquiring banks do that, and the obligation reaches a merchant through card-brand rules and the merchant agreement with its acquirer. If a requirement ever conflicts with local law, the law wins.

The standard protects "account data". That covers cardholder data (the card number, or PAN, plus the cardholder name, expiry date and service code) and sensitive authentication data such as full track data, card verification codes and PINs. It applies whatever your size or transaction volume. What changes with size is how you prove it, which our guide to PCI DSS compliance for small business covers in more detail.

PCI DSS 4.0.1: What Changed and What Is Retired

PCI SSC published PCI DSS v4.0.1 on 11 June 2024. It is a limited revision of v4.0 (March 2022) with no added or deleted requirements: clarifications, corrected errors and extra guidance. One change matters for patching. Requirement 6.3.3 again sets the one-month deadline for critical vulnerabilities only, as v3.2.1 did.

PCI DSS timeline: v3.2.1 retired 31 March 2024, v4.0.1 published 11 June 2024, v4.0 retired 31 December 2024, future-dated requirements in force from 31 March 2025
PCI DSS timeline: v3.2.1 retired 31 March 2024, v4.0.1 published 11 June 2024, v4.0 retired 31 December 2024, future-dated requirements in force from 31 March 2025

v4.0 brought in 64 new requirements. Thirteen applied at once. The other 51 were best practice until 31 March 2025 and are now mandatory in every assessment. If your last gap analysis predates that date, the PCI DSS 4.0 requirements you marked "future" are now open findings. No newer version has been published; PCI SSC asked for comments on v4.0.1 in June and July 2026 without naming a date for the next one.

Scope First: Your Cardholder Data Environment

PCI DSS scope decides how much of this checklist applies to you, so do it before anything else. The cardholder data environment (CDE) is the people, processes and technology that store, process or transmit account data. Systems that connect to the CDE, or could affect its security, are in scope too: the directory that controls logins to it, the admin laptops that reach it, and the patch, logging and anti-malware servers that serve it.

PCI DSS scope: the cardholder data environment, the connected and security-impacting systems around it, and segmented systems outside scope
PCI DSS scope: the cardholder data environment, the connected and security-impacting systems around it, and segmented systems outside scope

Segmentation can take a system out of scope, but only if you can show it works, and an assessor will test it. Three habits keep scope honest:

  • Map how card data enters, moves through and leaves your business, channel by channel (store, web, phone).
  • Keep an inventory of in-scope system components and what each one does (12.5.1). The Excel tracker's scope tab has columns for that.
  • Confirm scope at least every 12 months and after big changes (12.5.2). Service providers must do it every six months (12.5.2.1).

The cheapest scope reduction is not keeping card data at all. Tokenization, a hosted payment page or a validated point-to-point encryption (P2PE) solution can shrink scope a lot.

The PCI DSS 12 Requirements and What to Check

PCI DSS groups its 12 principal requirements under six goals. Each requirement splits into X.Y sections (63 in all), and in v4.x the first section of every requirement asks for written policies, procedures and assigned roles. The requirement titles below are PCI SSC's; the checks are our summary, not the standard's text.

The 6 PCI DSS goals and 12 requirements, with the number of sections and future-dated items in each
The 6 PCI DSS goals and 12 requirements, with the number of sections and future-dated items in each
#RequirementWhat to check
1Install and Maintain Network Security Controls
Goal 1: Build and Maintain a Secure Network and Systems
Network security controls (firewalls and similar) are configured and reviewed; CDE traffic is limited to what is needed; laptops that also reach the internet run controls users can't turn off.
2Apply Secure Configurations to All System Components
Goal 1: Build and Maintain a Secure Network and Systems
Every system type has a written hardening standard; vendor default passwords are changed or accounts disabled; unneeded services are off; Wi-Fi in scope is set up securely.
3Protect Stored Account Data
Goal 2: Protect Account Data
You keep as little account data as possible; no sensitive authentication data after authorization; card numbers are masked on screen and unreadable where stored; keys are managed.
4Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks
Goal 2: Protect Account Data
Card numbers sent over open, public networks use strong cryptography with valid certificates; you keep an inventory of trusted keys and certificates.
5Protect All Systems and Networks from Malicious Software
Goal 3: Maintain a Vulnerability Management Program
Anti-malware runs and updates itself on systems at risk; removable media is scanned; staff are protected against phishing.
6Develop and Maintain Secure Systems and Software
Goal 3: Maintain a Vulnerability Management Program
Vulnerabilities are ranked; critical patches go on within one month; custom software is inventoried and built securely; payment-page scripts are controlled.
7Restrict Access to System Components and Cardholder Data by Business Need to Know
Goal 4: Implement Strong Access Control Measures
Access follows job need; all user accounts and privileges are reviewed every six months; system and application accounts get least privilege.
8Identify Users and Authenticate Access to System Components
Goal 4: Implement Strong Access Control Measures
Unique IDs; idle sessions re-authenticate after 15 minutes; lockout after 10 failed attempts; 12-character passwords; MFA for all non-console access into the CDE.
9Restrict Physical Access to Cardholder Data
Goal 4: Implement Strong Access Control Measures
Physical access to the CDE is controlled; media with card data is tracked and destroyed properly; card-reading devices are listed and inspected for tampering.
10Log and Monitor All Access to System Components and Cardholder Data
Goal 5: Regularly Monitor and Test Networks
Audit logs capture the right events, are protected, reviewed daily (with automated tools) and kept 12 months; control failures raise alerts.
11Test Security of Systems and Networks Regularly
Goal 5: Regularly Monitor and Test Networks
Rogue Wi-Fi checks; internal and external scans every three months; yearly penetration tests; intrusion detection; payment pages watched for changes.
12Support Information Security with Organizational Policies and Programs
Goal 6: Maintain an Information Security Policy
Security policy, acceptable-use rules, targeted risk analyses, scope confirmed yearly, awareness training, vendor management and an incident response plan.

The Excel tracker breaks each row down into its sections, with an owner, a due date, a status and the evidence to keep. For the official wording, download the standard free from the PCI SSC Document Library.

The Future-Dated Requirements That Trip Teams Up

Give the 51 future-dated requirements their own pass, because gap analyses done before 2025 often marked them as future work. Requirement 12 holds 11 of them; Requirements 3 and 8 hold 7 each.

The 51 future-dated PCI DSS requirements by principal requirement
The 51 future-dated PCI DSS requirements by principal requirement
  • Targeted risk analysis (12.3.1). Wherever PCI DSS lets you choose how often to do something, you need a written risk analysis that justifies the frequency, reviewed every 12 months.
  • MFA into the CDE (8.4.2) and how MFA works (8.5.1). MFA now covers all non-console access into the CDE, not just admins, and it must resist replay and bypass.
  • Passwords (8.3.6). At least 12 characters, or 8 where a system can't do 12, with letters and numbers. The old minimum was 7.
  • Payment pages (6.4.3 and 11.6.1). Every script on the payment page needs authorization and an integrity check, and a tool must flag unauthorized changes at least weekly. Since 31 March 2025, merchants on SAQ A that embed a provider's payment page confirm their site is protected against script attacks instead.
  • Phishing (5.4.1) and training (12.6.3.1). Automated anti-phishing controls, plus training on phishing and social engineering.
  • Logs (10.4.1.1). Log review by automated mechanisms.
  • Scans (11.3.1.2). Internal vulnerability scans run with credentials.
  • Accounts (7.2.4). A review of all user accounts and privileges every six months.
  • Disk encryption (3.5.1.2). Full-disk encryption on its own now counts only for removable media.

The tracker has a separate tab for all 51, each with our short label, who it applies to and a status column.

How PCI DSS Compliance Is Validated

Validation is how you show your acquirer or customers where you stand. There are two routes:

  • Report on Compliance (ROC). A Qualified Security Assessor (QSA), or an Internal Security Assessor (ISA) where the card brand allows it, tests your controls and writes the ROC on PCI SSC's template.
  • Self-Assessment Questionnaire (SAQ). You answer the SAQ that matches your payment setup. Roughly, SAQ A fits fully outsourced e-commerce, B-IP fits standalone IP-connected terminals, SPoC fits phones or tablets with a secure card reader, and SAQ D is the full set for everyone else, including every SAQ-eligible service provider (SAQ D for Service Providers).

Either way you sign an Attestation of Compliance (AOC) and send it, with any Approved Scanning Vendor (ASV) scan reports, to your acquirer. Merchant levels decide which route you take, and each card brand sets its own. On Visa's scale, Level 1 is over 6 million Visa transactions a year and needs an annual ROC by a QSA; Levels 2 and 3 complete an annual SAQ, and for Level 4 the acquirer sets the requirements. Ask your acquirer which level and SAQ apply to you; the workbook's SAQ selector only gives a first guess.

Two more points come up in planning. Entities that self-assess with an SAQ cannot use the customized approach, which needs a QSA or ISA. And PCI SSC's free Prioritized Approach tool sorts the requirements into six milestones, starting with "don't store data you don't need"; download it from the Document Library and use it alongside this checklist. Our PCI compliance audit guide walks through the assessment itself.

PCI DSS Device Requirements: The Exact Numbers

PCI DSS never mentions MDM, but a good part of it lands on the laptops, desktops, phones and payment terminals in scope. These are the parameters assessors check, from v4.0.1:

PCI DSS device requirements with their parameters, and which ones a device management tool can set or report
PCI DSS device requirements with their parameters, and which ones a device management tool can set or report
  • 8.2.8: a session idle for more than 15 minutes needs the user to log in again.
  • 8.3.4: lock a user ID after no more than 10 invalid attempts, for at least 30 minutes or until identity is confirmed.
  • 8.3.6: passwords of at least 12 characters (8 if the system can't), with letters and numbers.
  • 6.3.3: critical patches within one month of release; others on a risk-based timeline. Our patch management policy template helps you write it down.
  • 5.2 and 5.3: anti-malware on systems at risk, updating automatically, logging, and locked so users can't disable it.
  • 1.5.1: any device, company or employee owned, that connects to both an untrusted network such as the internet and the CDE needs security settings that stay on and that users can't change without time-limited approval.
  • 3.5.1.2: disk or partition encryption, such as BitLocker or FileVault, makes card numbers unreadable only on removable media. A card number stored on a laptop's internal drive needs another method from 3.5.1 as well, so the better fix is not to store it there. Our guide to full disk encryption explains what it does protect.
  • 12.5.1 and 12.3.4: an inventory of in-scope components and a review of hardware and software in use every 12 months.
  • 9.5.1: a list of card-reading devices with make, model, location and serial number, inspected for tampering. See our POS security guide.

How to Run a PCI DSS Gap Analysis

A PCI DSS gap analysis compares what you do today with each requirement and turns the difference into a plan. With the tracker it takes these steps:

  1. Fill in the scope tab: every system component, what it does, whether it stores card data, and its category (CDE, connected, out of scope).
  2. Pick your likely SAQ in the SAQ selector, then confirm it with your acquirer. Mark requirements outside your SAQ or your entity type as not applicable.
  3. Go through the Requirements tab section by section. Every row that isn't Done is a gap; give it an owner and a due date.
  4. Check the Future-dated tab separately. Older gap analyses often skipped these rows.
  5. Set the device settings in the Device controls tab and record exceptions with a reason.
  6. Log the evidence as you collect it: policies, configuration exports, review sign-offs, scan and test reports.
  7. Watch the dashboard for progress by requirement and by goal, and for overdue rows.

Automation helps with the evidence part. Our guide to automated tools for PCI DSS compliance compares the tool types.

Common PCI DSS Mistakes

  • Calling a vendor "PCI certified". PCI SSC issues no seal or logo for compliance and does not endorse security products, and it warns against third-party "compliance certificates".
  • Treating the AOC as permanent. It records one assessment, and you repeat it every year.
  • Counting BitLocker or FileVault as protection for stored card numbers on fixed drives (3.5.1.2).
  • Leaving phones and tablets out of scope when they take payments or reach the CDE.

If you work across several frameworks, our NIST compliance checklist, ISO 27001 checklist, CIS Controls checklist and HIPAA compliance checklist come with similar trackers.

Where trio.so Fits

Most of PCI DSS is network security, logging, testing, physical security and policy, and trio.so does none of that. It handles the device settings behind several requirements, from one console across Windows, Mac, iOS and Android:

See how trio.so handles the device side of PCI DSS, area by area, with the evidence you can show your assessor.

  • Encryption (3.5): enforce BitLocker on Windows and FileVault on Mac with FileVault recovery key escrow, enforce encryption on phones, and see encryption status per device. Under 3.5.1.2 this alone does not protect stored card numbers on fixed disks.
  • Idle lock (8.2.8 on endpoints): passcode and screen-lock policies with a timeout of 15 minutes or less.
  • Patching (6.3.3): OS update management.
  • Secure configuration and approved software (1.5.1, 2.2, 12.2.1): enforced device policies and app allow and block lists.
  • Inventory (12.5.1, 12.3.4): device inventory, including installed apps on Windows, macOS, iOS and Android.
  • Lost and retired devices (9.4): lock lost Macs, iPhones and Android devices, and wipe company-owned devices.
  • Evidence: the compliance engine checks device settings against framework device controls, PCI DSS among them, and you can export the evidence for your QSA or SAQ.

trio.so does not assess or validate PCI DSS compliance, and using it does not make you PCI DSS compliant. Your QSA or your SAQ does the validating, and account lockout, MFA, anti-malware, logging, scanning and payment-page requirements need other tools. Learn more about compliance automation. Plans start at $5 per device.

Start free trial Book a demo

14-day free trial. No credit card required.

Sources. Last reviewed October 2026. PCI DSS is a standard of the PCI Security Standards Council. trio.so is not affiliated with or endorsed by PCI SSC. Requirement summaries here are paraphrased; get the official text from the PCI SSC Document Library. This article is guidance, not legal advice or an assessment. The device mapping is ours.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Start your free trial

No credit card required
Full access to all features

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

No. There is no PCI certificate for merchants or service providers, and PCI SSC issues no seal or logo. A checklist shows you the gaps; validation happens each year through a Report on Compliance (ROC) from a QSA or a Self-Assessment Questionnaire (SAQ), with a signed Attestation of Compliance (AOC) that goes to your acquirer.

The PCI DSS 12 requirements are: install and maintain network security controls; apply secure configurations; protect stored account data; protect cardholder data with strong cryptography in transit; protect systems from malicious software; develop and maintain secure systems and software; restrict access by business need to know; identify users and authenticate access; restrict physical access; log and monitor all access; test security regularly; and support security with organizational policies and programs.

PCI DSS v4.0.1, published in June 2024, is the only active version. v4.0 retired on 31 December 2024 and v3.2.1 on 31 March 2024. The 51 future-dated requirements from v4.0 have been mandatory since 31 March 2025.

No. PCI DSS is an industry standard. The card brands and acquiring banks require it through their rules and merchant agreements, and they set any fines or fees by contract. Some laws may add requirements, and where a law conflicts with PCI DSS, the law applies.

The cardholder data environment (CDE) is the people, processes and technology that store, process or transmit account data. Systems connected to the CDE or able to affect its security are also in PCI DSS scope unless segmentation removes them.

SAQ D is the Self-Assessment Questionnaire that covers all PCI DSS requirements. SAQ D for Merchants is for merchants that don't fit any other SAQ, and SAQ D for Service Providers is the only SAQ for service providers that are allowed to self-assess.

Not for stored card numbers on fixed drives. Under requirement 3.5.1.2, disk or partition encryption alone makes card numbers unreadable only on removable media. On a laptop's internal drive you need another method from 3.5.1, such as tokenization or strong cryptography of the data itself, or better, no card numbers there at all.

Related

From the blog

The related industry news, interviews, technologies, and resources.