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

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/14/2020
Omdia Research Launches Page on Dark Reading
Tim Wilson, Editor in Chief, Dark Reading 7/9/2020
Why Cybersecurity's Silence Matters to Black Lives
Tiffany Ricks, CEO, HacWare,  7/8/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-1448
PUBLISHED: 2020-07-14
A remote code execution vulnerability exists in Microsoft Word software when it fails to properly handle objects in memory, aka 'Microsoft Word Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2020-1446, CVE-2020-1447.
CVE-2020-1449
PUBLISHED: 2020-07-14
A remote code execution vulnerability exists in Microsoft Project software when the software fails to check the source markup of a file, aka 'Microsoft Project Remote Code Execution Vulnerability'.
CVE-2020-1450
PUBLISHED: 2020-07-14
A cross-site-scripting (XSS) vulnerability exists when Microsoft SharePoint Server does not properly sanitize a specially crafted web request to an affected SharePoint server, aka 'Microsoft Office SharePoint XSS Vulnerability'. This CVE ID is unique from CVE-2020-1451, CVE-2020-1456.
CVE-2020-1451
PUBLISHED: 2020-07-14
A cross-site-scripting (XSS) vulnerability exists when Microsoft SharePoint Server does not properly sanitize a specially crafted web request to an affected SharePoint server, aka 'Microsoft Office SharePoint XSS Vulnerability'. This CVE ID is unique from CVE-2020-1450, CVE-2020-1456.
CVE-2020-1454
PUBLISHED: 2020-07-14
This vulnerability is caused when SharePoint Server does not properly sanitize a specially crafted request to an affected SharePoint server.An authenticated attacker could exploit this vulnerability by sending a specially crafted request to an affected SharePoint server, aka 'Microsoft SharePoint Re...