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

4/11/2018
04:58 PM
Connect Directly
Twitter
RSS
E-Mail
0%
100%

Attacker Dwell Time Still Too Long, Research Shows

New DBIR and M-Trends reports show the window between compromise and discovery are still way too long.

In the past seven years, cybersecurity teams have cut down the time it takes to discover a security intrusion by fourfold. Unfortunately, that improvement in the window between initial attack and discovery of the incident isn't nearly enough to actually make a difference in blocking the typical intrusion from turning into a full-fledged data breach.

In fact, data from several new industry reports out in the last week show that most organizations would need to make that time to discover at least 100 times faster to actually prevent most successful breaches of data.

First among the latest spate of statistics are the numbers from FireEye/Mandiant's 2018 M-Trends report. According to the study, the most recently measured dwell time - that is, the time between initial attack and discovery of the incident - equals an average of about 101 days for organizations worldwide.

That's up by two days since last year, but the good news is that this number is down significantly from 416 days back in 2011. Another positive sign the report relates is that the percentage of incidents discovered internally versus those disclosed by a third party is way up. Approximately 62% of incidents are now discovered internally, which shows organizations are doing work to raise the bar on their detection capabilities, FireEye says.

Nevertheless, these are just silver linings on thunderclouds. Yesterday's Verizon Data Breach Investigation Report (DBIR) showed that once they've compromised their target, the time it takes attackers to breach data is orders of magnitude shorter than the time it takes for victims (or third parties) to discover an attack.

"When breaches are successful, the time to compromise continues to be very short. While we cannot determine how much time is spent in intelligence gathering or other adversary preparations, the time from first action in an event chain to initial compromise of an asset is most often measured in seconds or minutes," write the authors of this year's DBIR.

That's scary, considering discovery time is measured by weeks and months - sometimes even years. The DBIR numbers show that 87% of compromises took minutes or less. Only 3% of compromises were discovered as quickly. Meanwhile, 68% of them took months or years to be discovered. 

Many IT leaders are at least aware of this huge delta between compromise and discovery time. Another study out yesterday from LogRhythm showed a significant lack of confidence among IT decision makers in the ability of their systems and processes to discover all potential breaches -about four in 10 report they lack confidence in the thoroughness of their detection capabilities.

And, here's the thing: time to discovery is just the start of the journey in responding to a compromise. There's also the time it takes to respond to, contain, and investigate a threat. According to the LogRhythm study, fewer than one-third of organizations say that even if they detected a major incident they'd be unable to contain it within an hour. And that time to contain compromises is going up. A different study conducted by Ponemon Institute on behalf of IBM Resilient Systems earlier this year shows that 57% of organizations are experiencing longer times to resolve security incidents.

Related content:

 

Interop ITX 2018

Join Dark Reading LIVE for two cybersecurity summits at Interop ITX. Learn from the industry’s most knowledgeable IT security experts. Check out the security track here. Register with Promo Code DR200 and save $200.

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
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
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-2015-3154
PUBLISHED: 2020-01-27
CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email.
CVE-2019-17190
PUBLISHED: 2020-01-27
A Local Privilege Escalation issue was discovered in Avast Secure Browser 76.0.1659.101. The vulnerability is due to an insecure ACL set by the AvastBrowserUpdate.exe (which is running as NT AUTHORITY\SYSTEM) when AvastSecureBrowser.exe checks for new updates. When the update check is triggered, the...
CVE-2014-8161
PUBLISHED: 2020-01-27
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values by triggering constraint violation and then reading the error message.
CVE-2014-9481
PUBLISHED: 2020-01-27
The Scribunto extension for MediaWiki allows remote attackers to obtain the rollback token and possibly other sensitive information via a crafted module, related to unstripping special page HTML.
CVE-2015-0241
PUBLISHED: 2020-01-27
The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to cause a denial of service (crash) or possibly execute arbitrary code via a (1) large number of digits when processing a numeric ...