Vulnerability management finds and prioritizes exploitable weaknesses, reducing breach risk through timely patching, remediation, and verification.
Search across headline titles and summaries.
Background for this topic.
Vulnerability management is the ongoing process of finding, assessing, prioritizing, and addressing weaknesses in software, systems, cloud services, and devices. It helps defenders reduce the attack surface: an attacker may use a known flaw in an internet-facing service, endpoint, or dependency to gain access or increase privileges, but exposure depends on factors such as reachability, exploit availability, and existing controls.
Effective practice combines an accurate asset and software inventory with authenticated scanning, threat intelligence, and risk-based prioritization rather than treating every finding equally. Teams should patch or upgrade vulnerable components within defined timeframes, remove unnecessary exposure, or apply compensating controls such as isolation, access restrictions, and configuration changes when immediate remediation is impractical. Remediation must be verified through rescanning or other testing, with exceptions documented and reviewed; this also provides evidence for security governance and compliance. Vulnerability management supports incident response by identifying affected assets when a newly exploited flaw is disclosed.
For thirty years, vulnerability management ran on a buffer: the months between when a vulnerability was found and when someone could figure out how to weaponize it. The solution was straightforward enough; triage by severity, schedule the fix, validate, and move on. The buffer was what made that work