PCI's Bob Russo: Data loss hurts brand more than a fine
As Christmas shoppers spend away and data breaches keep hitting the headlines, the Payment Card Industry's security council is charged with keeping customer's data safe.
The Payment Card Industry Data Security Standard (PCI DSS) and the global forum formed to administer it, the PCI Security Standards Council (PCI SSC), pre-dated the biggest security breaches that have come to mark a new era of unprecedented cyber criminal activity.
Since card operators Visa, MasterCard, American Express, Discovery and JCB aligned their individual data security policies and created PCI DSS in 2004, the likes of TK Maxx, Cotton Traders and numerous government departments have proven the need for such regulation.
But the PCI DSS has risen up the corporate agenda ever since the threat of fines and losing the ability to process credit cards was introduced with a June 2007 deadline for those found to be non-compliant.
The standard is intended to create an additional level of protection for consumers by ensuring that merchants meet minimum levels of security when they store, process and transmit cardholder data. And the PCI council is charged with regulating PCI DSS and communicating its importance to any organisation handling credit card data anywhere in the world.
IT PRO spoke to PCI SSC general manager, Bob Russo about the challenges faced in raising the data security agenda.
IT PRO: 2007 was big year for PCI DSS, with the passing of the payment card operators' final deadline for compliance. What's been going on this year?
Russo: It's been just as busy. We released version 1.2 of the standard in October. Just prior to its release, we had our North America community meeting, which attracted 625 attendants and actually included quite a few representatives from Europe. There were a couple of days' good debate about the development of the standard, given that we're in a two-year cycle.
Next year will be a feedback year on how the implementation of version 1.2 has gone. And we also talked about our new QA [quality assessor] programme and got a lot of feedback on that, having kicked it off in October to maintain the quality of PCI assessments as well.
Then we had our first European meeting in Brussels with well over 200 people attending. I would say there is a lot more uptake in Europe on the standard. In fact, they are running, not walking, to comply. Reaction to the new version was good. It doesn't really contain any surprises, but instead includes a lot of clarifications, so organisations looking to stay up to date don't have to go back to square one to remain compliant.
It's interesting that you observe organisations are running' to be compliant. How do you propose they keep up if, as you say, the standard is on a two-year development cycle?
My guess is that the next release in 2010 will be a 2.0. But there are a couple of things we're doing to make sure it develops in line with the capabilities of our stakeholders. Starting in January, we're launching research into how the standard's specification should embody emerging technologies, like end-to-end encryption, virtualisation and secure payment tokens, that might come outside of its scope, making it easier to comply.
In This Article
Accelerating AI modernisation with data infrastructure
Generate business value from your AI initiativesFree Download
Recommendations for managing AI risks
Integrate your external AI tool findings into your broader security programsFree Download
Modernise your legacy databases in the cloud
An introduction to cloud databasesFree Download
Powering through to innovation
IT agility drive digital transformationFree Download