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?
WebAuthn, FIDO2 Infuse Browsers, Platforms with Strong Authentication
John Fontana, Standards & Identity Analyst, Yubico,  9/19/2018
Turn the NIST Cybersecurity Framework into Reality: 5 Steps
Mukul Kumar & Anupam Sahai, CISO & VP of Cyber Practice and VP Product Management, Cavirin Systems,  9/20/2018
NSS Labs Files Antitrust Suit Against Symantec, CrowdStrike, ESET, AMTSO
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-3914
PUBLISHED: 2018-09-21
An exploitable stack-based buffer overflow vulnerability exists in the retrieval of database fields in the video-core HTTP server of the Samsung SmartThings Hub STH-ETH-250 - Firmware version 0.20.17. The strcpy call overflows the destination buffer, which has a size of 2000 bytes. An attacker can s...
CVE-2018-3915
PUBLISHED: 2018-09-21
An exploitable stack-based buffer overflow vulnerability exists in the retrieval of database fields in the video-core HTTP server of the Samsung SmartThings Hub STH-ETH-250 - Firmware version 0.20.17. The strcpy call overflows the destination buffer, which has a size of 64 bytes. An attacker can sen...
CVE-2018-11240
PUBLISHED: 2018-09-21
An issue was discovered on SoftCase T-Router build 20112017 devices. There are no restrictions on the 'exec command' feature of the T-Router protocol. If the command syntax is correct, there is code execution both on the other modem and on the main servers. This is fixed in production builds as of S...
CVE-2018-11241
PUBLISHED: 2018-09-21
An issue was discovered on SoftCase T-Router build 20112017 devices. A remote attacker can read and write to arbitrary files on the system as root, as demonstrated by code execution after writing to a crontab file. This is fixed in production builds as of Spring 2018.
CVE-2018-16784
PUBLISHED: 2018-09-21
DedeCMS 5.7 SP2 allows XML injection, and resultant remote code execution, via a "<file type='file' name='../" substring.