Regulatory compliance 'irrelevant' to security
PCI DSS credit card 12 commandments standard flawed
Companies who get hung up on regulatory compliance are developing a false sense of security which leaves them just as open to malware attacks the chief exec of tools vendor Protegrity has warned.
The Payment Card Industry Data Security Standard (PCI DSS) was developed by the major credit card companies as a means to bolster the security posture of organisations that process card payments.
The 12 point guidelines framed by PCI DSS are a basic list of "thou shalt" (or shalt not) commandments for network security covering the need to run a firewall, maintain up to date anti-virus software, encrypt cardholder data, and the like. A revision of the standard (version 1.1) covering web application security is due to come into force in June.
Protegrity chief exec Gordon Rapkin said compliance with the standard should only be viewed as a useful first step towards becoming secure. However, too many ecommerce outfits view it as a test that needs to be passed - in order to avoid higher merchant fees or fines that come with non-compliance - before lessons learned by going through the process can be forgotten.
"The regulation itself gets firms to do something. But after passing the tests it can create a false sense of confidence," Rapkin explained.
Compliance with the standard involves self assessment for small ecommerce outfits stepping up to annual audits for the largest firms. Self assessment can encourage respondents to tick boxes without having any idea what they have answered while security auditing, a less mature process than financial auditing according to Rapkin, can also have its problems.
US grocery chain Hannaford warned last month of an information security breach that exposed an estimated 4.2 million credit card records. The Hannaford breach was later blamed on a sophisticated malware attack. The grocery chain had achieved PCI DSS compliance, but the process failed to unearth the flaws that led to the breach. "Just because you are PCI compliant doesn't mean you are secure," Rapkin noted.
Protegrity makes tools to encrypt data, safeguard web applications, and manage and report on security policy. One aspect of security policy involves achieving compliance with regulations such as PCI DSS.
Rapkin is a supporter of PCI DSS in general. He reckons that its prescriptive approach is better at improving security than US health sector regulations on maintaining patient data confidentiality (covered by the HIPA Act), for example.
However, he is critical of aspects of how the regulations work in practice, particularly the assessment process. "Assessment is not uniform. Some firms shop for assessors who they know are going to pass them. Meanwhile, some less scrupulous accessors use the assessment process as an opportunity to sell clients remediation technology to achieve compliance," Rapkin told El Reg.
In addition, more could be done to make the process more transparent. For all its faults PCI DSS is better than nothing, according to Rapkin.
"PCI DSS is prescriptive, which is a good approach as far as it goes. It raise the bar on security - and has probably reduced fraud but it doesn't go far enough," he concluded. ®
Sponsored: Customer Identity and Access Management