PCI Watch

Tracking changes across the Payment Card Industry
FAQs » FAQ #1331 » Versions » Diff

FAQ #1331 Diff

Can SAQ eligibility criteria be used for determining applicability of PCI DSS requirements for onsite assessments?

Earlier Version
Later Version
Removed
Added
Service providers cannotSAQs are compliance reporting tools developed by PCI SSC that are intended to help merchants document compliance with PCI DSS requirements under appropriate conditions, for designated use SAQ eligibility criteriacases, and are subject to determineany applicable rules and requirements of the organizations responsible for managing compliance programs (e.g., payment brands and acquirers).

 SAQs should not be used as a “guide” for determining the applicability of PCI DSS requirements for assessments documentedunless explicitly reviewed, discussed and agreed upon with the merchant’s compliance accepting entity (e.g., payment brands and acquirers). For the avoidance of doubt, merchants should always consult with the organizations responsible for managing compliance programs to confirm their PCI DSS validation and reporting requirements.

For further information please refer to FAQ #1473: What is the role of compliance-accepting entities and assessors in a Report on Compliance (ROC). The only acceptable SAQ fordetermining the applicability of PCI DSS requirements for merchant and service providers is SAQ D for Service Providers. All other SAQs are intended for merchant use only.provider PCI DSS assessments?

Merchants should work with their QSA to fully understand the merchant’s environment. If they are able to reach agreement that applying only the requirements includedContact information for the payment brands can be found in an SAQ is an acceptable approach to secure that merchant’s environment, then that SAQ may be used as a relevant guide for applicability of PCI DSS requirements for that environment. If an environment meets some but not all eligibility criteria for a particular SAQ, then the SAQ should not be considered a relevant guide for applicability of requirements. This approach must be clearly documented by the QSA in "Description of Scope of Work and Approach Taken" section 3.1 of the (ROC).

The assessor will need to perform appropriate testing and validation to verify the non-applicability of any PCI DSS requirements. As an example: If an e-commerce merchant has a webserver using a server-side redirect (for example, HTTP response with a status code 301 or 302) to a PCI DSS compliant third-partyFAQ #1142: How do I contact the payment processor, the assessor could consider requirement 6.4.3 and 11.6.1 as not applicable since the redirection mechanism is not susceptible to script-based attacks.

This approach must be clearly documented by the QSA in "Description of Scope of Work and Approach Taken" section 3.1 of the ROC. Any PCI DSS requirements verified by the assessor to be not applicable should be reported as "Not Applicable" in accordance with instructions in the ROC Template. Assessors should refer to the ROC Template and ROC Template FAQs for the version of the standard being used for relevant guidance.

In all cases, the merchant is still expected to include PCI DSS Requirement 12.5.2 to document and confirm their PCI DSS scope at least once every 12 months. The merchant’s assessor is expected to include an assessment of Requirement 12.5.2 and document results in the merchant’s ROC. See PCI DSS v4.x “Annual PCI DSS Scope Confirmation” for more details.

Merchants should always consult with the organizations that manage compliance programs (for example, payment brands and acquirers) to confirm their PCI DSS validation and reporting method. If a detailed assessment and ROC is the appropriate method, merchants meeting the eligibility criteria from an SAQ should also confirm that the approach outlined above is acceptable. Contact information for the payment brands can be found in FAQ #1142 How do I contact the payment card brands?

Disclaimer: This FAQ has been processed for display on this website and may contain errors. Please check the original FAQ on the PCI SSC website for the authoritative version.