Frequently Asked Question
Are call center environments considered "sensitive areas" for PCI DSS Requirement 9.1.1?
PCI DSS Requirement 9.1.1 addresses the need for video cameras and/or access control mechanisms to monitor individual physical access to sensitive areas. "Sensitive areas" refers to any data center, server room or any area that houses systems that store, process, or transmit cardholder data. Note that this excludes the areas where only point-of-sale terminals are present, such as the cashier areas in a retail store. This exclusion was included to recognize that such controls may not be practical or permitted in public-facing areas where cardholders are using their own payment cards.
Because call-center environments contain systems that process, transmit and/or store cardholder data, such areas need to be protected from unauthorized physical access. Without physical access controls, unauthorized persons could potentially gain access to the CDE and to sensitive information, or could alter system configurations, introduce vulnerabilities into the network, or destroy or steal equipment. The purpose of Requirement 9.1.1 is to ensure that all entry/exit points to sensitive areas are controlled and monitored, and that all individuals who physically access the area are identified. Whichever mechanism is used to meet this requirement, it must be sufficient for the organization to verify that only authorized personnel are granted access.
Related
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
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?
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 for determining applicability of PCI DSS requirements for assessments documented in a Report on Compliance?
Most Popular
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
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?
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
Most Recently Updated
-
Are Mobile Payments on COTS (MPoC) solutions, Software-based PIN Entry on COTS (SPoC)™ solutions, or Contactless Payments on COTS (CPoC™) solutions eligible for a P2PE Solution approval?
-
How can an entity meet PCI DSS requirements for PAN masking and truncation if it has migrated to 8-digit BINs?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
-
How does encrypted cardholder data impact PCI DSS scope for third-party service providers?
-
Does PCI SSC provide a list of PCI DSS-compliant third-party service providers?