Vulnerabilities & Risk

The Vulnerability Management Lifecycle

find, rank, fix, verify, repeat

2 min readupdated by Syed Khaleel Ahmed

Vulnerability management is the ongoing routine of finding weaknesses in your systems and fixing the ones that matter, before attackers use them. It is a cycle, not a project: new flaws are published every day.

The cycle

  1. Know what you have. You cannot protect what you do not know about. Keep an up-to-date inventory of devices, software, cloud resources and owners.
  2. Scan and discover. Run authenticated vulnerability scans, watch vendor advisories and track the components inside your software. Authenticated scans (with credentials) find far more than scans from outside.
  3. Validate. Scanners produce false positives, so confirm what is real and affects you.
  4. Prioritize. Use severity (CVSS), exploitation evidence (EPSS, the KEV catalog), exposure (is it internet-facing?) and business criticality.[2]
  5. Remediate. Patch, change configuration, or remove the software. Where you cannot fix quickly, mitigate with compensating controls such as isolating the system or blocking a port, and record the decision.
  6. Verify. Rescan to confirm the fix worked and did not break anything.
  7. Report and improve. Track how long fixes take and which teams are stuck.

Patch management is the heart of it

Patching sounds simple and is hard: systems cannot always restart, vendors release fixes at awkward times, and updates occasionally break things. Good programs test patches on a small group first, schedule regular maintenance windows, and have a faster emergency route for actively exploited flaws.[1]

Measures worth tracking

  • Mean time to remediate by severity.
  • Coverage: what percentage of assets is scanned.
  • Age of open findings, especially anything on the KEV list.
  • Exceptions: accepted risks should have an owner and an expiry date.

Common traps

Scanning without acting, counting findings instead of reducing risk, ignoring assets nobody owns, end-of-life software that no longer receives patches, and treating the scan report as the finish line.

Vulnerability assessment vs penetration test

An assessment broadly lists weaknesses, usually with scanners. A penetration test exploits chosen ones to show what an attacker could actually achieve. They answer different questions and complement each other.

Sources

  1. NIST SP 800-40 Rev. 4: Guide to Enterprise Patch Management Planning
  2. CISA: Known Exploited Vulnerabilities Catalog

Test yourself

My notes

Private — saved only on this device, never sent anywhere.