Frequently Asked Question

Can merchants using non-console administrative access be eligible for SAQ B-IP, C-VT, or C?
Yes, as long as all SAQ eligibility criteria are met. For example, SAQ B-IP, SAQ C and SAQ C-VT are each intended for environments using only permitted system types, as defined in the eligibility criteria for each SAQ. A brief description for each SAQ is provided below:
- SAQ B-IP: Environments using only PTS-approved point-of-interaction (POI) devices (excludes SCRs). This is the only permitted system type for this SAQ.
- SAQ C-VT: Environments using only web-based virtual payment terminals on a personal computer connected to the Internet. This is the only permitted system type for this SAQ.
- SAQ C: Environments using only payment application systems (for example, point-of-sale systems) connected to the Internet. This is the only permitted system type for this SAQ.
The SAQ criteria is not intended to prohibit more than one of the permitted system types being on the same network zone, as long as the permitted systems are isolated from other types of systems (e.g. by implementing network segmentation). In these types of environments, a merchant may wish to administer a defined system/device from the same type of system/device located within the same network. This would be considered non-console administrative access, and, in this scenario, the PCI DSS requirements for protecting non-console administrative access would apply.
Merchants that do not support non-console administrative access should select "N/A" for the affected requirements and complete Appendix C, as directed in the Before You Begin section of the applicable SAQ.
If any type of system other than that defined by the SAQ criteria is used to administer a SAQ-defined system, the environment would not be eligible for that SAQ. As an example, use of a back-office server to administer a PTS-approved POI device does not meet the eligibility criteria of SAQ B-IP.
Related
-
What are the expectations for entities when assigning risk rankings to vulnerabilities and resolving or addressing those vulnerabilities?
-
Is phishing-resistant authentication alone acceptable as multi-factor authentication for PCI DSS Requirements 8.4.1 and 8.4.3?
-
Are passkeys synced across devices, implemented according to the FIDO2 requirements, acceptable for use as phishing-resistant authentication to meet PCI DSS Requirement 8.4.2?
Featured FAQ Articles
Featured
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Is the PCI DSS Attestation of Compliance intended to be shared?
-
How does an entity report the results of a PCI DSS assessment for new requirements that are noted in PCI DSS as best practices until a future date?
-
Where do I direct questions about complying with PCI standards?
-
Can SAQ eligibility criteria be used as a guide for determining applicability of PCI DSS requirements for merchant assessments documented in a Report on Compliance?
Most Popular
-
What are the expectations for entities when assigning risk rankings to vulnerabilities and resolving or addressing those vulnerabilities?
-
Is phishing-resistant authentication alone acceptable as multi-factor authentication for PCI DSS Requirements 8.4.1 and 8.4.3?
-
Are passkeys synced across devices, implemented according to the FIDO2 requirements, acceptable for use as phishing-resistant authentication to meet PCI DSS Requirement 8.4.2?
-
How should PCI DSS v4.x requirements noted as superseded by another requirement be reported after 31 March 2025?
-
Are providers of third-party scripts for e-commerce environments considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
Most Recently Updated
-
What are the expectations for entities when assigning risk rankings to vulnerabilities and resolving or addressing those vulnerabilities?
-
Can SAQ eligibility criteria be used as a guide for determining applicability of PCI DSS requirements for merchant assessments documented in a Report on Compliance?
-
Is phishing-resistant authentication alone acceptable as multi-factor authentication for PCI DSS Requirements 8.4.1 and 8.4.3?
-
Are passkeys synced across devices, implemented according to the FIDO2 requirements, acceptable for use as phishing-resistant authentication to meet PCI DSS Requirement 8.4.2?
-
How should PCI DSS v4.x requirements noted as superseded by another requirement be reported after 31 March 2025?