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
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.