The Tangled Web of PCI Compliance, Are You Ready?

New e-commerce security requirements for payment processing are vague enough to leave everyone wondering what to do, as the June 30 deadline approaches. We offer compliance strategies for different budgets.
Fear and loathing will dominate when Best Practice 6.6 of the PCI Data Security Standard becomes a requirement June 30.

The regulation requires that merchants dealing with debit and credit cards tighten up their security by both conducting application code reviews and installing Web application firewalls.

It was put forth by the PCI Security Standards Council, which issues, maintains and enforces the PCI security standards that govern payment account data security to which all corporations that deal with payment cards must adhere.

However, while stating that "proper implementation of both options would provide the best multi-layered defense", the Council says, in essence, that some merchants won't be able to implement both. The solution: select the best option for their needs. This is leading to compliance problems.

"We're addressing the problem in two ways," said Bob Russo, general manager of the PCI Security Standards Council. "If you have custom application code, it needs to be reviewed for common vulnerabilities, either by yourself or by a company that does application code reviews by a standard like OWASP. The Open Web Application Security Project, OWASP, is a worldwide free and open community focused on improving the security of application software whose materials are available under an open source license.

For off-the-shelf software, "installing an application layer firewall in front of a Web facing app will work as well," Russo explained. "You need security in the application itself if you can do it but that's not necessarily the way you need to look at this; either way will suffice."

In essence, it's going to have to be a business decision. And which option merchants choose depends on how much money they have.

"Bigger merchants have more budget and can afford to do both; but when you get into Level 4 merchants, which Visa describes as "any merchant processing fewer than 20,000 Visa e-commerce transactions per year," margins tend to be thin. (By contrast, Level-1 merchants have more than 6 million transactions a year.) Level 4 merchants "don't have lots of staff," said Ryan Barnett, director of application security at Breach Security and an instructor at the training-focused SANS Institute. "They're forced to choose between the two options."

(Continue to Page 2 for How Costs Affect Compliance)


Comment and Contribute
* Required Field
Your email address will not be published


Note: No advertising, no spam, no keyword in name/nickname field. Thank you!

Free Resources

  • eBook
    The Case for Endpoint Visibility A majority of organizations are operating under the assumption that their network has already been compromised, or will be, according to a survey...
  • eBook
    Dangerous File-Sharing The greatest threat to data security today is the carelessness of corporate employees. Today's workforce expects the ability to send and receive...

Subscribe To Our Daily Newsletter