Threat Intelligence

5/8/2018
08:00 AM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

Publicly Disclosed Breaches Down Drastically in Q1 2018

Quietest first quarter since 2012, according to new report from Risk Based Security.

The early part of 2018 has brought a spot of good news, as reports from first quarter show that the number of publicly reported breaches dropped dramatically compared to the same period of time last year.

"We haven't seen a Q1 this quiet since 2012," says Inga Goddijn, executive vice president for Risk Based Security, which today released the statistics from its Q1 2018 Data Breach Trends report

The study shows that organizations experienced 686 breaches that exposed approximately 1.4 billion records. That's nothing to sneeze at, but the good news is that compared to Q1 2017 both numbers have gone down more than half. In the first three months of 2017, the number of exposed records had already added up to 3.4 billion.

Goddijn and the Risk Based Security team are not sure exactly why the numbers have shifted lower, though they have a few theories. First of all, the number of attacks phishing for employee W-2 wage and salary data has plummeted. Last year's report saw 200 of these incidents in Q1 and this year it's dropped down to 35. Additionally, the change could also be attributable to the momentum growing in cryptomining activity. 

"We also think the shift toward cryptomining is possibly easing some of the attention on data theft," says Goddijn. This would reduce the number of publicly disclosed breaches but could represent a jump in malicious activity that's off the books, so to speak. "It's still too early to say for sure but it does go to show, malicious activity will follow the best opportunities for making a profit."

Regardless of shifts in attack trends, Goddijn says that all of the same old security fundamentals still apply to new threats. 

"Take cryptomining for example," she says. "Many of the same processes that are used to protect against ransomware - like good vulnerability management, restricting code execution, strong email filtering and helping users stay safe on line - are helpful for stopping mining malware too."

Organizations should also probably keep things in perspective. While the number of incidents is at a six-year low for early year activity, the only reason year-over-year number of breached records dropped is because there was such a huge spike in 2017. The 1.4 billion records exposed early this year is still more than double than the number of records exposed during Q1 of 2014, 2015 and 2016 combined.   

Interestingly, aside from the drop in W-2 phishing incidents, the mix of incident types and victim organization still remains largely static.

"The other metrics we track, such as breach types, who is being impacted, (and) size of breaches, are very similar to recent quarters," says Goddijn. "We have not observed sizable changes in the type of organizations being breached, the type of data that is being exposed, the number of large events, insider vs outsider activity, breach severity scores or where breaches are taking place. We would have expected other sizable shifts to be evident along with the drop in the number of breaches but that is not the case."

Related Content:

 

 

 

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
5/9/2018 | 8:16:56 AM
PUBLIC DISCLOSED
OK - what about the ones we do not know about?  
Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
BEC Scammer Pleads Guilty
Dark Reading Staff 3/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Well, at least it isn't Mobby Dick!
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
The State of Cyber Security Incident Response
The State of Cyber Security Incident Response
Organizations are responding to new threats with new processes for detecting and mitigating them. Here's a look at how the discipline of incident response is evolving.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2016-10743
PUBLISHED: 2019-03-23
hostapd before 2.6 does not prevent use of the low-quality PRNG that is reached by an os_random() function call.
CVE-2019-9947
PUBLISHED: 2019-03-23
An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.2. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the query string or PATH_INFO) follo...
CVE-2019-9948
PUBLISHED: 2019-03-23
urllib in Python 2.x through 2.7.16 supports the local_file: scheme, which makes it easier for remote attackers to bypass protection mechanisms that blacklist file: URIs, as demonstrated by triggering a urllib.urlopen('local_file:///etc/passwd') call.
CVE-2019-9945
PUBLISHED: 2019-03-23
SoftNAS Cloud 4.2.0 and 4.2.1 allows remote command execution. The NGINX default configuration file has a check to verify the status of a user cookie. If not set, a user is redirected to the login page. An arbitrary value can be provided for this cookie to access the web interface without valid user...
CVE-2019-9942
PUBLISHED: 2019-03-23
A sandbox information disclosure exists in Twig before 1.38.0 and 2.x before 2.7.0 because, under some circumstances, it is possible to call the __toString() method on an object even if not allowed by the security policy in place.