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.

Threat Intelligence

11/19/2019
01:45 PM
50%
50%

Most Companies Lag Behind '1-10-60' Benchmark for Breach Response

Average company needs 162 hours to detect, triage, and contain a breach, according to a new CrowdStrike survey.

The vast majority of companies cannot respond in time to prevent attackers from infecting other systems on their networks, according to a new CrowdStrike report released today.

The report, based on a global survey of 1,900 senior IT managers and security professionals, found only 33% of respondents thought their companies could contain a breach within an hour, with 31 hours as the average time to close a breach once it is discovered. In total, the average company would need 162 hours to detect, triage, and contain a breach, according to the CrowdStrike survey. 

The reality of businesses' cybersecurity response falls far short of what the cybersecurity firm considers the best practice: 1 minute to detect, 10 minutes to triage, and 60 minutes to contain. 

"Clearly there is a lot of room for improvement to get to the benchmark," says Thomas Etheridge, vice president of services at CrowdStrike. "The faster an organization has visibility into the initial stages of an attack, the better organizations are prepared to stop breaches."

The report gives a view into the maturity level of companies' security incident response groups and how effective they are against sophisticated threats. On average, only 5% of respondents believed they could regularly hit the 1:10:60 benchmark, and only 11% thought they could regularly detect a threat in one minute. 

"If [the] one-minute detection time could be achieved, IT leaders and security professionals alike can see the positive impact," the report stated. "Not only would it give the intruder less time to try to access their targeted data, but it also gives the organization a head start when it comes to investigating the incident and ultimately containing [the attack]."

On average, 83% of respondents said they believe nation-state attacks to be a clear danger to their organizations. Companies in India were most concerned, with 97% of respondents indicating that attacks from nation-states were a danger, while organizations in Singapore worried the second most (92%), followed by US companies, coming in third (84%).

"The faster you detect a nation-state attack before it spreads throughout the organization, the less damage it will do," Etheridge says. "In many cases, e-crime actors are adopting many of the same tactics — attacking in stages and spreading through the organizations before demanding a ransom." 

The 1-10-60 rule is based on CrowdStrike data that shows most nation-state and criminals adversaries break out from the initial beachhead in a network and move laterally to other systems within hours. In 2017, the average adversary whose operations were investigated by CrowdStrike had an average breakout time of two hours. In 2018, when the company analyzed the data by nation, Russian nation-state actors executed most efficiently, with a breakout time of 19 minutes, while North Korean actors came in second with a breakout time of 2 hours, 20 minutes, and China-linked actors took third with a breakout time of approximately four hours.

CrowdStrike maintains that companies that detect intrusions, fully investigate the incident, and respond to the compromise within an hour are much more likely to limit damage from attacks.

"Organizations that meet this 1-10-60 benchmark are much more likely to eradicate the adversary before the attack spreads out from its initial entry point, minimizing impact and further escalation," the company said in its "2019 Global Threat Report."

In reality, the average organization takes 120 hours to detect an attack, five hours to triage, six hours to investigate, and 31 hours to contain, according to respondents to CrowdStrike's survey.

To some degree, security teams have accepted the status quo. The largest portion of respondents — 33% — said they feel attackers are always one step ahead, making them more difficult to detect, according to the survey. About the same number — 32% — blame legacy infrastructure for making security more difficult to achieve. Other major reasons for the slow detection of threats include a lack of resources, shadow IT, and difficulty in being able to hire the right people.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "How Medical Device Vendors Hold Healthcare Security for Ransom.'"

Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
How Attackers Could Use Azure Apps to Sneak into Microsoft 365
Kelly Sheridan, Staff Editor, Dark Reading,  3/24/2020
Malicious USB Drive Hides Behind Gift Card Lure
Dark Reading Staff 3/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-10940
PUBLISHED: 2020-03-27
Local Privilege Escalation can occur in PHOENIX CONTACT PORTICO SERVER through 3.0.7 when installed to run as a service.
CVE-2020-10939
PUBLISHED: 2020-03-27
Insecure, default path permissions in PHOENIX CONTACT PC WORX SRT through 1.14 allow for local privilege escalation.
CVE-2020-6095
PUBLISHED: 2020-03-27
An exploitable denial of service vulnerability exists in the GstRTSPAuth functionality of GStreamer/gst-rtsp-server 1.14.5. A specially crafted RTSP setup request can cause a null pointer deference resulting in denial-of-service. An attacker can send a malicious packet to trigger this vulnerability.
CVE-2020-10817
PUBLISHED: 2020-03-27
The custom-searchable-data-entry-system (aka Custom Searchable Data Entry System) plugin through 1.7.1 for WordPress allows SQL Injection. NOTE: this product is discontinued.
CVE-2020-10952
PUBLISHED: 2020-03-27
GitLab EE/CE 8.11 through 12.9.1 allows blocked users to pull/push docker images.