Vulnerability management is the continuous process of identifying, assessing, prioritizing, remediating, and monitoring security weaknesses across an organization's IT infrastructure, applications, and cloud environments. This discipline sits at the intersection of security operations, risk management, and compliance, serving as a critical defense against exploitation by threat actors. While traditional approaches relied on static CVE databases and basic CVSS scoring, modern vulnerability management now integrates real-world threat intelligence, exploitability predictions (EPSS), and contextual risk scoring to cut through the noise of 50,000+ CVEs published annually. The key mental model: not all vulnerabilities are equal—prioritization based on actual exploitability, asset criticality, and business impact determines success, not just patching everything with a high CVSS score.
What This Cheat Sheet Covers
This topic spans 15 focused tables and 108 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
Table 1: CVE and Vulnerability Databases
Every vulnerability program starts here—the canonical sources that tell you a weakness exists and how the world refers to it. NVD enriches each CVE with scores and references, the CVE program guarantees a single shared identifier, and CISA's KEV list cuts straight to what attackers are actually exploiting right now. Knowing which database carries which kind of authority is what keeps you from chasing noise.
| Database | Example | Description |
|---|---|---|
nvd.nist.gov/vuln/search | • U.S. government repository of CVE records enriched with CVSS scores, CWE mappings, and references • NIST prioritizes enrichment for critical and KEV-listed vulnerabilities as of April 2026. | |
CVE-2026-33952 | • Unique identifier assigned by CNAs to publicly disclosed vulnerabilities • format CVE-YEAR-NUMBER serves as universal reference across security tools | |
CVE-2026-32202 added to KEV | • Authoritative catalog of actively exploited vulnerabilities in the wild • federal agencies must remediate KEV entries within specified deadlines | |
VulDB-2026-123456 | • Independent vulnerability database documenting and explaining vulnerabilities since 1970 • includes threat intelligence and exploitability context |