This page collects the questions answered across our PCI DSS guide, with each answer based on PCI SSC documents. Confirm your own validation requirements with your acquirer or payment brand, since those organizations manage compliance programs.
Browse the questions by topic below, or start from the PCI DSS hub for the full picture.
PCI DSS guide
Who enforces PCI DSS compliance?
The payment brands run their own compliance programs, and acquirers apply brand rules to the merchants they serve. The brands decide who must validate and establish any penalties and fees. PCI SSC maintains the standard and qualifies assessors. Full answer: PCI DSS guide →
Can a business store card verification codes for recurring payments?
Requirement 3.3.1.2 says the card verification code is not stored once authorization is complete, and encryption doesn’t change that. Requirement 3.3.1 has an exception only for issuers and companies that support issuing services with a documented business need. Full answer: PCI DSS guide →
How often should payment terminals be inspected for tampering?
PCI DSS doesn’t set a fixed interval. Under Requirement 9.5.1.2.1, your targeted risk analysis defines how often you inspect payment terminals and what type of inspection you perform. Full answer: PCI DSS guide →
Does PCI DSS apply to payment systems hosted in the cloud?
Yes. PCI DSS lists cloud infrastructure and components among the system components it can cover. Your organization and your cloud provider should document which requirements each one is responsible for. Full answer: PCI DSS guide →
What is PCI DSS?
What does PCI DSS stand for?
PCI DSS stands for Payment Card Industry Data Security Standard. PCI Security Standards Council (PCI SSC) maintains it. Full answer: What is PCI DSS? →
Is PCI DSS a law?
PCI DSS is an industry standard that payment brands and acquirers apply through their compliance programs. Separate laws may also cover payment or personal data. If a requirement conflicts with a local law, the law applies. Full answer: What is PCI DSS? →
Does PCI SSC certify businesses as PCI compliant?
PCI SSC doesn’t certify merchants or service providers. An assessed organization documents its results in a Report on Compliance or Self-Assessment Questionnaire, then attests to them in an Attestation of Compliance. Full answer: What is PCI DSS? →
Is a cardholder name covered by PCI DSS?
It can be. A cardholder name must be protected under PCI DSS when it is stored, processed, or transmitted with the primary account number, or is otherwise present in the cardholder data environment. Full answer: What is PCI DSS? →
How is P2PE related to PCI DSS?
Point-to-point encryption (P2PE) is a separate PCI SSC standard for encrypting account data from the point of interaction. A PCI-listed P2PE solution can significantly reduce the PCI DSS requirements that apply to a merchant, though PCI DSS still applies. Full answer: What is PCI DSS? →
Why it matters
Does PCI SSC issue fines for non-compliance?
PCI SSC is the standards body. The payment brands manage compliance enforcement and establish penalties and fees in their own programs, so your acquirer or payment brand is the right source for the terms that apply to you. Full answer: Why it matters →
What does a Non-Compliant result on an Attestation of Compliance mean?
It means not all sections of the report are complete, or one or more requirements are marked Not in Place. The form records a target date for compliance, and the requesting organization may ask for an action plan. Full answer: Why it matters →
Why is the primary account number so important?
The PAN identifies the card account and is the defining factor for cardholder data. If an organization stores, processes, or transmits it, PCI DSS requirements apply to that environment. Full answer: Why it matters →
Does PCI DSS compliance prevent every data breach?
No standard can remove all risk. PCI DSS provides a minimum set of requirements, and organizations can add controls to address further risks in their own environment. Full answer: Why it matters →
Who needs it
Does a small business need to comply with PCI DSS?
PCI DSS defines a merchant as any entity that accepts payment cards bearing a participating brand’s logo, with no size threshold. Size can affect how you validate, so ask your acquirer which path applies. Full answer: Who needs it →
Do I need PCI DSS if a processor handles all my card payments?
Some requirements usually still apply. Using a third-party provider doesn’t remove your responsibility, and you must manage that provider under Requirement 12.8. Fully outsourced card-not-present merchants may qualify for a shorter questionnaire, such as SAQ A. Full answer: Who needs it →
Does encrypting card data take it out of PCI DSS scope?
Encryption alone is generally insufficient. Systems that perform encryption, decryption, or key management stay in scope, as does encrypted data that isn’t isolated from those processes. A provider without decryption ability may be able to exclude encrypted data if certain conditions are met. Full answer: Who needs it →
Do I need a PCI DSS network diagram?
Requirements 1.2.3 and 1.2.4 call for an accurate network diagram and account data-flow diagram. They appear in a Report on Compliance and SAQ D, while shorter questionnaires such as SAQ A leave them out. Accurate flow information also supports your scope confirmation. Full answer: Who needs it →
Is VoIP in scope for PCI DSS?
It can be. PCI DSS lists VoIP network devices among the network components that count as system components. They are in scope when they handle account data or could affect its security. Full answer: Who needs it →
How it works
What is the difference between a ROC and an SAQ?
Both document the results of a PCI DSS assessment. A Report on Compliance records detailed results and is prepared by a QSA or ISA, while a Self-Assessment Questionnaire documents self-assessment results for eligible entities. Your acquirer or payment brand determines which one you need. Full answer: How it works →
How often does PCI DSS validation happen?
The standard refers to an annual PCI DSS assessment, and payment brands and acquirers set the validation expectations for their programs. Some controls run more often, such as vulnerability scans at least once every three months. Full answer: How it works →
Who signs the Attestation of Compliance?
An executive officer of the assessed merchant signs the merchant attestation. When a QSA is involved, the lead QSA and an authorized officer of the QSA company also sign their acknowledgment. Full answer: How it works →
Is an ASV scan the same as a penetration test?
No. An ASV scan is an external vulnerability scan performed at least once every three months under Requirement 11.3.2. Penetration testing falls under Requirement 11.4 and has its own methodology and frequency. Full answer: How it works →
What happens if an assessment finds a requirement not in place?
You address the open item, and the assessor reassesses to validate that remediation is complete. You then provide an updated report. A control scheduled for a future date doesn’t count as in place. Full answer: How it works →
The 12 requirements
How many requirements are in PCI DSS v4.0.1?
PCI DSS v4.0.1 has 12 principal requirements grouped under six goals. Each principal requirement breaks into detailed requirements with their own testing procedures. Full answer: The 12 requirements →
Does Requirement 8.4.2 mean MFA for everyone who touches the CDE?
Requirement 8.4.2 covers all non-console access into the CDE. It excludes automated application and system accounts, point-of-sale accounts with access to only one card number at a time, and accounts authenticated only with phishing-resistant factors. Full answer: The 12 requirements →
What is the minimum password length under PCI DSS v4.0.1?
Requirement 8.3.6 sets a minimum of 12 characters, with both numeric and alphabetic characters. If a system cannot support 12 characters, the minimum is eight. Full answer: The 12 requirements →
Do Requirements 6.4.3 and 11.6.1 apply if my payment form is in a provider’s iframe?
You manage scripts on your own webpage that includes the iframe, and your provider manages scripts inside its iframe. SAQ A does not include these two requirements, but it has an eligibility criterion about script attacks. Full answer: The 12 requirements →
How long must PCI DSS audit logs be kept?
Requirement 10.5.1 calls for at least 12 months of audit log history. The most recent three months must be immediately available for analysis. Full answer: The 12 requirements →
Cost and timeline
What affects the cost of PCI DSS compliance the most?
Scope and validation type usually shape the rest of the budget. Stored account data, flat networks, multiple payment channels, and custom payment software all add work. Full answer: Cost and timeline →
Why can’t I get a standard PCI DSS timeline?
Your schedule depends on the gaps you find, the size of your scope, and how quickly you can change systems and processes. A short gap list and a major network redesign need very different plans. Full answer: Cost and timeline →
Who sets PCI non-compliance fees?
Payment brands establish penalties and fees in their own programs, not the standard. Ask your acquirer which terms apply to your business. Full answer: Cost and timeline →
Does network segmentation lower PCI DSS costs?
It can. PCI DSS does not require segmentation, but it says proper segmentation may reduce assessment scope and cost, along with the cost and difficulty of maintaining controls. Full answer: Cost and timeline →
Common mistakes
Does using a PCI compliant payment processor make my business compliant?
No. PCI DSS says using a compliant provider does not make a customer compliant or remove its own responsibility. You still manage the relationship and confirm your own compliance as requested. Full answer: Common mistakes →
Can a targeted risk analysis let me run a control less often than PCI DSS states?
No. A targeted risk analysis sets the frequency only where a requirement allows it. To run a fixed-frequency activity less often, you would need a customized approach or a compensating control that qualifies. Full answer: Common mistakes →
Can I mark a requirement In Place if the fix is already scheduled?
No. Controls that are not yet implemented or are scheduled for a future date are not in place. In an SAQ, use Not in Place until the work is finished and tested. Full answer: Common mistakes →
Does a daily log review have to happen on weekends?
Yes. PCI DSS defines daily as every day of the year, not only business days. Automated mechanisms can help you meet this expectation. Full answer: Common mistakes →
How to prepare
What is the difference between Not Applicable and Not Tested on an SAQ?
Not Applicable means you verified that a requirement does not apply to your environment. Not Tested means you excluded it from review without considering whether it could apply, which makes the assessment partial, and not every SAQ offers this response. Full answer: How to prepare →
Is a gap assessment required for PCI DSS?
PCI DSS does not list a gap assessment as a requirement. It is a preparation practice that shows what to fix before you validate. Full answer: How to prepare →
Can I use the customized approach on an SAQ?
No. SAQs cannot document the customized approach. Ask your acquirer or payment brand whether you may complete a ROC instead. Full answer: How to prepare →
What do I submit after completing an SAQ?
You submit the SAQ and Attestation of Compliance, along with any other requested documentation such as ASV scan reports. They go to the organization that requested them, such as your acquirer or a payment brand. Full answer: How to prepare →
Comparisons
Can you use a compensating control with the customized approach?
No. Appendix D of PCI DSS v4.0.1 says compensating controls are not an option with the customized approach. The entity designs the control to meet the objective, so it is expected to implement that control effectively. Full answer: Comparisons →
Can a merchant that completes an SAQ use the customized approach?
No. Entities that complete an SAQ are not eligible for the customized approach. They may elect to have a QSA or ISA perform the assessment and document it in a ROC Template, and should check that choice with their acquirer or payment brand. Full answer: Comparisons →
Can compensating controls be reported on an SAQ?
Yes. SAQs include an In Place with CCW response, which requires a completed Compensating Controls Worksheet. The control must still meet the Appendix B criteria. Full answer: Comparisons →
Who decides whether an entity completes an SAQ or a ROC?
The organizations that manage compliance programs decide, such as an acquirer or payment brand. Ask them which report they expect before you begin an assessment. Full answer: Comparisons →
Choosing a provider
What is a QSA?
A Qualified Security Assessor is a person employed by a QSA company and qualified by PCI SSC to perform PCI DSS assessments. The company itself must also be qualified and appear on the QSA List. Full answer: Choosing a provider →
Does a QSA need to be onsite for a PCI DSS assessment?
Not always. The QSA Program Guide allows onsite work or remote assessment activities that follow PCI SSC guidance. Remote methods may suit situations where onsite work is not feasible or practical, so confirm with the organization accepting your compliance report. Full answer: Choosing a provider →
How does a company gain QSA designation?
The company and at least one employee must satisfy the QSA Qualification Requirements, which cover business legitimacy, independence, insurance, experience, and training. The designation then needs annual requalification by PCI SSC. Full answer: Choosing a provider →
What does a red listing on the QSA List mean?
PCI SSC updates a QSA company’s listing to red during its Quality Remediation program, which notifies merchants and service providers. Ask the company what led to the remediation and how it affects your assessment. Full answer: Choosing a provider →
Staying compliant
What happens if we miss a scheduled PCI DSS activity?
A late activity is not automatically non-compliant if a documented process caught it, explained it, and got it done as soon as possible. Without that process, the requirement is not met until you re-establish the schedule and show the activity was performed. Full answer: Staying compliant →
Does Requirement 12.4 apply to merchants?
No. Requirements 12.4.1, 12.4.2, and 12.4.2.1 apply only to service providers. Merchants can still benefit from similar periodic reviews as a business-as-usual practice. Full answer: Staying compliant →
How often must we confirm PCI DSS scope?
Requirement 12.5.2 calls for confirmation at least once every 12 months and upon significant change. Service providers confirm at least once every six months and upon significant change under 12.5.2.1. Full answer: Staying compliant →
Do we need a targeted risk analysis if we follow PCI SSC’s suggested frequency?
Yes. PCI SSC’s guidance says a targeted risk analysis is still required to document and support the frequency you select, even if you follow its suggested frequency. Full answer: Staying compliant →
Myths
Does using a compliant payment processor make a merchant PCI compliant?
No. PCI DSS says using a compliant third-party service provider does not make a customer compliant. The customer remains responsible for confirming its own compliance. Full answer: Myths →
Are small businesses exempt from PCI DSS?
PCI DSS sets no exemption based on size. Payment brands define merchant levels and who must validate, so a small merchant should ask its acquirer what applies. Full answer: Myths →
Does PCI SSC fine merchants for non-compliance?
PCI SSC maintains the standards and does not run the enforcement programs. The QSA Program Guide says the payment brands establish penalties and fees and manage compliance enforcement. Full answer: Myths →
Does encrypting card data remove it from PCI DSS scope?
Generally not. PCI DSS says encryption alone is generally insufficient to render cardholder data out of scope. A third-party service provider with no ability to decrypt the data is a narrow exception, subject to conditions. Full answer: Myths →
Red flags
What should we do if we find card numbers outside our CDE?
Follow the procedures Requirement 12.10.7 calls for, which cover retrieval, secure deletion, or migration into the defined CDE. Then find out how the data got there and whether your scope needs to change. Full answer: Red flags →
Does a flat network put everything in PCI DSS scope?
PCI SSC scoping guidance says that without adequate segmentation, the entire network is in scope. Segmentation is not a PCI DSS requirement, but PCI DSS strongly recommends it as a way to reduce scope. Full answer: Red flags →
How often should we confirm our PCI DSS scope?
Requirement 12.5.2 calls for at least once every 12 months and upon significant change. Service providers confirm scope at least once every six months under Requirement 12.5.2.1. Full answer: Red flags →
Official guidance
Do PCI SSC information supplements add new PCI DSS requirements?
No. Each supplement states that it provides supplemental information and does not replace or supersede requirements in any PCI SSC standard. Full answer: Official guidance →
Where are the official definitions of PCI DSS terms?
PCI SSC publishes them in Appendix G of PCI DSS v4.0.1. Compensating controls and the customized approach are defined further in the standard’s other appendices and in Section 8. Full answer: Official guidance →
Which PCI SSC document explains how to define PCI DSS scope?
Start with Section 4 of PCI DSS v4.0.1 and Requirement 12.5.2. The information supplement on scoping and network segmentation then explains the system categories and gives worked examples. Full answer: Official guidance →
Is the official ROC Template mandatory for a Report on Compliance?
Yes. Section 11 of PCI DSS v4.0.1 says the ROC Template must be used to create a PCI DSS Report on Compliance. Full answer: Official guidance →
Assessment findings
Can a partly implemented control be reported as In Place?
No. The ROC Template uses Not in Place when some or all elements of a requirement have not been met or are still being implemented. The assessor reassesses after remediation. Full answer: Assessment findings →
Does a first PCI DSS assessment need four passing ASV scans?
Not necessarily. Requirement 11.3.2 allows fewer if the assessor verifies that the most recent scan passed, policies require scanning at least once every three months, and rescans show that noted vulnerabilities were corrected. Later years need passing scans at least every three months. Full answer: Assessment findings →
Can a targeted risk analysis justify running a control less often than PCI DSS states?
No. PCI SSC’s TRA guidance says that a stated frequency is the minimum. Performing the activity less often means the requirement as stated is not met. The alternative the guidance gives is a customized control under the customized approach. Full answer: Assessment findings →
What does an assessor review for payment page scripts under Requirement 6.4.3?
The testing procedures call for policies and procedures, interviews with responsible personnel, inventory records, and system configurations. Together they show how each script is authorized, how its integrity is assured, and why it is necessary. Full answer: Assessment findings →
Tools
Is there software that removes all PCI DSS requirements?
No. PCI SSC’s scoping guidance says no solution or technology eliminates all PCI DSS requirements. Tools such as encryption or tokenization may reduce risk or reduce how many requirements apply. Full answer: Tools →
Is antivirus still required under PCI DSS?
PCI DSS uses the term anti-malware. Requirement 5.2.1 calls for a solution on all system components, except those that periodic evaluations under Requirement 5.2.3 conclude are not at risk from malware. Full answer: Tools →
Can internal staff run PCI DSS vulnerability scans?
Qualified, reasonably independent internal staff can run internal scans under Requirement 11.3.1. External scans under Requirement 11.3.2 must be performed by a PCI SSC Approved Scanning Vendor. Full answer: Tools →
Is file integrity monitoring required by PCI DSS?
Requirement 11.5.2 requires a change-detection mechanism and gives file integrity monitoring tools as an example. It must alert personnel to unauthorized changes and compare critical files at least once weekly. Full answer: Tools →
Do security tools themselves fall within PCI DSS scope?
They can. Section 4 of PCI DSS v4.0.1 lists systems that provide security services, including SIEM, multi-factor authentication, and anti-malware systems, as examples of in-scope system components. Full answer: Tools →
Standard updates
Are the requirements that were best practices until 31 March 2025 still optional?
No. The standard says each one became required after that date and must be fully considered during a PCI DSS assessment. Full answer: Standard updates →
What did the January 2025 SAQ A revision remove?
SAQ A Revision 1 removed Requirements 6.4.3, 11.6.1, and 12.3.1. It added an eligibility criterion for e-commerce merchants to confirm that their site is not susceptible to attacks from scripts that could affect their e-commerce systems. Full answer: Standard updates →
What happened to the In Place with Remediation reporting option?
PCI SSC removed it in December 2022. The change appears in the SAQ and ROC Template change tables. Full answer: Standard updates →
Who decides whether an older PCI DSS version can still be used?
Section 14 of PCI DSS v4.0.1 directs questions about previous versions to the organizations that manage compliance programs, such as payment brands and acquirers. Full answer: Standard updates →
By business type
Is PCI compliance mandatory for e-commerce merchants?
PCI DSS applies to merchants that accept payment cards bearing participating brand logos. Whether a specific entity must comply or validate is set by payment brands and acquirers, so confirm your obligations with your acquirer. Full answer: By business type →
What is the difference between SAQ A and SAQ A-EP?
SAQ A fits merchants that completely outsource account data functions, with every payment page element coming directly from a compliant provider. SAQ A-EP fits e-commerce merchants whose websites do not receive account data but do affect transaction security. Full answer: By business type →
Do Requirements 6.4.3 and 11.6.1 apply if we use an iframe?
They apply to scripts on your page that includes the provider’s iframe. The provider manages scripts inside its iframe, and your SAQ type affects how you report this. Full answer: By business type →
Can a service provider complete an SAQ?
Only if a payment brand defines it as eligible. SAQ D for Service Providers is the only SAQ option for service providers. Full answer: By business type →
Work with RSI Security
RSI Security is a PCI Qualified Security Assessor (QSA) company and an Approved Scanning Vendor (ASV). It performs PCI DSS assessments and quarterly ASV scans. Organizations that need help with scoping or readiness can work with RSI Security through a separate advisory engagement. RSI Security provides either advisory or assessment to a given client, never both.
Schedule a PCI DSS assessment · Talk to an advisor about readiness
Sources
- PCI DSS v4.0.1 (Requirements and Testing Procedures; each answer’s originating page lists its specific sections)
