- 15 Non-Certified IT Skills Growing in Demand
- How 19 Tech Titans Target Healthcare
- Twitter Suffering From Growing Pains (and Facebook Comparisons)
- Agile Comes to Data Integration
Network World - The Payment Card Industry Security Standards Council, the organization that sets technical requirements for processing credit- and debit-cards, last week issued revised security rules. The council also indicated that next year it will focus on new guidelines for end-to-end encryption, payment machines and virtualization.
Adherence to PCI rules could play a key role in preventing big data thefts, like the 2005 TJX breach, security experts say.
The PCI 1.2 data security standard (DSS) seeks to clarify several pieces of the earlier 12-part PCI 1.1 standard that had many confused. Among other things, Version 1.2 clarifies that all operating systems associated with card processing have to run antivirus software, while many had thought this was only about Microsoft Windows.
"That sounds like a sensible piece of advice," says Sushila Nair, product manger at BT, who says organizations often deploy antivirus on Windows but erroneously believe Unix and Macs and other operating systems are somehow more invulnerable. However, she notes accommodating the clarified PCI rule on antivirus in many places will be "expensive."
One of the biggest topics of debate at last month's PCI Council meeting was how to determine what "network segmentation" means since the standard is aimed at trying to devise technical methods to cordon off where credit cards are stored so that PCI compliance assessment can be focused on specific parts of a merchant's network involved with cardholder data.
"There was a lot of talk about network segmentation," says Sumedh Thakar, PCI solutions manager at vulnerability management and policy compliance product company Qualys. "A lot of merchants were trying to get answers. The guidelines now are to restrict access using firewalls."
The PCI 1.2 standard advises the use of "internal firewalls, routers with strong access control" and other network-restricting technologies to assure internal network segmentation for card-processing purposes.
Some IT managers say the PCI-based reviews that their organizations are now undergoing are already based on PCI 1.2 as the baseline. Such reviews are typically carried out by PCI Council-certified assessors if self-assessment procedures aren't applicable.
"It was in draft form so we decided to use that since there seemed to be no point in using 1.1 anymore," says one IT manager, who preferred not to be named. But he says his organization is finding it very difficult to isolate the network to protect specific servers and applications associated with cardholder data, plus monitor and log according to the PCI 1.2 guidelines.
"There's no way we can log all the stuff they want," he said, adding his organization has no choice but to keep plowing on with the assessors to make it through the PCI audit.
The PCI update is also ushering in revised products to support it.
Qualys, for example, last week introduced a Web-application scanning service targeted at satisfying the new requirement that Part 6.6 of PCI 1.2 brings for conducting vulnerability tests of public-facing Web applications "at least annually or after any changes." An alternate technology allowed in PCI 1.2 in the 6.6 rule would be installing a Web application firewall.