5 Things You Probably Missed In The Verizon DBIR
1 of 6
Source: Verizon
If you're still digesting this year's massive Verizon Data Breach Investigations Report (DBIR), you're not alone. The super-sized 2015 DBIR came with the usual popular data and rare insight on real-world incidents and breach cases, but with the addition of loads of data contributed by 70 other organizations from around the world.
Unless you've been combing the DBIR regularly since it was published in April, there's a good chance you missed a few things in it. Marc Spitler, co-author of the DBIR and senior risk analyst with Verizon, joined Dark Reading Radio yesterday and shared what may have been some of the possibly lesser-noticed or publicized nuggets from the report.
So grab your copy of the DBIR, and follow along to see what key research points you may have missed. Consider it a little summer reading for the beach.
Kelly Jackson Higgins is Executive Editor at DarkReading.com. 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
1 of 6
Comment |
Print |
More Insights
Comments
Newest First | Oldest First | Threaded View
Re: 5 things you missed
ata and rare insight on real-world incidents and breach cases, but with the addition of loads of data contributed by 70 other organizations from around the world.
Unless you've been com
Unless you've been com
Re: Mobile Malware not a significant threat
I think you forgot the word "yet." ;)
Sure, Windows is where the action is...but that's more a function of its proliferation/market dominance and less a function of how many vulnerabilities it has. (In 2014, for instance, several times more vulnerabilities -- and of greater severity on the whole -- were discovered in Linux, OSX, and iOS than in any Windows OS.)
Same thing if we look at mobile only, too. iOS has way more vulnerabilities than Android, but Android is attacked way more often than iOS because there are so many more Android phones out there than iOS phones (and because it's far easier to attack people via malicious apps on Android than it is on iOS because of Apple's tight iTunes Store controls).
Anyway, it's worthwhile to keep an eye on everything across the board. There's little telling how the results will differ five or ten years from now.
Sure, Windows is where the action is...but that's more a function of its proliferation/market dominance and less a function of how many vulnerabilities it has. (In 2014, for instance, several times more vulnerabilities -- and of greater severity on the whole -- were discovered in Linux, OSX, and iOS than in any Windows OS.)
Same thing if we look at mobile only, too. iOS has way more vulnerabilities than Android, but Android is attacked way more often than iOS because there are so many more Android phones out there than iOS phones (and because it's far easier to attack people via malicious apps on Android than it is on iOS because of Apple's tight iTunes Store controls).
Anyway, it's worthwhile to keep an eye on everything across the board. There's little telling how the results will differ five or ten years from now.
5 things you missed
I like your way of presentation.Thanks dear for such an informatic blog.
Re: Mobile Malware not a significant threat
Yep, attackers always start with the easy entry point. But as Marc Spitler said, it's only a matter of time before mobile devices are a big part of the attack chain.
Mobile Malware not a significant threat
It is nice to see this confirmation that, despite all the products and hot air from security vendors, mobile devices are not where the security breaches are happening. Windows is still by far the low hanging fruit for attackers.
relying on their customers' security
Great stuff Kelly. I love the way they put this: "What we have here are companies ... relying on the security of their customer base. Over one half of Web app attacks came from the use of stolen credentials." So basically organizations are outsourcing security to their customers, and I suppose to the other organizations that the customers do business with.
White Papers
Video
0 Comments
Current Issue
Flash Poll
The State of IT and Cybersecurity
IT and security are often viewed as different disciplines - and different departments. Find out what our survey data revealed, read the report today!
Twitter Feed
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database CVE-2011-2765
PUBLISHED: 2018-08-20
PUBLISHED: 2018-08-20
PUBLISHED: 2018-08-20
PUBLISHED: 2018-08-20
PUBLISHED: 2018-08-20
From DHS/US-CERT's National Vulnerability Database CVE-2011-2765
PUBLISHED: 2018-08-20
pyro before 3.15 unsafely handles pid files in temporary directory locations and opening the pid file as root. An attacker can use this flaw to overwrite arbitrary files via symlinks.
CVE-2018-15594PUBLISHED: 2018-08-20
arch/x86/kernel/paravirt.c in the Linux kernel before 4.18.1 mishandles certain indirect calls, which makes it easier for attackers to conduct Spectre-v2 attacks against paravirtual guests.
CVE-2018-15572PUBLISHED: 2018-08-20
The spectre_v2_select_mitigation function in arch/x86/kernel/cpu/bugs.c in the Linux kernel before 4.18.1 does not always fill RSB upon a context switch, which makes it easier for attackers to conduct userspace-userspace spectreRSB attacks.
CVE-2018-15573PUBLISHED: 2018-08-20
** DISPUTED ** An issue was discovered in Reprise License Manager (RLM) through 12.2BL2. Attackers can use the web interface to read and write data to any file on disk (as long as rlm.exe has access to it) via /goform/edit_lf_process with file content in the lfdata parameter and a pathname in the lf...
CVE-2018-15574PUBLISHED: 2018-08-20
** DISPUTED ** An issue was discovered in the license editor in Reprise License Manager (RLM) through 12.2BL2. It is a cross-site scripting vulnerability in the /goform/edit_lf_get_data lf parameter via GET or POST. NOTE: the vendor has stated "We do not consider this a vulnerability."
- Terms of Service
- Privacy Statement
- Legal Entities
- Copyright © 2018 UBM, All rights reserved
Tweet This