Vulnerabilities / Threats

10/31/2017
10:30 AM
Ed Bellis
Ed Bellis
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Stop Counting Vulnerabilities & Start Measuring Risk

When security teams report on real risk, executive teams can gain a much better understanding of the company's security posture.

As a security team, you are what you measure. The problem is that too many security teams are counting vulnerabilities, not measuring risk. It's time we examine how vital it is for security teams to establish risk-based metrics, while offering some examples of both the right and wrong measures to use.

Why is the distinction between these approaches so vital? It's essential for security teams to understand the spectrum of risk, based both on the likelihood of an incident and the potential damage that may result.

Fundamentally, risk measurement provides a way for security teams to work smarter. They can focus their time, budget, and resources on what matters most: reducing risk. Risk measurement also provides teams with a centralized way to accumulate, analyze, and report on risk, which helps significantly improve operational efficiency.

When you adopt a risk management approach, you focus on what poses the largest and likeliest effects on the business, effectively tracking and making progress toward the ultimate goal: reducing uncertainty. Contrast this with measuring the quantity of vulnerabilities, where metrics are focused on measuring work rather than outcomes.

Before we can discuss risk, let's establish definitions. Rather than starting from scratch, I'd suggest you take a look at these from the Open Group and Daniel Miessler:

It's often easiest to think of risk as uncertainty, and our job as security professionals is to remove as much uncertainty as we can.

The Problem: Security Can't Go It Alone
The security team has started taking a risk management approach and everything is going to be rosy, right? Not exactly. Once a security team embraces risk management, the hard work is just beginning. The rest of the organization needs to start following the team's example. How does security build support for risk management across teams?

For security teams and the business to succeed in reducing uncertainty, risk management must be incorporated into operations across the organization. When security starts to be part of operations — rather than an ad hoc afterthought— the critical efforts that need to happen, do happen.

To begin, focus on two key steps:

  • Measurement. Practitioners must make sure they're measuring actual risk. All key stakeholders should buy off on what is being measured and ensure actual risk reduction is being addressed.
  • Integration. Once you're reporting on risk, it's critical to make sure risk management is part of operations.

Step 1: Selecting the Right Metrics for Measuring Risk
I meet with practitioners from a wide range of industries and often see the same missteps. Chief among these is that security teams are measuring the wrong things.

More often than not, teams take a "best practices" approach. Security analysts may run a report and find their checklist of vulnerabilities has been unaddressed for longer than 90 days. Then they'll prioritize efforts based on this aging data, focusing on how long a vulnerability has existed. Likewise, I often see companies focusing on the security news of the day over items that may be less attention-getting but pose a greater risk.

Contrast these somewhat arbitrary approaches with a risk-based strategy. With a risk-based approach, you may realize that those older vulnerabilities don't pose as much risk, but that three vulnerabilities discovered yesterday pose both a great likelihood of resulting in an incident and significant potential damage to the business. With this insight, the need to remediate these three vulnerabilities sooner is clear.

When you focus on the quantity or aging of vulnerabilities, you deprioritize higher-risk items that have a high likelihood or impact.

These contrasting scenarios underscore the importance of tracking and reporting with the right metrics. Metrics are vital in guiding behavior and play a key role in measuring success, tracking progress, getting buy-in, and investing in new approaches

It can be far better to address one high-risk vulnerability than even 100 low-risk vulnerabilities. The key is to establish metrics and analytics that measure risk in an empirical, meaningful way, so you can make these calculations with clarity.

While specific metrics that are optimal will vary somewhat depending on the nature of the business and environment, there are some common do's and don'ts when it comes to choosing metrics.

Here are some metrics to avoid:

  • Total open vulnerabilities
  • Average vulnerability age
  • Total vulnerabilities open longer than X days

Organizations that use a risk-based approach can consider tracking a number of key metrics:

  • Remediation rate of high-risk vulnerabilities with breakdowns
  • Median time to remediate a high-risk vulnerability
  • Median time to discover a high-risk vulnerability
  • Number of high-risk assets (which is very different than tracking high-risk vulnerabilities)

By and large, if you're tracking these metrics and seeing progress, you are making real improvements in reducing risk.

Step 2: Integrate Risk Management into Operation Processes
When it comes to operationalizing risk management, don't start by trying to create new operational processes. Instead, focus on transparently integrating risk management into existing processes.

Too often, security teams create out-of-band tools and procedures — and results suffer. Under any circumstances, it will be challenging to get teams to focus on security activities. Creating unique tools and workflows significantly exacerbates this challenge.

To significantly enhance your odds of success, leverage existing teams' processes wherever possible. Look to bake risk management into existing tools and workflows that staff members are using every day, including bug tracking and incident management. In effect, you're starting with what everyone is doing today and applying a risk-based lens to it.

The Payoff of Operationalizing Risk Management
When security teams adopt risk management, good things start to happen for these groups:

  • Security staffers start measuring real risk and understand how best to reduce uncertainty.
  • Those in IT operations become more productive. They aren't stuck feeling like they're doing busywork for the security folks; rather, they get visibility into risks facing the business and how they can play a part in reducing them.

When security teams start tracking and reporting on real risk, executive teams can gain a much better understanding of the company's security posture, how it's changing, and, most importantly, which efforts and investments need to be made to improve it.  

Related Content:

Join Dark Reading LIVE for two days of practical cyber defense discussions. Learn from the industry’s most knowledgeable IT security experts. Check out the INsecurity agenda here.

 

Ed Bellis is a security industry veteran and expert and was once named Information Security Executive of the Year. He founded Kenna Security to deliver a data-driven, risk-based approach to remediation and help IT teams prioritize and thwart would-be security threats. Ed is ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Australian Teen Hacked Apple Network
Dark Reading Staff 8/17/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-15504
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. The server mishandles some HTTP request fields associated with time, which results in a NULL pointer dereference, as demonstrated by If-Modified-Since or If-Unmodified-Since with a month greater than 11.
CVE-2018-15505
PUBLISHED: 2018-08-18
An issue was discovered in Embedthis GoAhead before 4.0.1 and Appweb before 7.0.2. An HTTP POST request with a specially crafted "Host" header field may cause a NULL pointer dereference and thus cause a denial of service, as demonstrated by the lack of a trailing ']' character in an IPv6 a...
CVE-2018-15492
PUBLISHED: 2018-08-18
A vulnerability in the lservnt.exe component of Sentinel License Manager version 8.5.3.35 (fixed in 8.5.3.2403) causes UDP amplification.
CVE-2018-15494
PUBLISHED: 2018-08-18
In Dojo Toolkit before 1.14, there is unescaped string injection in dojox/Grid/DataGrid.
CVE-2018-15495
PUBLISHED: 2018-08-18
/filemanager/upload.php in Responsive FileManager before 9.13.3 allows Directory Traversal and SSRF because the url parameter is used directly in a curl_exec call, as demonstrated by a file:///etc/passwd value.