PCI DSS Compliance Checklist for Contact Centres

PCI DSS Compliance Checklist for Contact Centres

PCiDSS-LogoIf your contact centre handles customer transactions and sensitive card data- the Payment Card Industry Data Security Standard (PCI DSS) is most likely something you’ve heard of.

As a formal set of requirements and standards, PCI DSS applies to all organisations which store, process or transmit sensitive data. The standards aims to ensure retailers, credit card brands and consumers are all protected from fraud and breaches.

Card Not Present Fraud

For contact centres taking Card Not Present (“CNP”) payments (transactions made via phone, internet or mail order purchases), PCI Compliance is crucial.

If your company is actively non-compliant, you’re at risk of suffering a data breach, monetary fines, as well as losing consumer trust. Ignoring the standard requirements could have a detrimental impact on your business, especially when CNP fraud is on the rise internationally. According to the Aite Group, CNP fraud in the U.S currently represents 45% of total U.S. card fraud, and in the UK the Financial Fraud Action UK reported an increase in fraud losses by 10%, totalling an estimated £331.5m in 2014.

So how does PCI DSS help?

The standards help to shape baseline requirements, that help companies like yours to create a series of information security networks. Being compliant will help you to identify where your cardholder data is coming from, who has access to it and how it will be stored.  Understanding how this sensitive data is transferred is fundamental in order to protect it.

The Checklist

Among the many risks, two of the key risk areas for data breaches, include staff access and phone/network hacking. The PCI standards are robust and comprehensive to enhance payment card data security – and consequently reduce the risks associated.

Here is a brief checklist of the requirements your organisation must meet to become PCI DSS compliant:

Build and Maintain a Secure Network and Systems

This should be implemented by installing and maintaining a firewall configuration that protects CHD. It is advised to not use vendor-supplied defaults for system passwords or associated devices used in payment processing.

Protect Cardholder Data

It is best not to store cardholder data. If your business requires you to do so then ensure it is thoroughly protected. Any CHD that is transmitted across open, public networks should be encrypted. 

Maintain a Vulnerability Management Programme

This should consist of installing anti-virus software and keeping all protection programs up to date.  Develop and maintain secure systems and applications such as using security patches. 

Implement Strong Access Control Measures

Restrict access to sensitive CHD on a strictly need-to-know basis.  Each user should be identified with a valid ID number when accessing system components. All personnel should be restricted physical access to CHD. 

Regularly Monitor and Test Networks

Track and monitor all access to network resources, systems and CHD.  Ensure that all security systems, functions and cardholder data environment are regularly tested. 

Maintain an Information Security Policy

Maintain a policy that addresses information security and make sure all personnel are aware of it and are kept up-to-date.

Beyond the compliance of systems and processes, there are many secure payment services available, to eliminate the risk of internal staff having unnecessary contact with sensitive card information. Popular solutions range from DTMF Payments, Pause and Resume, Tokenisation and many more. To find out more about these methods, and the popular choices that organisations are adopting to meet PCI DSS in their contact centres download our free eBook below.

eckon. pc.dss.ebook.image.jan.2016Additional Information

To download the Eckoh eBook ‘How to Secure Your Telephone Payments’ Click Here

For additional information about Eckoh visit their Website or view their Company Profile


Leave a Reply

Your email address will not be published. Required fields are marked *

error: Content Protected