David Heath
Monday, 14 November 2011 15:32
Page 1 of 2
Sometimes it seems as though we finally achieve PCI compliance only to have 'management' change the landscape and throw the 'cloud' curveball at us. Will PCI and clouds mix or are they oil and water?
For a credit card processing organization, it's (relatively) easy to achieve PCI compliance when they own pretty-well all of the computers and plumbing right up to the secure connection to the payment gateway.
"Great, we can rest a little easy until the next audit," says the CSO.
Next thing he hears is that the Board and the CIO have decided to make his sunny day exceedingly cloudy.
"We're going to outsource our back-end systems to a cloud provider; we're looking to see who's cheapest."
According to leading Australian specialist security information consultancy Pure Hacking, The challenges of transparency and independent verification of compliance standards are two major issues which organisations need to address prior to moving credit card storage and transaction facilities to a public cloud. They suggest that while the costs of daily operations might well be best reduced by sending them into the cloud, there is little but heartache for any plan to do similar for card processing.
"Solely relying on public cloud computing systems for processing credit card information and transactions is literally a game of probability and risk. In the end the likelihood of an attack against a public cloud that holds such high value information is extremely probable. The security posture of your public cloud vendor against such attacks is key to your ability to protect your client's data privacy and business functionality," said Ty Miller, CTO, Pure Hacking.
See the
next page for some suggestions on considering whether or not to mix your PCI with the cloud.