GuestView Columnist David Taylor is the Founder of the PCI Knowledge Base, Research Director of the PCI Alliance and a former E-Commerce and Security analyst with Gartner.
Based on the PCI Standards Committee’s official "hint" about what will be in the 1.2 release, it appears that clarifying when and how virtualized servers can be PCI compliant didn’t make the cut. But before the server and security geeks start lighting their torches and getting all "vigilante" on the card brands, let me tell you why I don’t think this will matter.
Virtualization saves money. As a technology, virtualization—particularly server virtualization—is saving retailers money on hardware and IT management. In a down economy, cost reduction trumps compliance. Where virtualized servers and PCI compliance come to blows is PCI DSS 2.2.1, which says only one primary function per server. Because some merchants, assessors and acquirers think "physical server" when they read this standard, some merchants have limited the deployment of server virtualization to the dev/test environment.
Other merchants are making sure not to deploy server virtualization in the cardholder environment. Still others are deploying virtualized servers for applications with credit card, SSN and other confidential data, but they are careful not to put applications with different "trust levels" for different levels of access controls on the same physical server. The point is that if you want to use virtualization to reduce your IT costs, you just need to be careful about what applications you put on what types of servers.
Proof that virtualization is secure. We recently did a Webinar on the topic of how to prove that virtualized servers are secure enough to pass PCI assessments. Based on interviews with more than a dozen PCI assessors for the PCI Knowledge Base, it’s clear that in more than 75 percent of …