Gartner Blog Network


Is MDR just Another Acronym that means Managed Security?

by Pete Shoard  |  June 11, 2020  |  Submit a Comment

The Managed Detection and Response (MDR) market has experienced great traction over the last few months and years. This has been, in part, due to the simplicity of the concept. Although there have been a few ‘pretenders’ that have tried to get into the club with ‘fake ID’. As with all new and exciting terms, its really easy for marketing departments to grab onto them and put together a PowerPoint. All of a sudden that vendor is an ‘MDR’, but are they? Recently, questions from vendors and end users alike have regularly included “What really is MDR?”

I thought it might be worth writing a blog post to try and explain what MDR is. As well as how it sits within the wider sphere of ‘Detection and Response’ type services. Much like any product in any market. There is competition and the story becomes about adding differentiation to try and make a product stand out. This is easy with a chocolate bar or a breakfast cereal, but not so easy with security services. Unlike most products its difficult to cut through to what you are actually buying when you buy that security service. Buyers must be consumption-model and outcome focused to get clarity. Herein lies the key to understanding the difference between MDR and ‘other’ detection and response services.

What defines MDR?

Does MDR really mean you’re going to get the ‘best’ detection? Are you really looking for the most advanced tool-sets and funky dashboards? There are three defining characteristics that buyers of threat detection and response must be focused on for MDR to be right for them:

  1. Turn-key, fast to deploy service.
  2. Skilled threat analysis, interpretation and actionable outcomes.
  3. Fully managed, not a technology, not automated.

Naturally there are some things here that i have missed out. MDR services must have a wide range of use cases, ability to detect threats and capability to respond quickly and remotely. But other services that detect and respond to threats can have these things. In the same way buyers don’t go-to a car showroom and say “I’d like a car, with wheels and lights”. You don’t need to go to a MDR provider and ask for the things that are most common with detection and response type services.

A firm favorite is ‘Threat Hunting’. Its obvious that all MDR services must run on well-developed Threat Hunting processes. If they don’t they are simply not delivering on #2 of the defining characteristics above. you can dig a little deeper into my thoughts about this in a post i published in April “What Really is Threat Hunting?”

Does MDR need to run on specific data/technologies?

Can MDR run on log data, or using a SIEM? The simple answer is yes, but there are a few caveats; Log data is often difficult to integrate with a detection solution, especially custom log sources. Therefore log data does make it harder, but not impossible to meet #1 of the defining characteristics above. Furthermore it is hard to create a solution which includes ‘response’ if it is simply a passive listener. It then stands to reason that logs alone cannot make a detection and response service MDR. The same applies for any passive collection and processing based technology.

The ‘R’ in MDR means there is a direct requirement for a method for feedback. And before someone says “isn’t a security incident report with actionable ‘advice’ feedback”, yes it is, but its not response. The same way that simply telling your four year old not to draw on the wall again is not as effective a response as taking the crayons away.

What about Automation?

Finally, in defining characteristic #3 ‘not automated’ is important, and it is. When you buy a ‘service’ you don’t expect the technology to do all of the work (not that it would be possible anyway). It’s perfectly acceptable (and beneficial) for services providers that offer MDR to automate ‘parts’ of their workflow. That’s logical cost optimisation and improves consistency. But no managed security service is fully automated. Without the skilled threat analysis, constant evolution and development, they become outdated and useless over time.

So, in answer to the question i posed at the beginning, The one that brought you here… Is MDR just Another Acronym that means Managed Security? No its not, its a breed of detection and response service, one that helps you accelerate maturity by being turnkey, one that brings expertise, evolution and development. Something that can be part of a wider detection and response strategy or stand up on its own. MDR provides outcomes that reduce cyber security risk in your organization.

 

Additional Resources

Drive Cost Optimization and Efficiencies With IT Vendor Portfolio Rationalization

Drive savings and efficiencies by defining, socializing and executing a rationalization plan.

Read Free Gartner Research

Category: security-of-networks-and-endpoints  security-operations  sourcing-procurement-and-vendor-management-leaders  

Tags: detection-response  mdr  mss  

Pete Shoard
Sr Director Analyst I
3 years at Gartner
17 years IT Industry

Pete Shoard is part of the Security Operations team. Covering analysis of and selection criteria for threat detection and response Managed Security Services (MSS) such as Managed Detection and Response (MDR) and Vulnerability Management (VM) services. Also security detection and response technologies such as Security Information and Event Management (SIEM), User Entity Behavioral Analytics (UEBA) and Deception. Supporting Gartner's ITL research in wider areas such as Security Operation Centre (SOC) best practice and security metrics and measurement.Read Full Bio




Leave a Reply

Your email address will not be published. Required fields are marked *

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.