LiquidShop is PCI DSS compliant
LiquidShop has been tested, and is part of an ongoing compliance check by McAfee Secure. McAfee's strict testing procedure ensure that LiquidShop remains PCI compliant and helps form part of your PCI DSS compliance.
LiquidShop is also hosted within secure data centres in London's Docklands. Only customer contact details are captured within the servers - all credit card information is handled in its entirety by our preferred payment providers, such as Sage Pay, who themselves are required to be PCI DSS compliant to a very high level. Learn more about Sage Pay PCI Compliance
There are many areas of your business that must be compliant, and LiquidShop is just one of them. Your other retail channels, your internal network and other systems which deal with credit card and personal data should also be compliant. Learn more about PCI DSS Compliance
PCI Compliance
The Payment Card Industry Data Security Standard (PCI DSS) is a worldwide information security standard, defined by the PCI Security Standards Council. It was created to prevent credit card fraud through increased data controls and reduced exposure to compromise. It applies to organisations which hold, process, or exchange credit card information. Learn more at the PCI Security Standards Council website.
12 Requirements for Compliance
The current version of the standard (1.2) specifies 12 requirements for compliance, organised into six logically related groups called Control Objectives.
Build and Maintain a Secure Network
1. Install and maintain a firewall configuration to protect cardholder data
2. Do not use vendor-supplied defaults for system passwords and other security parameters
Protect Cardholder Data
3. Protect stored cardholder data
4. Encrypt transmission of cardholder data across open, public networks
Maintain a Vulnerability Management Program
5. Use and regularly update anti-virus software on all systems commonly affected by malware
6. Develop and maintain secure systems and applications
Implement Strong Access Control Measures
7. Restrict access to cardholder data by business need-to-know
8. Assign a unique ID to each person with computer access
9. Restrict physical access to cardholder data
Regularly Monitor and Test Networks
10. Track and monitor all access to network resources and cardholder data
11. Regularly test security systems and processes
Maintain an Information Security Policy
12. Maintain a policy that addresses information security.
