Sycurio Glossary.

De-scoping PCI DSS

Descoping PCI DSS involves implementing measures to minimize the contact center's exposure to sensitive cardholder data and reducing the systems, networks, and processes that fall within the scope of PCI DSS compliance. By descoping, organizations can simplify their compliance efforts, reduce associated costs, and mitigate the risks associated with handling and storing sensitive payment card information.

Here are some common strategies used to descop PCI DSS in contact center payment operations:
1. Outsourcing Payment Processing: By outsourcing payment processing to a PCI DSS-compliant third-party service provider, the contact center can transfer the responsibility of handling and storing cardholder data. This can greatly reduce the scope of PCI DSS compliance within the contact center environment.

2. Tokenization: Implementing tokenization involves replacing sensitive cardholder data (such as credit card numbers) with unique tokens. The actual payment card data is securely stored in a tokenization system, which can be located outside the contact center environment. This way, the contact center only handles tokens, significantly reducing the scope of PCI DSS compliance.

3. Point-to-Point Encryption (P2PE): P2PE solutions encrypt sensitive cardholder data at the point of interaction (such as the payment terminal) and keep it encrypted until it reaches the payment processor. With P2PE, the contact center does not have access to the decrypted cardholder data, reducing its exposure and simplifying PCI DSS compliance.

4. Interactive Voice Response (IVR) Payments: Implementing an IVR system for payment transactions allows customers to enter their payment card information directly through a secure, automated system. The contact center agents do not handle or have access to the sensitive cardholder data, significantly reducing the scope of PCI DSS requirements.

5. Segmentation and Network Isolation: By segregating and isolating systems and networks that handle payment card data from the rest of the contact center infrastructure, the scope of PCI DSS compliance can be limited to a specific area. This reduces the potential for cardholder data exposure and simplifies compliance efforts.

It is important to note that descoping PCI DSS does not mean bypassing security or neglecting the protection of sensitive data. It involves implementing alternative methods and technologies to minimize the contact center's exposure to cardholder data and maintain compliance with the required security standards. Organizations should carefully assess and validate their descoping strategies to ensure they meet the necessary security requirements and are accepted by the relevant card brands and payment processors.

Back to Glossary