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.

Attacks/Breaches

5/7/2019
04:20 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Orgs Are Quicker to Disclose Breaches Reported to Them Via External Sources

Companies that find a breach on their own take substantially longer to report a breach, a new analysis shows.

A security vendor's analysis of breach data from first-quarter 2019 suggests an organization that discovers a security breach on its own is actually likely to take longer to disclose it than an organization alerted to a breach via an external source.

Risk Based Security found that when organizations first learned of a breach from an external source such as law enforcement, they publicly reported the incident within 43 days, on average. In contrast, when organizations discovered a breach via an internal team, they took a much longer 74 days on average to report it. Half of all externally discovered incidents were reported in just eight days compared with a median of 46 days for internal discovery.

That finding is somewhat unexpected. It runs counter to the theory about organizations that are better able to detect a breach also being better prepared to respond to it, says Inga Goddijn, executive vice president of Risk Based Security. "We're very interested in understanding whether the first-quarter report findings are an outlier or a more typical result," Goddijn says.

For now, the reasons why it might be happening are really anyone's guess, she says. "We have some theories as to why companies that discover their own breaches would take longer to disclose them. But we'd like to see more data before pointing to possible reasons for the delay," Goddijn notes.

Risk Based Security's report shows that an astounding 1,903 breaches were publicly disclosed in the first three months of this year. That number has already put 2019 on track to being the worst year ever for data breaches. The number of reported breaches in first-quarter 2019 was 56.4% higher than the number reported in the same period last year. The number of exposed records shot up 28.9% from about 1.5 billion in 2018 to 1.9 billion this year.

As is usually the case, a handful of breaches were responsible for a vast majority of the records that were compromised last quarter. One breach alone — at email verification company Verifications.io — exposed some 983 million records containing names, email addresses, dates of birth, personal mortgage amounts, and other data. Most reports of the incident so far have pegged the number of exposed records at a smaller, but still staggeringly high, 763 million.

Risk Based Security's report showed that, together, the top five breaches in the first quarter accounted for about 1.3 billion of the total number of exposed records. In other words, the number of records exposed in the remaining 1,898 breaches combined was around 600,000.

Web Compromises Remain Top Cause for Data Exposures
Malicious hacking remained the top cause for data breaches. It accounted for 84.8% of reported security breaches last quarter. However, significantly more records once again were compromised through exposures on the Web — of the accidental, negligent, and malicious variety — than any other breach cause. Risk Based Security's analysis showed that nearly 68% of the records that were compromised in the first quarter were via leaks on the Web.

"Researchers are increasingly going public when they discover sizable, unprotected databases containing sensitive information," the Risk Based Security analysis noted. "Unfortunately, they aren't terribly difficult to find when you know where to look." The massive compromise at Verifications.io, for instance, happened because a MongoDB database containing the sensitive information was left completely open — without even password protection — and accessible to the Internet. 

More than eight in 10 (85.6%) of the records that were exposed last quarter belonged to organizations in the business sector, which in Risk Based Security's counting includes finance and insurance companies. Meanwhile, the government and education sectors — often criticized for lax security practices — accounted for some 5.8 million exposed records or less than 0.03% of the total last quarter.

"Despite so much attention on the need for improving security, breaches are still happening at an unprecedented rate," Goddijn says. "There really is no sign of a slowdown in breach activity, which to me illustrates just how difficult it is to protect networks and data."

Related Content:

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
White Papers
More White Papers
Comments
Newest First  |  Oldest First  |  Threaded View
AndrewfOP
50%
50%
AndrewfOP,
User Rank: Moderator
5/10/2019 | 11:23:32 AM
Breaches notified External vs. Internal, Average vs. Median
"...from an external source such as law enforcement, they publicly reported the incident within 43 days, on average.  ...via an internal team, they took a much longer 74 days on average to report it. Half of all externally discovered incidents were reported in just eight days compared with a median of 46 days for internal discovery."

 Makes perfect sense that organization would report breaches notified by external sources sooner.  Since the orgs do not control external sources, they either get ahead of the publicity or risk being exposed later.  However, my beef is with the big difference between the average and the median numbers.  Apparently, significant numbers of organization still not only don't take breaches seriously, but also have much longer response time comparing with the majority of organizations. 

 
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20399
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
CVE-2020-7915
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.
CVE-2019-20391
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r3 in the function resolve_feature_value() when an if-feature statement is used inside a bit. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20392
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r1 in the function resolve_feature_value() when an if-feature statement is used inside a list key node, and the feature used is not defined. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20393
PUBLISHED: 2020-01-22
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an empty description is used. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.