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.

Risk

10/1/2010
03:04 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

New Verizon Report: Non-PCI Compliant Organizations Suffer More Breaches

First report on real-world PCI assessments by Verizon shows nearly 80 percent of companies miss the compliance mark in first audit

Data from PCI DSS assessments conducted by Verizon Business' PCI auditors shows that organizations hit by breaches are 50 percent less likely to be PCI-compliant than its other clients.

The first-ever Verizon Payment Card Industry Compliance Report, released today, analyzed findings from actual PCI DSS assessments Verizon conducted between 2008 and 2009. The report also shows that only 22 percent of organizations score as compliant with the PCI DSS at their first audit.

Protecting stored data, tracking and monitoring access to network resources and cardholder data, and regularly testing security systems and processes were the top three reasons for breaches in Verizon's 2010 Data Breach Investigations Report. And it's those three security areas where companies are having difficulty deploying or complying with in PCI, according to Verizon.

"We found a direct correlation to the top reasons for data breaches," says Jen Mack, director of global PCI consulting services at Verizon. "PCI requires protecting source data, monitoring and reviewing, and systematically checking and scanning and penetration testing ... And we could see those were the top reasons for breaches in our breach report. We see in our PCI report that these areas have the least amount of requirements in place at the time of their Initial Report on Compliance."

Mack says these are PCI compliance areas where organizations are most lagging behind. Overall, the numbers showing PCI-compliant companies being less likely to suffer a breach is good news for the specification, she says.

"I would say this is very good news for PCI," Mack says. "This pushes for maintaining good security practices."

The report analyzes findings in 200 PCI DSS assessments conducted by Verizon's PCI Qualified Security Assessors (QSAs), and correlates it with the company's breach report.

The top attack techniques used to breach payment card data were malware and hacking (25 percent); SQL injection attacks (24 percent); exploiting default or guessable credentials (21 percent); abuse of system access privileges (17 percent); use of stolen login credentials (14 percent); RAM scraper malware (13 percent); exploiting insufficient authorization (13 percent); packet sniffer (13 percent); and keylogger/spyware (13 percent), according to the report.

Interestingly, three-fourths of the organizations audited by Verizon met 79 percent of PCI testing processes. "So folks not in compliance are not that far off," Mack says. "PCI compliance is still an ongoing effort. It's more of a lifestyle change."

Verizon recommends building security into the business process, aligning compliance and security as one effort and approaching compliance as a continuous process rather than a "point-in-time event." And keeping the scope of the assessment manageable is also crucial, so Verizon advises controlling data closely.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
A Realistic Threat Model for the Masses
Lysa Myers, Security Researcher, ESET,  10/9/2019
USB Drive Security Still Lags
Dark Reading Staff 10/9/2019
Virginia a Hot Spot For Cybersecurity Jobs
Jai Vijayan, Contributing Writer,  10/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-17612
PUBLISHED: 2019-10-15
An issue was discovered in 74CMS v5.2.8. There is a SQL Injection generated by the _list method in the Common/Controller/BackendController.class.php file via the index.php?m=Admin&c=Ad&a=category sort parameter.
CVE-2019-17613
PUBLISHED: 2019-10-15
qibosoft 7 allows remote code execution because do/jf.php makes eval calls. The attacker can use the Point Introduction Management feature to supply PHP code to be evaluated. Alternatively, the attacker can access admin/index.php?lfj=jfadmin&action=addjf via CSRF, as demonstrated by a payload in...
CVE-2019-17395
PUBLISHED: 2019-10-15
In the Rapid Gator application 0.7.1 for Android, the username and password are stored in the log during authentication, and may be available to attackers via logcat.
CVE-2019-17602
PUBLISHED: 2019-10-15
An issue was discovered in Zoho ManageEngine OpManager before 12.4 build 124089. The OPMDeviceDetailsServlet servlet is prone to SQL injection. Depending on the configuration, this vulnerability could be exploited unauthenticated or authenticated.
CVE-2019-17394
PUBLISHED: 2019-10-15
In the Seesaw Parent and Family application 6.2.5 for Android, the username and password are stored in the log during authentication, and may be available to attackers via logcat.