← 返回列表

Cloud vulnerability teardown: what's important and what you can ignore

单站 Grounded Cloud Security 作者 Ethan Chen 发布 Fri, 14 Mar 2025 17:59:07 GMT 入库 2026-11-18T07:34:31

alt="" alt=""

TL;DR

Security flaws remain a primary entry point for attackers—creating significant frustration when breaches occur through long-patched vulnerabilities. Organizations often discover that exploited weaknesses had available fixes for extended periods, suggesting preventable incidents through faster patching cycles.

Yet expecting immediate remediation of every discovered vulnerability ignores practical realities. Today's sprawling IT landscapes make universal patching unfeasible, particularly in cloud platforms where configuration errors proliferate, infrastructure evolves rapidly, and comprehensive monitoring proves elusive.

Reality dictates that most vulnerabilities never face exploitation. Rather than pursuing impossible perfection through complete remediation, security teams must focus resources on high-risk exposures most likely to enable attacks.

We'll explore inherent challenges with cloud vulnerabilities and demonstrate how organizations can efficiently pinpoint and eliminate their most dangerous security gaps.

Vulnerability management is different in the cloud

In theory, vulnerability management (VM) is simple: Identify the security flaws or weaknesses in an organization’s software, and then work to reduce or eliminate the risks they pose. Traditional data center environments offered relative simplicity: applications existed behind defined perimeters, experienced minimal changes, and maintained limited external connections—enabling straightforward vulnerability management approaches.

Cloud computing disrupts these assumptions entirely. Modern enterprises embrace continuous deployment, microservices architectures, and distributed infrastructure. Established vulnerability scanning methodologies and tools prove inadequate for addressing the fluid, interconnected nature of cloud-native ecosystems. Security teams confront expanding attack surfaces while grappling with numerous operational challenges.

The challenge of ephemeral infrastructure

By design, cloud infrastructure changes constantly. Applications are deployed, updated, and moved. Resources including compute instances and storage volumes provision and terminate automatically based on demand. This perpetual evolution introduces vulnerabilities faster than conventional assessment methodologies can track, while complicating ongoing monitoring of identified security gaps.

Signs your VM practice is struggling in this more dynamic environment include:

Complex, multi-layered environments

Cloud environments encompass a stack of services, applications, and network layers across various cloud providers. Each has its own potential vulnerabilities. This can create numerous interdependencies across a broad landscape, making it hard to determine which vulnerabilities are most important. Teams spend too much time trying to understand the environment and can’t give enough attention to prioritization.

Complexity may be an issue for your VM team if you’re seeing:

Decentralized and multi-cloud environments

Organizations using multiple cloud providers or a hybrid environment will face inconsistencies as teams work across different platforms, each with individual sets of tools, security protocols, and configurations. Vendor-dependent patching adds to the problem, as many vulnerabilities in SaaS solutions can only be patched by the vendor, delaying remediation.

When teams lack an effective way to work across platforms, the problem often manifests as:

Cloud-native development implications

VM methods developed for traditional applications aren’t well adapted for the unique characteristics of cloud-native applications, including DevOps, containerization, and continuous integration and continuous delivery/deployment (CI/CD). The speed and complexity of modern development practices can leave dangerous gaps, letting vulnerabilities flow unchecked into production.

Cloud-native development may be posing problems for your team if you discover:

Some teams overlook these new risks, focusing solely on the more traditional vulnerabilities of monolithic apps and static infrastructure.

Ownership issues

VM in the cloud requires coordination among multiple groups. SecOps teams deploy vulnerability assessment tools and determine which vulnerabilities to prioritize. IT operations tests and remediates patches. Other groups—such as dedicated VM, risk management, internal audit, or line-of-business teams—may define their own policies and processes and make their own decisions about exceptions. All of this can blur ownership and responsibility. Without consistent or shared goals across teams, it’s hard to optimize VM.

The problem is exacerbated when a lack of proper controls lets anyone spin up their own cloud environment. This shadow IT can make it especially difficult to maintain a full survey of the environment with detailed ownership information.

Ownership issues may be undermining your VM practice if teams are experiencing:

Why vulnerability prioritization is critical — and difficult

The extreme volume and velocity of vulnerabilities in the typical hybrid, multi-cloud environment makes it neither feasible nor effective to aim for complete and timely mitigation. Beyond the massive staff this would require, it’s also inefficient to go after vulnerabilities that don’t pose a significant threat. Instead, organizations need to focus on effectively prioritizing the most important fixes. However, vulnerability prioritization can be a time-consuming and difficult task.

Traditional prioritization approaches rely on conventional risk scoring frameworks like the common vulnerability scoring system (CVSS). But the CVSS lacks the full context needed to make optimal decisions. As generic, one-size-fits-all ratings, CVSS scores aren’t aligned with the strategy, tactics, and operational objectives of a given business. And they’re not analyzed within the context of your business architecture (the systems, dependencies, and data stores powering specific services). Many vulnerabilities rated critical or high may have no significant relevance to your organization.

Similarly, the CVSS focuses on potential threats, not actual threat activity. Criteria such as the use of privileged credentials or remote execution can be good indicators of possible threats. But they don’t indicate how the vulnerability is actually being exploited in the wild, or whether a given asset or organization is a likely target. Prioritization must also consider multiple factors, including active threats, attack feasibility, and other customized security practices and controls.

In some cases, the CVSS can even be misleading about actual risk. Threat actors often target vulnerabilities rated “medium” and “low” as paths of least resistance, since potential victims may not give them the same level of scrutiny. In practice, this means a lower CVSS score can translate into a higher likelihood of exploitation. Also, the CVSS has a long backlog of unscored vulnerabilities. Just because a vulnerability hasn’t been labeled “critical” doesn’t mean it’s more or less likely to be exploited.

This lack of context isn’t limited to CVSS scores. Most common VM metrics (time-to-detection, vulnerability age, patching rate) aren’t risk-based, and often lead to ineffective, low-value prioritization with negative impacts and high costs. Neither velocity nor volume of vulnerabilities patched are accurate indicators of a VM program’s success.

This post was originally published on Expel's blog. Reach out personally or see resources below how Expel - the leading cloud MDR - can help:

原文链接:https://groundedcloudsecurity.substack.com/p/vulnerability-management-but-in-the