Frequently Asked Question
To which types of service providers does PCI DSS Appendix A1 for Multi-Tenant Service Providers apply?
All service providers are expected to meet PCI DSS requirements as applicable to the services offered to their customers. In addition, PCI DSS Appendix A1: Additional PCI DSS Requirements for Multi-Tenant Service Providers includes requirements specific to multi-tenant service providers, which is a type of third-party service provider (TPSP) that offers various shared services to merchants and other service providers.
Appendix A1 for Multi-Tenant Service Providers applies to service providers with customers in shared services environments, where customers manage their own environment or have administrative control over their own segment.
Multi-tenant service providers offer various shared services to merchants and other service providers, where customers share system resources (such as physical or virtual servers), infrastructure, applications (including Software as a Service (SaaS)), and/or databases. Services may include, but are not limited to, hosting multiple entities on a single shared server, providing e-commerce and/or “shopping cart” services, web-based hosting services, payment applications, various cloud applications and services, and payment gateway and processor services offered in a shared environment. *
It is not the intent that all or even most TPSPs are categorized as multi-tenant service providers. For example, the following are not considered multi-tenant service providers and are not subject to Appendix A1:
- TPSPs that offer a single, unified environment where customers access only their own data through a common platform, and the provider manages all access and infrastructure.
- TPSPs that offer only shared data center services (often called co-location or "co-lo" providers), where equipment, space, and bandwidth are available on a rental basis.
- TPSPs with servers that are dedicated to a single customer.
Note that all other applicable PCI DSS requirements do apply to the above TPSPs.
Whether a service provider is required to validate PCI DSS compliance is determined by the organizations that manage compliance programs (for example, an acquirer, payment brand, or other entity). Entities should always contact the entity that manages their compliance program directly to determine their compliance requirements. Contact details for the payment brands can be found in FAQ #1142: How do I contact the payment card brands?
* For additional information and applicable requirements for these TPSPs, refer to PCI DSS Appendix A1: Additional PCI DSS Requirements for Multi-Tenant Service Providers.
Related
-
Do ASV scans in SAQ A apply to merchants with webpages that redirect to TPSPs or include TPSPs’ embedded iframes?
-
Are authentication values from a 3DS transaction considered sensitive authentication data for PCI DSS purposes?
-
Should entities with enterprise or internal service providers, used to provide internal services to other corporate entities, conduct separate PCI DSS assessments of these service providers or include them as part of each corporate entity’s PCI DSS assessment?
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 acceptable formats for truncation of primary account numbers?
-
For PCI DSS, why is storage of sensitive authentication data (SAD) after authorization not permitted even when there are no primary account numbers (PANs) in an environment?
-
How does an e-commerce merchant meet the SAQ A eligibility criteria for scripts?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
-
Are truncated Primary Account Numbers (PAN) required to be protected in accordance with PCI DSS?
Most Recently Updated
-
Are authentication values from a 3DS transaction considered sensitive authentication data for PCI DSS purposes?
-
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?
-
Does PCI DSS define which versions of TLS must be used?
-
Do ASV scans in SAQ A apply to merchants with webpages that redirect to TPSPs or include TPSPs’ embedded iframes?
-
Is sampling allowed in PCI DSS v4.x?