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:
- The Open Group has published an extensive standard,"Risk Taxonomy (O-RT), Version 2.0."
- Daniel Miessler has written an informative post, "The Difference Between Threats, Threat Actors, Vulnerabilities, and Risks."
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.
- Total open vulnerabilities
- Average vulnerability age
- Total vulnerabilities open longer than X days
- 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)
- 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.
- 10 Social Engineering Attacks Your End Users Need to Know About
- Security Training & Awareness: 3 Big Myths
- What's Next After HTTPS: A Fully Encrypted Web?
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.