Vulnerabilities / Threats

3/23/2015
10:45 AM
Joshua Goldfarb
Joshua Goldfarb
Commentary
Connect Directly
Twitter
RSS
E-Mail vvv
100%
0%

Context: Finding The Story Inside Your Security Operations Program

What's missing in today's chaotic, alert-driven incident response queue is the idea of a narrative that provides a detailed understanding of how an attack actually unfolds.

Decision-making is a regular part of our lives. Most of us probably don’t give much thought to how many decisions we make on a daily basis. Although we may not be aware of it, particularly for smaller decisions, each decision involves considering multiple data points. Granted, there will always be some decisions that we make emotionally or irrationally. But for logical decisions, let’s take a step back and consider what happens during the decision-making process.

For logical decisions, the decision-maker will typically understand the decision that needs to be made, develop criteria, gather supporting data, and then evaluate the supporting data per the criteria. This probably sounds like a familiar process, but what does this have to do with information security? That is a great question, and it is one that I would like to discuss further.

In the security operations and incident response realm, organizations typically manage their workflow out of a unified work queue. Into this work queue may stream different types of information, the most common type being alerts. The volume of alerts heading into this work queue is typically extremely high, the noise level is quite high, and the signal is quite low. The end result of this alert-driven work queue can be quite chaotic. Why is this an issue, and why am I calling attention to this here? It goes back to the goal of that unified work queue.

The goal of a security operations and incident response work queue should be to support decision-making. Let’s put aside, for the moment, the question of “Where do I begin?” when looking at a somewhat overwhelming queue of alerts. Let’s think about this question: If I pick an alert out of the work queue, how do I know if it is a false positive or something that will land me in the headlines in six months’ time? The answer to that question is not trivial, and it’s one reason why detection rates are so low within many organizations.

What’s missing from the current-day work queue is the idea of a narrative. Each alert in the work queue is a snapshot, a moment in time, and a part of the overall story of what occurred. It’s a piece of the puzzle. Just as I cannot look at one piece of a 1,000 piece jigsaw puzzle and understand what the fully assembled puzzle looks like, I also cannot look at one alert and understand exactly what happened within my organization.

In order to understand the complete picture, alerts in the work queue must be vetted, qualified, investigated, and enriched with additional contextual information. This contextual information includes supporting data from relevant corroborating data sources, intelligence, and an understanding of how the attack unfolded. In other words, the alert needs an accurate story built around it to properly support decision-making. It needs a narrative.

Typically, vetting, qualifying, investigating, and enriching is a very manual process that some organizations do better than others. As you can imagine, this presents quite a challenge to the typical resource-constrained organization. It is a challenge that keeps detection rates low and persistence times high. Long term, the paradigm must shift away from today’s alert-driven model and toward a narrative-driven model, which will improve detection rates and reduce persistence times. But presenting the analyst with a queue of pre-assembled narratives, rather than a queue of context-less alerts changes the nature of security operations and incident response.

The narrative-driven model creates a world in which analysts work through a queue of assembled puzzles and painted pictures that empower them to make better decisions. Similarly, a lack of context is one of the main reasons decision-making is so hard and why so many breaches fly under the radar. The narrative-driven world will be one that supports better decision-making, resulting in stronger signal, less noise, and fewer missed cues.

It may not surprise you that this is a topic I am quite passionate about. Having spent a long time on the operational side, I long felt the pain of inadequate decision support in the security operations and incident response realm. When I speak to professionals currently in operational roles, it’s clear to me that they feel this pain as well. From the discussions I’ve had, I believe that the security operations community is ready for a move from an alert-driven model to a narrative-driven model. In the end, it all boils down to the ability to make better decisions about what’s going on within our organizations. Better decisions, in turn, improve our overall security postures.

Josh (Twitter: @ananalytical) is an experienced information security leader with broad experience building and running Security Operations Centers (SOCs). Josh is currently co-founder and chief product officer at IDRRA and also serves as security advisor to ExtraHop. Prior to ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
josh@idrra.com
50%
50%
[email protected],
User Rank: Apprentice
3/24/2015 | 11:00:24 AM
Re: Powerful Analysis
Yes, correct Marilyn.  Just like contributing to DarkReading. ;-)
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
3/24/2015 | 10:30:16 AM
Re: Powerful Analysis
Thanks, Josh. Like most things, I expect this is something that takes a little bit of practice, to get good at!
josh@idrra.com
50%
50%
[email protected],
User Rank: Apprentice
3/24/2015 | 10:24:13 AM
Re: Powerful Analysis
Thank you Marilyn for what is a great question.  In general, pitfalls that can impede or obstruct the narrative can vary widely, but a few common ones are:

* Lack of telemetry to support narrative-building

* Lack of intelligence/background contextual information regarding activity of interest

* Shortage of expertise require to design narrative-driven workflow

* Immature or unreliable methods for enrichment of data and addition of contextual information

The narrative would seem to be preferred over alerts for internal incidents (i.e., incidents within the organization).  Perhaps for external incidents (e.g., attacks on partners or third parties) where there is less control, less telemetry, and/or less influence, narratives wouldn't work so well.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
3/24/2015 | 10:09:04 AM
Re: Powerful Analysis
Josh, what are some of the common pitfalls to watch out for when applying a narrative approach to security operations programs? And when does it not make sense to use this strategy?
josh@idrra.com
50%
50%
[email protected],
User Rank: Apprentice
3/23/2015 | 9:08:00 PM
Re: Powerful Analysis
Thank you for your comments and question.  I think that after detection, one needs to move to analysis/forensics, and then on to response.  What's cool about the narrative approach is that it gets us much further down the road of analysis/forensics than alerts do.  When the puzzle is partially or wholly assembled for us, some of the analysis/forensics that needs to be done is also done for us.  Helps to save time and reduce human error.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
3/23/2015 | 2:32:50 PM
Powerful Analysis
Great article! This type of thinking can be very beneficial in all aspects of life when trying to analyze a situation. It's not only the discovery phase however that may be difficult for a security program but the execution phase of what is done with that knowledge.

Do you recommend employing the same principles? Or how would you recommend proceeding after the detection phase?
High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-1659
PUBLISHED: 2019-02-21
A vulnerability in the Identity Services Engine (ISE) integration feature of Cisco Prime Infrastructure (PI) could allow an unauthenticated, remote attacker to perform a man-in-the-middle attack against the Secure Sockets Layer (SSL) tunnel established between ISE and PI. The vulnerability is due to...
CVE-2019-8983
PUBLISHED: 2019-02-21
MDaemon Webmail 14.x through 18.x before 18.5.2 has XSS (issue 1 of 2).
CVE-2019-8984
PUBLISHED: 2019-02-21
MDaemon Webmail 14.x through 18.x before 18.5.2 has XSS (issue 2 of 2).
CVE-2018-20122
PUBLISHED: 2019-02-21
The web interface on FASTGate Fastweb devices with firmware through 0.00.47_FW_200_Askey 2017-05-17 (software through 1.0.1b) exposed a CGI binary that is vulnerable to a command injection vulnerability that can be exploited to achieve remote code execution with root privileges. No authentication is...
CVE-2018-6687
PUBLISHED: 2019-02-21
Loop with Unreachable Exit Condition ('Infinite Loop') in McAfee GetSusp (GetSusp) 3.0.0.461 and earlier allows attackers to DoS a manual GetSusp scan via while scanning a specifically crafted file . GetSusp is a free standalone McAfee tool that runs on several versions of Microsoft Windows.