ISC · Security and Confidentiality and Privacy · 6 practice questions
PCI DSS Scope: Card Data, Hosted Checkout, and Admin Systems
PCI DSS scope includes systems that handle cardholder data and systems that can affect its security. Below: sort a retailer's payment systems, admin workstations, and isolated corporate systems by what they actually do.
Try one first
Hint
Focus on what activity brings an organization into scope, not on whether it keeps the data or how large the organization is.
Answer A. PCI DSS applies to any entity that stores, processes, or transmits cardholder data (or sensitive authentication data). The retailer entered PCI DSS scope when it began transmitting card data through its POS in Year 1, even though it does not retain the card numbers after authorization. Transaction volume affects how compliance is validated (for example, which assessment or SAQ is required), but does not change when PCI DSS is applicable.
Why not B: This is tempting because many candidates associate PCI DSS primarily with stored card data. However, transmitting or processing cardholder data also brings an entity into scope, so scope begins when the retailer transmits card data through its POS.
Why not C: This distractor confuses applicability with validation. Transaction volume can affect the required validation method (e.g., SAQ vs. external QSA assessment), but it does not delay the point at which PCI DSS applies.
Why not D: Banks and processors are subject to PCI DSS, but so are merchants that store, process, or transmit cardholder data. Being a merchant does not exempt the retailer from PCI DSS.
Sort it
The system itself stores, processes, or transmits cardholder data.
The system does not handle cardholder data but connects to the CDE or can affect its security.
The system handles no cardholder data, and validated segmentation shows it cannot connect to or affect the CDE.
| Item | Goes to |
|---|---|
| North's payment terminal transmits card numbers to its processor and retains none after authorization. | Card-data systemsTransmitting cardholder data brings the terminal into scope. Keeping no card numbers does not change that result. |
| North's payroll server handles no card data. Validated segmentation prevents it from connecting to or affecting the payment environment. | Systems eligible for exclusionThe exclusion rests on verified isolation, not merely the server's payroll function. |
| North's corporate workstation remotely administers payment terminals but never receives card numbers. | Connected or security-impacting systemsAdministrative access can affect terminal security. The workstation does not need to receive cardholder data to be in scope. |
| North's checkout server forwards card numbers to the processor through a server-to-server submission. | Card-data systemsThe card numbers pass through North's server. Outsourcing authorization does not remove that server from scope. |
| North's web server controls code loading an embedded payment widget. Compromise could alter checkout, although the server receives no card numbers. | Connected or security-impacting systemsControl over the payment experience can affect cardholder data security without direct receipt of card numbers. |
| North's chargeback database retains full primary account numbers, or PANs. | Card-data systemsStoring full PANs places the database in the CDE. The business reason for keeping them does not remove scope. |
| North's inventory server handles no card data. Tested segmentation prevents access to or influence over the payment environment. | Systems eligible for exclusionIts verified separation supports exclusion. Accepting cards does not automatically put every corporate system in scope. |
| North's support workstation has unrestricted network access to the CDE but does not handle cardholder data. | Connected or security-impacting systemsConnectivity to the CDE brings the workstation into scope even without card-data handling. |
| North's processor operates a separate hosted card-entry page. North's systems never receive the card data entered there. | Card-data systemsThe provider's page processes card data. Hosting it externally can reduce North's scope, but North retains provider-oversight responsibilities. |
| North's payment gateway transmits PANs and is covered by North's NIST Cybersecurity Framework program. | Card-data systemsTransmission determines scope. NIST CSF alignment does not replace the gateway's applicable PCI DSS requirements. |
| North's terminal-management server handles no card data and is covered by a clean SOC 2 Type 2 report. | Connected or security-impacting systemsManaging terminals can affect the CDE. A SOC 2 report does not remove the server from PCI DSS scope. |
| North's redirect website receives no card data, but its configuration can send customers to an attacker-controlled payment page. | Connected or security-impacting systemsThe redirect can affect payment security. Hosted card entry does not justify ignoring merchant-controlled integration components. |
Key points
- Remember: No card data on a system does not mean no PCI scope if that system can affect payment security.
- The cardholder data environment, or CDE, includes systems that store, process, or transmit cardholder data.
- A processor's hosted page can reduce merchant scope without eliminating merchant responsibilities.
- SOC 2 reports and NIST CSF alignment do not replace PCI DSS scoping.
How the exam traps you
- Exclude a system because it deletes card numbers after authorization. Processing or transmitting cardholder data is enough; storage is not required.
- Exclude admin workstations because the processor handles payments. Include workstations that can administer or otherwise affect the payment environment.
- Treat a SOC 2 report or NIST CSF alignment as a PCI DSS substitute. Determine PCI DSS scope separately; those measures do not remove payment-card obligations.
Question 2
Hint
Ask which option is specifically targeted to organizations that handle payment card data, rather than a broad governance framework or an unrelated regulation.
Answer A. PCI DSS is the industry standard created specifically for organizations that store, process, or transmit payment cardholder data, and it defines detailed technical and operational security requirements for that environment. Broader governance frameworks or unrelated regulations do not provide the same cardholder-data-specific controls that PCI DSS requires.
Why not B: HIPAA establishes security and privacy rules for protected health information and applies to covered entities and business associates, not to general retail payment card environments.
Why not C: COBIT is an IT governance and management framework that helps with enterprise control objectives, so it may seem relevant, but it does not contain the specific technical and operational requirements targeted at protecting cardholder data.
Why not D: NIST CSF is a voluntary, broad cybersecurity risk-management framework useful for organizing programs, but it is not the payment-card-specific standard that prescribes controls for cardholder data environments.
Question 3
Hint
Separate the factor that makes a standard applicable from factors that only affect how compliance is carried out.
Answer D. PCI DSS applicability is driven by whether an entity stores, processes, or transmits payment card account data as part of its operations. Here, Blue Finch's checkout page collects card data and transmits it to the processor, so the standard is relevant even though a third party handles authorization and settlement. Transaction volume may affect validation requirements, but it does not determine basic applicability.
Why not A: This is tempting because candidates often associate compliance obligations with public-company status. However, PCI DSS applies to any entity that handles cardholder data regardless of whether it is publicly traded.
Why not B: Outsourcing can affect scope and responsibilities, but if Blue Finch's website collects and transmits cardholder data, that activity brings cardholder data into scope even when a third party processes transactions.
Why not C: Transaction volume is used to assign merchant levels and to determine validation requirements, but it does not determine whether PCI DSS applies at all; handling card data does.
Question 4
Hint
Focus on the difference between reducing PCI DSS scope and eliminating it entirely when payment processing is outsourced.
Answer C. A processor-hosted checkout on the processor's domain generally removes cardholder data from the merchant's systems and therefore narrows the merchant's PCI DSS scope. However, the merchant still retains responsibilities such as selecting and overseeing the service provider, ensuring contractual and evidence-of-compliance controls, and addressing any remaining integration or website controls that could affect cardholder data. Reduced scope is not the same as zero PCI responsibility.
Why not A: Tempting because the merchant no longer directly handles cardholder data. Incorrect because even when card entry is outsourced, the merchant still has compliance-related responsibilities (service-provider oversight, contractual requirements, and possible residual technical controls) that keep PCI DSS relevant.
Why not B: Tempting because contracts allocate duties between parties. Incorrect because contractual allocation alone does not relieve the merchant of PCI-related obligations; the merchant must still validate and oversee the provider and may retain responsibilities tied to its own systems or integrations.
Why not D: Tempting because merchants are still part of the payment flow and cannot ignore security. Incorrect because a processor-hosted, separate-domain checkout can materially reduce the merchant's PCI scope, so claiming the scope is essentially unchanged overstates the merchant's ongoing footprint.
Question 5
Hint
Ask whether NorthPeak's own systems ever 'touch' cardholder data and remember that NIST CSF is a broad framework, not a card‑specific compliance standard.
Answer D. PCI DSS applies to entities that store, process, or transmit cardholder data. Because NorthPeak's web servers transmit cardholder data (server-to-server), its systems are within the cardholder data environment and subject to applicable PCI DSS requirements. NIST CSF is a useful governance framework but does not replace payment-card-specific technical and operational obligations under PCI DSS.
Why not A: This is tempting because outsourcing can reduce merchant scope and many responsibilities fall to processors. It fails because merchant systems that transmit, process, or store cardholder data remain in PCI DSS scope; outsourcing does not automatically eliminate the merchant's obligations and typically requires merchants to validate the processor's compliance and maintain certain controls.
Why not B: This is tempting because NIST CSF is broad and maps to many security controls, so one might think it covers PCI objectives. It fails because PCI DSS is a card‑specific standard triggered by storing, processing, or transmitting cardholder data; following NIST CSF does not, by itself, satisfy PCI DSS compliance requirements.
Why not C: This distractor tempts by linking NorthPeak's healthcare-related business to HIPAA. It fails because HIPAA governs PHI for covered entities/business associates; the stem states the checkout system does not handle PHI, and HIPAA does not replace PCI DSS for protection of cardholder data.
Question 6
Hint
Don't stop at where cardholder data is stored; consider whether any merchant-controlled system can connect to, administer, or otherwise affect the cardholder data environment and whether segmentation has been validated.
Answer C. Outsourcing authorization and not retaining cardholder data can reduce PCI DSS scope, but merchant-controlled systems that can connect to, administer, or otherwise affect the cardholder data environment (CDE) remain in scope. The two corporate workstations are authorized to administer the terminals and therefore can impact the security of the terminals/CDE, so they remain in scope. Systems that are truly segmented and where segmentation has been validated through appropriate testing (for example, by a QSA or other qualified assessor) may be excluded from scope.
Why not A: Tempting because candidates may over-rely on a service provider's assessment, but a processor's validated compliance does not automatically extend to merchant-controlled systems that can affect the CDE; the merchant remains responsible for identifying its own in-scope systems.
Why not B: This distractor appeals to the shortcut that accepting cards makes the entire enterprise in scope, but PCI DSS permits scope reduction when effective segmentation has been validated; the stem states validated segmentation prevents unrelated systems from connecting to or affecting the payment environment, so blanket enterprise-wide scope is not supported.
Why not D: Tempting because encrypted direct transmission and no retention reduce scope, but merchant systems that can administer or otherwise impact the terminals/CDE remain in scope despite those factors.
Common questions
Does PCI DSS apply if card numbers are never stored?
Yes. North's payment terminals and forwarding server are in scope because they process or transmit cardholder data, even without retaining it.
Does a hosted payment page eliminate PCI DSS scope?
No. A processor-hosted page can remove card data from merchant systems and reduce scope. North still has provider-oversight responsibilities and must evaluate systems that can affect payment security.
Are corporate admin workstations in PCI DSS scope?
Yes, if they administer or can affect the payment environment. Unrelated corporate systems may be excluded when validated segmentation demonstrates they cannot connect to or affect that environment.
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Regulations and standards and frameworks
- PCI DSS vs. NIST CSF vs. ISO 27001 vs. COBIT
- Do NIST CSF and ISO 27001 Satisfy HIPAA or PCI DSS?
- SOC 2 vs ISO 27001 vs PCI DSS vs NIST CSF
- ISO 27001 vs NIST CSF vs SOC 2: Which Should You Choose?
- When Is the NIST Cybersecurity Framework the Right Choice?
- SEC Cybersecurity Disclosure: The Four-Business-Day Clock
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.