PCI DSS Compliance Checklist: 12 Requirements (v4.0.1)
A PCI DSS compliance checklist is a working list of the controls you must have in place, and the evidence you must keep, to meet the Payment Card Industry Data Security Standard (PCI DSS). This one is built on PCI DSS v4.0.1, the only active version, and walks through all 12 requirements in order.
Before you start ticking boxes, do one thing first: shrink your scope. The fewer systems that touch card data, the shorter this checklist gets. For the bigger picture on the framework, see the PCI DSS compliance guide.
Before the Checklist: Confirm Version and Scope
Which version applies
PCI DSS v4.0.1 is the version in force. The PCI Security Standards Council (PCI SSC) published it in June 2024 as a limited revision of v4.0. It added no new requirements and deleted none. Version 4.0 was retired on 31 December 2024.
The bigger change already happened. Version 4.0 introduced dozens of new requirements marked as best practice until 31 March 2025. That date has passed. Every one of them is now mandatory, and assessors test them.
Scope comes first
Your scope is the cardholder data environment (CDE): every system that stores, processes, or transmits account data, plus anything connected to it. Requirement 12.5.2 makes you document and confirm that scope at least once every 12 months and after any significant change. Service providers must do it every six months (12.5.2.1).
The highest-leverage move is to keep card numbers off your servers. A hosted checkout or a tokenizing integration, like Stripe Checkout or Elements, keeps the primary account number (PAN) inside the processor's environment. That can cut your checklist from the full SAQ D control set to the short SAQ A.
Which SAQ or ROC you complete
Your validation path depends on your merchant level and how you take payments. Most SaaS companies self-assess with a Self-Assessment Questionnaire (SAQ). Large merchants and many service providers need a Report on Compliance (ROC) from a Qualified Security Assessor (QSA).
This checklist covers the full standard. If you qualify for a shorter SAQ, only the subset in that SAQ applies to you. The PCI DSS SAQ guide explains which one fits your payment flow.
Build and Maintain a Secure Network and Systems
Requirement 1: Network security controls
Requirement 1 is about controlling traffic into and out of the CDE. "Network security controls" covers firewalls, cloud security groups, and similar tools.
- Document network diagrams and cardholder data flow diagrams, and keep them current
- Restrict inbound and outbound traffic to what the business needs
- Review network security control rules at least once every six months
- Separate the CDE from untrusted networks, including the internet
- Secure any device that connects to both the CDE and an untrusted network, such as laptops
Requirement 2: Secure configurations
Requirement 2 targets default settings, which attackers know by heart.
- Change all vendor default passwords before a system goes live
- Remove or disable unnecessary services, protocols, and accounts
- Apply configuration standards based on an industry benchmark, such as CIS
- Encrypt all non-console administrative access
- Assign one primary function per server, or isolate functions with different security levels
Protect Account Data
Requirement 3: Protect stored account data
The best way to meet Requirement 3 is to store no card data at all. If you must store it, the controls get heavy.
- Keep a data retention policy and delete card data you no longer need
- Never store sensitive authentication data (full track data, CVV, PIN) after authorization
- Mask PAN when displayed, showing no more than the first six and last four digits
- Render stored PAN unreadable with strong cryptography, tokenization, or truncation
- Use keyed cryptographic hashes if you hash PAN (3.5.1.1)
- Do not rely on disk-level encryption alone, except for removable media (3.5.1.2)
- Block copying or moving PAN through remote-access tools unless authorized (3.4.2)
- Document and run key management procedures
Requirement 4: Strong cryptography in transit
Requirement 4 covers PAN sent over open, public networks.
- Use strong cryptography, such as TLS 1.2 or higher, for all PAN transmission
- Confirm certificates are valid and not expired (4.2.1)
- Keep an inventory of trusted keys and certificates (4.2.1.1)
- Never send unprotected PAN through email, chat, or messaging tools
Maintain a Vulnerability Management Program
Requirement 5: Protect against malicious software
- Deploy anti-malware on systems at risk of malware
- Keep anti-malware current and running, with logs retained
- Scan removable media when it is inserted or mounted (5.3.3)
- Run processes and automated tools to protect staff from phishing (5.4.1)
The anti-phishing control in 5.4.1 is one of the 2025 requirements. In practice, it means email filtering with DMARC, SPF, and DKIM, plus link and attachment scanning.
Requirement 6: Secure systems and software
Requirement 6 is the one most SaaS engineering teams feel. It covers how you build and patch software.
- Follow a secure software development process with security training for developers
- Review custom code for vulnerabilities before release
- Keep an inventory of bespoke and custom software and its third-party components (6.3.2)
- Rank vulnerabilities by risk, and install critical patches within one month of release
- Protect public-facing web apps with an automated tool that detects and blocks attacks, such as a web application firewall (6.4.2)
- Manage payment page scripts: authorize each one, check its integrity, and keep an inventory with a justification (6.4.3)
- Follow change control, with separate test and production environments
Requirement 6.4.3 exists because of web skimming attacks, where malicious JavaScript steals card numbers from a checkout page. If any script loads on your payment page, you need to know what it is and why it is there.
Implement Strong Access Control Measures
Requirement 7: Restrict access by need to know
- Define access roles based on job function and least privilege
- Require documented approval for access
- Review all user accounts and privileges, including vendor accounts, at least every six months (7.2.4)
- Assign and manage application and system accounts on least privilege (7.2.5)
Requirement 8: Identify users and authenticate access
Requirement 8 changed the most in v4.0. Two of its controls catch many teams out.
- Give every user a unique ID; no shared or group accounts without strict controls
- Require multi-factor authentication (MFA) for all access into the CDE (8.4.2), not just remote access
- Set passwords to at least 12 characters, with letters and numbers (8.3.6)
- Lock accounts after no more than 10 failed attempts
- Prevent interactive login with system and application accounts unless approved (8.6.1)
- Remove hard-coded passwords from scripts and configuration files (8.6.2)
If a system cannot support 12 characters, 8.3.6 allows a minimum of eight. Document that exception.
Requirement 9: Restrict physical access
For a cloud-native SaaS, your cloud provider covers most of Requirement 9 for its data centers. Get its Attestation of Compliance and keep it on file.
- Control physical access to any on-premises systems in scope
- Secure and inventory media that contains card data
- Destroy media securely when it is no longer needed
- Inspect card-reading devices for tampering, if you run point-of-sale hardware
Regularly Monitor and Test Networks
Requirement 10: Log and monitor all access
- Log all access to cardholder data and all actions by administrators
- Protect logs from changes and keep them for at least 12 months, with three months immediately available (10.5.1)
- Use automated tools to review audit logs (10.4.1.1)
- Review security event logs at least daily
- Sync clocks across all systems
- Detect, alert on, and respond to failures of critical security controls (10.7.2)
Daily manual log review is no longer realistic, and 10.4.1.1 now makes automation mandatory. A SIEM (security information and event management) tool with alerting is the usual answer.
Requirement 11: Test security regularly
Requirement 11 sets the testing calendar. Map these dates before your assessment window.
- Run internal vulnerability scans at least once every three months
- Use authenticated scanning for internal scans (11.3.1.2)
- Run external scans through an Approved Scanning Vendor (ASV) at least once every three months, with passing results
- Run internal and external penetration tests at least once every 12 months and after significant changes
- Test segmentation controls at least once every 12 months, or every six months for service providers
- Detect rogue wireless access points at least once every three months
- Deploy change- and tamper-detection on payment pages (11.6.1)
Requirement 11.6.1 pairs with 6.4.3. Together they target the same web skimming risk from two angles: controlling scripts, and alerting when headers or scripts change. For what testing costs, see penetration testing cost.
Maintain an Information Security Policy
Requirement 12: Policies and programs
Requirement 12 ties the program together. It is also where most of your documentation lives.
- Publish an information security policy and review it at least once every 12 months
- Assign security roles and responsibilities
- Perform a targeted risk analysis for any requirement where you choose the frequency (12.3.1)
- Keep an inventory of in-scope system components (12.5.1)
- Document and confirm PCI DSS scope at least every 12 months (12.5.2)
- Run security awareness training at hire and at least once every 12 months, including phishing and social engineering (12.6.3.1)
- Screen personnel before they get access to the CDE
- Keep a list of third-party service providers, with written agreements and annual monitoring of their compliance status (12.8)
- Maintain an incident response plan and test it at least once every 12 months
- Include procedures for finding stored PAN where it is not expected (12.10.7)
What Changed in v4.0 That Teams Still Miss
The 2025 requirements are now 19 months old, but they still show up as findings. These are the ones worth a second look:
- MFA for all CDE access (8.4.2). Earlier versions only required MFA for remote access. Now it covers every non-console login into the CDE.
- Payment page script controls (6.4.3 and 11.6.1). These matter most for e-commerce merchants on SAQ A-EP or SAQ D. In January 2025, PCI SSC removed them from SAQ A and replaced them with an eligibility check that your site is not open to script attacks.
- Automated log review (10.4.1.1). Manual review alone no longer meets the requirement.
- Targeted risk analysis (12.3.1). Wherever the standard lets you pick a frequency, you must document the analysis behind your choice.
- Authenticated internal scans (11.3.1.2). Unauthenticated scans miss too much, so they no longer satisfy the requirement.
The SAQ A change is covered in detail in the PCI DSS SAQ guide.
How to Run This PCI DSS Compliance Checklist
A checklist is only useful if you work it in the right order. Here is the sequence that wastes the least effort:
- Map card data flows. Find every place a card number could enter your systems, including support tickets and logs.
- Reduce scope. Move to a tokenizing integration and isolate anything left with segmentation.
- Pick your validation path. Confirm your merchant level with your acquirer and choose the SAQ or ROC.
- Run a gap assessment. Score yourself against the controls in your SAQ, not the whole standard.
- Remediate. Fix the gaps, starting with MFA, logging, and scanning, since those need time to produce evidence.
- Collect evidence. Assessors want proof, such as scan reports, access review records, and training logs.
- Validate and submit. Complete the SAQ or ROC and the Attestation of Compliance, then send them to your acquirer.
- Keep it running. Put quarterly, semiannual, and annual tasks on a calendar so next year is easier.
PCI DSS compliance for SaaS service providers
If you store, process, or transmit card data on behalf of other businesses, you are a service provider, not just a merchant. That adds requirements, such as six-month scope confirmation and six-month segmentation testing. Your customers will also ask for your Attestation of Compliance. The PCI DSS for SaaS post covers the merchant versus service provider line.
Using this alongside SOC 2 or ISO 27001
Much of PCI DSS overlaps with other security frameworks. Access reviews, logging, vulnerability management, and incident response all carry across. If you already hold SOC 2 or ISO 27001, start your gap assessment from that evidence. See compliance controls overlap for where the work double-counts.
For the full engagement, including scoping, gap assessment, and SAQ or ROC support, see the PCI DSS service page. For background on the framework, read the PCI DSS compliance guide. To choose your questionnaire, use the PCI DSS SAQ guide, and for platform-specific scoping, see PCI DSS for SaaS.
Frequently Asked Questions
What is the current version of PCI DSS? PCI DSS v4.0.1, published in June 2024. It is a limited revision of v4.0 with no new or deleted requirements. Version 4.0 was retired on 31 December 2024, and the requirements that were best practice until 31 March 2025 are now mandatory.
What are the 12 requirements of PCI DSS? Network security controls, secure configurations, protecting stored data, encryption in transit, anti-malware, secure software, need-to-know access, user authentication, physical access, logging and monitoring, regular testing, and policies and programs.
How often do you need to complete a PCI DSS compliance checklist? Validation is annual. Inside the year, controls run on shorter cycles: quarterly scans, access reviews every six months, and daily log review. Scope must be confirmed every 12 months, or every six months for service providers.
Does using Stripe make me PCI compliant? No. It shrinks your scope, often to SAQ A, but you still validate the part that remains. The processor's compliance covers its environment, not yours.
What happens if you fail PCI DSS compliance? Consequences come through your acquiring bank. Expect possible fines passed down from the card brands, higher processing fees, or loss of your merchant account. After a breach, add forensic and card reissuance costs.
Need Help Working Through the Checklist?
ShieldKey Solutions helps SaaS teams scope PCI DSS down, close the v4.0.1 gaps, and complete the right SAQ or ROC. We start with your card data flows and cut the checklist to only what applies.