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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-35196
PUBLISHED: 2021-06-21
** DISPUTED ** Manuskript through 0.12.0 allows remote attackers to execute arbitrary code via a crafted settings.pickle file in a project file, because there is insecure deserialization via the pickle.load() function in settings.py. NOTE: the vendor's position is that the product is not intended fo...
CVE-2010-1433
PUBLISHED: 2021-06-21
Joomla! Core is prone to a vulnerability that lets attackers upload arbitrary files because the application fails to properly verify user-supplied input. An attacker can exploit this vulnerability to upload arbitrary code and run it in the context of the webserver process. This may facilitate unauth...
CVE-2010-1434
PUBLISHED: 2021-06-21
Joomla! Core is prone to a session fixation vulnerability. An attacker may leverage this issue to hijack an arbitrary session and gain access to sensitive information, which may help in launching further attacks. Joomla! Core versions 1.5.x ranging from 1.5.0 and up to and including 1.5.15 are vulne...
CVE-2010-1435
PUBLISHED: 2021-06-21
Joomla! Core is prone to a security bypass vulnerability. Exploiting this issue may allow attackers to perform otherwise restricted actions and subsequently retrieve password reset tokens from the database through an already existing SQL injection vector. Joomla! Core versions 1.5.x ranging from 1.5...
CVE-2010-0413
PUBLISHED: 2021-06-21
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none.