Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

2/4/2009
02:29 PM
John H. Sawyer
John H. Sawyer
Commentary
50%
50%

PCI DSS Is A Process, Not A Checklist

Data breaches happen. We all know this simple fact. It's plastered on the news and the Internet. We hear about the big ones from co-workers, friends, and family. The recent Heartland Payment Systems breach, reported here on Dark Reading, is a testament.

Data breaches happen. We all know this simple fact. It's plastered on the news and the Internet. We hear about the big ones from co-workers, friends, and family. The recent Heartland Payment Systems breach, reported here on Dark Reading, is a testament.I've written about the inevitability of security program failures in the past. No matter how secure you think you are, a breach will occur. It could be small or big, but it will happen -- and probably in the least likely manner than what you would have suspected.

What's that? You say you're PCI DSS compliant? That's excellent. Congratulations on jumping through the hoops to get your gold star. Want to know something scary? Heartland was given the PCI compliance seal of approval back in 2008 from Trustwave. You can see that here on VISA's "List of PCI DSS Compliant Service Providers" (PDF); meantime, according to some reports, its breach may have occurred as far back as May 2008.

"Security Warrior" blogger Anton Chuvakin posed the question you're probably wondering yourself: How can a company "that was audited by a QSA and deemed 'PCI DSS compliant' at some point be breached and have all their credit card information stolen at some later point?" I know I was asking the same question when I saw the VISA compliance list. Anton poses some scenarios as to how, but I think the real reason is that companies don't realize the PCI DSS is truly a process and not a checklist.

PCI DSS does not mean you are completely safe from being a data-breach statistic. It means you've complied with the requirements, subsequent scans confirm that, and some trustworthy and diligent QSA has filled out the checklist saying you've done so. Being secure does not end there. The elements that go into complying with PCI DSS need to be followed day in and day out -- not just every quarter when your scan is scheduled or your annual pentest comes up.

What it's going to take for companies to realize this? Maybe they (or someone very close to them) will have to experience a breach themselves. What would happen to many of the compliant companies if their scans were run randomly throughout the year instead of a scheduled monthly or quarterly date? Thanks to Heartland, it's obvious 2009 is going to be an interesting year with regard to breaches and PCI DSS.

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-29370
PUBLISHED: 2021-04-13
A UXSS was discovered in the Thanos-Soft Cheetah Browser in Android 1.2.0 due to the inadequate filter of the intent scheme. This resulted in Cross-site scripting on the cheetah browser in any website.
CVE-2021-3460
PUBLISHED: 2021-04-13
The Motorola MH702x devices, prior to version 2.0.0.301, do not properly verify the server certificate during communication with the support server which could lead to the communication channel being accessible by an attacker.
CVE-2021-3462
PUBLISHED: 2021-04-13
A privilege escalation vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could allow unauthorized access to the driver's device object.
CVE-2021-3463
PUBLISHED: 2021-04-13
A null pointer dereference vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could cause systems to experience a blue screen error.
CVE-2021-3471
PUBLISHED: 2021-04-13
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none.