web analytics

Why CVSS is failing us and what we can do about it – Source: go.theregister.com

Rate this post

Source: go.theregister.com – Author: Sıla Özeren, Security Research Engineer, Picus Security

Partner content Two decades ago, CVSS revolutionized vulnerability management, enabling security teams to speak a common language when measuring and prioritizing risks posed by the vulnerability to the affected asset. However, today, the same tool that once guided us in the right direction is holding us back.

In an environment where adversaries are faster, attack surfaces are broader, and resource constraints are tighter than ever, relying only on CVSS ratings to drive remediation efforts is no longer enough. Yet many organizations still patch vulnerabilities based on severity scores alone without asking the critical question necessary to determine real risk: Does this exposure actually pose a real risk in our environment?

Legacy severity scores tell us what could happen in a vacuum, not what would happen in a context of live, defended infrastructure. Adversarial exposure validation seeks to cross this bridge between theoretical risk and real-world exposure.

Legacy severity scoring systems are useful tools but not the final answer

CVSS scores introduced risk assessment that was more about standardization than anything else. The intention was for security professionals in the vulnerability domain to use the same notational system to refer to the same phenomenon. However, CVSS scores are broad generalizations that don’t take vital variables into account. These include compensating controls (e.g., firewalls, segmentation, endpoint protection), the attack paths an adversary would traverse by successfully chaining together multiple exploits, and finally, the importance of the business context and assets.

A vulnerability designated as critical might be found on a non-sensitive server, seated behind layers of defensive technology. In contrast, a medium-level misconfiguration that’s on an asset exposed to the internet could be the opening move in an impactful compromise. By ignoring this context, CVSS leads teams down a misguided path.

Misplaced priorities happen when risk rankings mislead

The sole reliance on CVSS leads to three dangerous outcomes. First, it causes teams to waste valuable time patching exposures that pose little or no real risk, such as vulnerabilities that are unlikely to be exploited or are already mitigated by existing security controls.

The second is a non-deliberate lack of attention to critical attack paths. This is another misguided practice stemming from a lack of insight. Teams often overlook subtle, highly exploitable exposures because they don’t come with a “critical” label.

The final one is something your security team is probably facing right now: vulnerability overload. Security teams find themselves trapped in a never-ending cycle of vulnerability scanning, patching and score chasing. When they look up, adversaries are already ahead of them and moving faster than remediation cycles can cope with.

Hence, security leaders must ask: Are we remedying what is truly significant, or are we diverting our attention to problems that appear urgent on paper (i.e. compliance box ticking?)

The shift to adversarial exposure validation

Adversarial Exposure Validation (AEV) marks a fundamental shift in how organizations prioritize and address vulnerabilities, such as those traditionally managed through vulnerability management programs.

AEV doesn’t assign equal importance to each vulnerability based on a static number. Instead, it runs simulations of real-world attack techniques and scenarios in an organization’s unique environment. It asks if this exposure can actually be exploited right now. What would the impact be if it were? Does this exposure contribute to an attack path toward critical assets?

When security teams validate the identified exposure to see if they can be exploited in the real world, they focus on the significant, small number of exposures that matter. In other words, they are not just theorizing about the exploitability of vulnerabilities.

By doing so, AEV supplies what CVSS is unable to: proof with business context.

How exposure validation changes the game

Organizations that embrace exposure validation see instant rewards. The first is sharper and clearer prioritization, enabling remediation efforts to focus on exposures with real attack potential instead of chasing vulnerabilities based on abstract severity scores. This leads to efficiency gains, in which security teams spend less time patching a pool of noise and faux issues and more time fixing real, exploitable weaknesses.

Exposure validation also improves communication throughout the organization, allowing CISOs to report risk in a much more straightforward, more understandable way based on validated attack scenarios rather than those pesky theoretical scoring models.

Beyond improved communication, exposure validation also drives smarter security control testing. It continuously highlights which security controls perform as intended and which ones are ineffective or simply need adjustment. This approach aligns with the reality that trying to fix every vulnerability is a losing proposition. Instead, organizations validate, prioritize, and act with precision.

From static prediction to dynamic proof

CVSS will always have a place in cybersecurity. It offers a quick reference point and helps with initial triage. But in a world where attackers adapt faster than risk models, prediction alone is not enough.

Organizations need proof. They need real-world validation of exposures, informed by how adversaries actually operate, and grounded in the realities of their unique infrastructures.

Exposure validation doesn’t discard risk scores: it challenges them, augments them, and transforms them into a dynamic decision-making tool. By continuously validating exposures against real attack behaviors, organizations move from making assumptions about their security posture to proving it every day.

This shift has a profound impact on how security operations function. Instead of reacting to a flood of theoretical vulnerabilities, teams can act with clarity and precision. Instead of treating all risks as equal, they can focus their efforts on the few exposures that truly endanger critical assets. And instead of relying solely on periodic assessments, they can establish a state of sustainable readiness, where validation is continuous, automated, and deeply integrated into daily workflows.

Proof, not prediction. Context, not theory. Focus, not noise. This is the evolution that modern cybersecurity demands, and exposure validation makes possible.

The future is evidence-based security

The challenges security teams face today are not only about the volume of vulnerabilities but about the need to adapt faster than adversaries. Attackers are creative, determined, and opportunistic. Thus, they don’t wait for patch cycles or annual audits. To outpace them, defenders must anchor their strategies in continuous, real-world validation.

AEV empowers organizations to prioritize with evidence, remediate with confidence, and align resources to where they will have the greatest impact. It elevates cybersecurity from reactive defense to proactive resilience.

Risk scores will remain part of the ecosystem, but organizations that succeed in the future will be those that supplement prediction with proof, looking beyond CVSS and into the actual conditions shaping their risk at every moment.

The move from CVSS-based risk scoring to dynamic exposure validation is not just a technical upgrade; it’s a strategic imperative.

If you want to learn more about how AEV helps prioritize security efforts, check out our white paper: Introduction to Adversarial Exposure Validation.

Contributed by Picus Security

Original Post URL: https://go.theregister.com/feed/www.theregister.com/2025/05/14/picus_cvss/

Category & Tags: –

Views: 2

LinkedIn
Twitter
Facebook
WhatsApp
Email

advisor pick´S post