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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: I think the boss is bing watching '70s TV shows again!
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26244
PUBLISHED: 2020-12-02
Python oic is a Python OpenID Connect implementation. In Python oic before version 1.2.1, there are several related cryptographic issues affecting client implementations that use the library. The issues are: 1) The IdToken signature algorithm was not checked automatically, but only if the expecte...
CVE-2020-28206
PUBLISHED: 2020-12-02
An issue was discovered in Bitrix24 Bitrix Framework (1c site management) 20.0. An "User enumeration and Improper Restriction of Excessive Authentication Attempts" vulnerability exists in the admin login form, allowing a remote user to enumerate users in the administrator group. This also ...
CVE-2017-14451
PUBLISHED: 2020-12-02
An exploitable out-of-bounds read vulnerability exists in libevm (Ethereum Virtual Machine) of CPP-Ethereum. A specially crafted smart contract code can cause an out-of-bounds read which can subsequently trigger an out-of-bounds write resulting in remote code execution. An attacker can create/send m...
CVE-2017-2910
PUBLISHED: 2020-12-02
An exploitable Out-of-bounds Write vulnerability exists in the xls_addCell function of libxls 2.0. A specially crafted xls file can cause a memory corruption resulting in remote code execution. An attacker can send malicious xls file to trigger this vulnerability.
CVE-2020-13493
PUBLISHED: 2020-12-02
A heap overflow vulnerability exists in Pixar OpenUSD 20.05 when the software parses compressed sections in binary USD files. A specially crafted USDC file format path jumps decompression heap overflow in a way path jumps are processed. To trigger this vulnerability, the victim needs to open an atta...