Skip to content
StratQuad

Vulnerability management

2 min read

How to find, prioritise, fix and evidence vulnerabilities across an estate, using exploitation evidence rather than severity alone.

At a glance

Owner
StratQuad
Version
November 2026
Applies to
Any organisation running its own IT, cloud or operational technology
Mandatory
Guidance; specific timescales are required by Cyber Essentials, CAF profiles and many contracts

Key points

  • Vulnerability management is a cycle: know your assets, find vulnerabilities, prioritise, remediate or mitigate, verify, and report.
  • Prioritise by evidence of exploitation first (CISA KEV), likelihood second (EPSS), then severity (CVSS) and asset exposure and value.
  • Set remediation timescales by priority, write them down, and track exceptions with a named risk owner.
  • Cyber Essentials requires critical and high risk updates within 14 days of release on in scope devices.
  • Measure time to remediate exploited vulnerabilities on internet facing assets; it tracks the exposure attackers most often use.

The cycle

  • Asset inventory

    Every device, cloud service, application and internet facing service, with an owner and a criticality rating. Vulnerabilities on unknown assets are never fixed.

  • Discovery

    Authenticated scanning of servers and endpoints, external attack surface scanning, cloud configuration assessment, software composition analysis for in house code, and vendor advisories for appliances that scanners miss.

  • Prioritisation

    Combine exploitation evidence, likelihood, severity and asset context into a priority.

  • Remediation

    Patch, upgrade, reconfigure, or apply a vendor mitigation; remove what cannot be fixed.

  • Verification

    Rescan to confirm the fix, rather than trusting the change ticket.

  • Reporting

    Metrics for operations and a short summary of exposure and trend for the board.

Prioritising

PriorityCriteriaExample target
1In CISA KEV, or exploitation reported by the NCSC or a vendor, on an internet facing or critical assetDays, not weeks; treat as an incident
2In KEV on internal assets, or high EPSS on internet facing assetsWithin 14 days
3Critical or high CVSS without exploitation evidenceWithin 30 days
4Everything elseNormal patch cycle

Practitioner note

The table is a starting point, not a standard; set your own timescales against your risk appetite and contracts, and make sure they are no slower than Cyber Essentials' 14 days for critical and high updates if you hold or need that certification. Edge devices (VPNs, firewalls, file transfer appliances) deserve their own fast lane: they are among the most exploited asset classes and often sit outside normal patch tooling.

Exceptions

Where a fix cannot be applied in time, record the vulnerability, the reason, the compensating control (isolation, disabling the vulnerable feature, a web application firewall rule), the risk owner who accepts the residual risk, and a review date. Unsupported software should have a removal date, not an indefinite exception.

Metrics that matter

  • Mean and 90th percentile time to remediate, by priority.
  • Open KEV vulnerabilities on internet facing assets (target: zero).
  • Percentage of assets scanned in the last 30 days (coverage).
  • Number and age of open exceptions.

Evidence expected

Auditors and assessors typically ask for: the asset inventory and its coverage by scanning; the documented prioritisation method and timescales; a sample of vulnerabilities traced from detection to verified fix with dates; the exception register with risk owner sign off; and trend reporting to management.

Common mistakes

Common mistakes

  • Prioritising by CVSS alone, leaving teams overwhelmed by thousands of "criticals" while exploited flaws wait.
  • Scanning without credentials, which misses most missing patches on hosts.
  • Edge appliances excluded from the patch process because the scanner does not cover them.
  • Closing tickets on deployment rather than on verified remediation.
  • Exceptions without expiry, which become permanent accepted risk nobody reviews.

Sources

Suggest a correction