EVOPEDIA

← all systems · see it in The System

Vulnerability management

The cyclical practice of identifying, classifying, prioritising, remediating and mitigating software vulnerabilities across an organisation (src:wp:vulnerability-management); in the research literature, security patch management: identifying, acquiring, testing, installing and verifying security patches (src:dissanayake-2022-slr), framed by NIST as preventive maintenance for technology (src:nist-sp800-40r4). Walked as practitioners and researchers describe it: scanning and inventories, advisory and exploitation feeds, scoring and prioritisation (CVSS, EPSS, KEV, SSVC), the decision and coordination of patching, the programme's cycles, the people who do it, its economics and the measurements of how well it works.

Properties published scienceour proposal

Sourced fields, and our own readings.

born at1999-2003 (CVE public 1999; earliest studies 2002; Patch Tuesday 2003)
born precisionyear
boundaryInside: the programme's sensing (scanners, inventories, feeds), its findings and ranked queue, the decisions, tests, schedules and deployments of fixes and mitigations, the verification after, and the people and cycles that run it. Outside: the vulnerabilities themselves (their own system), vendors who write patches, attackers, the SOC and incident responders, regulators, and the rest of the organisation it serves.
nested levelA process inside an organisation's security function, next to the SOC and incident response; fed by the shared vulnerability record and vendors' patches.
scalesocial

Measures (29) published science

characteristic clock: patch cycle (Patch Tuesday, second Tuesday each month)1 month
characteristic clock: patch coordination meeting interval14 (about 1.5 hours each) days
standard patch window4 hours
standard phase time frames (retrieval, scan/assess, test, deploy, verify)2 days; 1 week; 1 week; 2 weeks; by next cycle time
delayed patching tasks (healthcare, four years)132 of 232 tasks
share of delays at deployment54 %
longest average delay per phase3.6 months
organisations unable to patch critical flaws within 72 hoursmore than 50 (about 15% unpatched after 30 days)
share of patch-management solutions rigorously evaluated in industry20.8 %
share of CVEs exploited in the wild within 12 months (2016-2018)3.7 (921 of 25,159) %
remediation efficiency of a CVSS 7+ rule6.2 (coverage 62.7) %
effort saved at equal coverage (EPSS vs CVSS 7+)60.7 (2,773 vs 1,091 fixes) %
median time to remediate (almost 300 companies)100 (75% within 392) days
known vulnerabilities exploited in the wildabout 5 %
EPSS v3 improvement over past models82 %
CVEs published per year25,059 (2022); 28,961 (2023); 29,004 (2024) CVEs
CVEs whose EPSS exceeded 50% before KEV listingfewer than 20 %
enterprise time to patch 90% of client hosts (average)over 6 (avg 67 days to 50%, 200 to 90%) months
Chrome enterprise patch time18 days to 50%; 78 days to 90%
server application vulnerability window (average)7.5 (over 9 months to patch 90%)
servers fixed one week after the OpenSSL announcement (2002)23 %
share of operators who patch immediatelyabout 35 (65 take no action) %
knees in bad-patch risk after release10 and 30 days
revised or pulled security patches (1999-2001)20 of 112 patches (136 CVE entries, 24 without a patch)
time to generate an exploit from a patcha few minutes
Heartbleed: increase in patching after notification47 (150,000 hosts) %
Heartbleed: vulnerable Top-1M HTTPS sites two months after disclosure3 (plateau after about two weeks) %
Microsoft updates, first quarter 2013over 300 updates
home users who misunderstood their update settings28 of 37 users

Open contentions (4) open contention

Where sources or readings disagree. Both stay on the map.

Partners and parts published science

Built from / builds (7)

Sits inside / holds (2)

Trades with (valence) (14)

expressed by (17)

floor filled by (11)

Kinds (6)

Notes published science

Layers

The ways it takes in its world, where they meet, and how it acts back, each from L1 (where it meets the world) up.

the boardroom (shared floors)

  1. L4: Assessment and prioritisation: findings ranked by severity (CVSS), exploitation (EPSS, KEV), weakness type (CWE) and asset context; the ranked queue
  2. L5: Decision and coordination: the risk response chosen (accept, mitigate, transfer, avoid), scheduled through change management, tested, approved; patch meetings across teams, customers and vendors
  3. L6: The programme: maintenance groups and plans, patch cycles (monthly, Patch Tuesday), standard time frames, metrics and policy
  4. L7: Purpose: preventive maintenance so the organisation's technology reliably serves its mission; a cost of doing business

vulnerability management as practitioners and researchers describe it: the organisation's assets and their flaws, up to the mission the maintenance keeps (reader's view)

  1. L1: The estate: the organisation's assets (computers, servers, applications, libraries, firmware) and the flaws in them
  2. L2: Sensing: scanners, inventories and SBOM tools, advisory feeds, exploitation data, fuzzing
  3. L3: Findings: known vulnerabilities matched to assets and versions; filtered and validated
  4. L4: Assessment and prioritisation: CVSS, EPSS, KEV, SSVC, asset context; the ranked queue
  5. L5: Decision and coordination: risk response, testing, scheduling, approvals, deployment
  6. L6: The programme: patch cycles, maintenance groups, time frames, policy and metrics
  7. L7: Purpose: preventive maintenance for the mission

way in: Advisories and patch releases from vendors and the shared record

  1. L1: Vulnerabilities disclosed and patches released by vendors (Patch Tuesday bulletins, the Security Update Guide), recorded as CVEs
  2. L2: Security advisories (78%), vendor notifications (71%), mailing lists, forums, news, blogs, social media
  3. L3: Filtering and validating against what the organisation runs: no central platform, hours spent monitoring sources

way in: Business context: asset criticality, downtime limits, approvals

  1. L1: Business units, customers (hospitals) and end users whose services depend on the assets
  2. L2: Their constraints arrive: approvals for patch windows, change freezes, minimum-interruption policies
  3. L3: Asset criticality and operational constraints as contextual metrics

way in: Exploitation evidence: who is attacking which flaws

  1. L1: Exploitation in the wild by attackers, and exploit code published (Exploit DB, Metasploit modules)
  2. L2: Sensors of security vendors (Proofpoint, Fortinet, AlienVault, GreyNoise) record exploitation attempts
  3. L3: Turned into scores and lists: EPSS probability of exploitation in 30 days, the CISA KEV catalogue

way in: Incidents and breaches through unpatched flaws

  1. L1: Attacks exploiting known, already patchable flaws (Equifax; WannaCry stopped 45 NHS hospital groups)
  2. L2: Alerts and investigations by the SOC and incident responders
  3. L3: Out-of-band and emergency patching scenarios triggered

way in: Inventory: what software runs where, down to packages and libraries

  1. L1: The organisation's applications, operating systems, firmware and their packages and libraries
  2. L2: Asset inventory systems and SCA/SBOM tools for third-party components
  3. L3: Versions matched to known vulnerabilities; re-bundled open-source code hides in other dependencies; inventories are often incomplete

way in: Looking for unknown flaws: fuzzing, static analysis, testing

  1. L1: The organisation's own and third-party programs, with flaws nobody has reported
  2. L2: Fuzzers (AFL, libFuzzer) feed random or semi-random inputs; static analysis and symbolic execution read code without running it
  3. L3: Crashes and warnings triaged into candidate vulnerabilities

way in: Mandates: standards, regulators, auditors

  1. L1: Payment-card standard and federal directives that set CVSS thresholds and deadlines
  2. L2: PCI-DSS requires flaws above CVSS 4.0 remediated; DHS BOD 19-02 requires high and critical flaws remediated
  3. L3: Legal and regulatory requirements as motivators to patch

way in: Notifications from outsiders who scanned you

  1. L1: Researchers scan the whole IPv4 space for vulnerable hosts
  2. L2: Operators contacted by email through abuse contacts
  3. L3: Notified operators patch more (a 47% increase)

way in: Own patch state after deployment

  1. L1: Assets after deployment: patched, failed, or rolled back
  2. L2: Confirming the patch is installed and has taken effect
  3. L3: An overview of the patch state; often missing and manual
  4. L4: Continuous monitoring that no one undoes the response

way in: Patch quality and vendor support

  1. L1: Vendors' patches, some faulty: 20 of 112 patches revised or pulled in 1999-2001
  2. L2: Announcements that a patch was bad; vendor support tickets
  3. L3: Patches tested in a test environment before production; manual, slow and hard to make identical to production

way in: Scanning the estate: hosts, ports, services and installed software

  1. L1: The organisation's computers, servers and network devices, with open ports, services and configurations
  2. L2: Vulnerability scanners probe them: authenticated scans log in over SSH or RDP for low-level detail; unauthenticated scans look from outside
  3. L3: Findings: known vulnerabilities, misconfigurations and missing security patches per asset; unauthenticated scans give many false positives

way in: The team's own state: workload, expertise, fatigue

  1. L1: Administrators, security engineers, change managers
  2. L2: Overload, leave, missing expertise hold tasks; 67% feel they lack time to mitigate all vulnerabilities
  3. L3: Coordination load: delays in coordinating patch work are the top cause of delay
  4. L4: Burnout across the industry

way out: Avoid: uninstall, decommission, replace

  1. L1: The vulnerable attack surface gone
  2. L2: Software uninstalled, asset decommissioned or replaced (e.g. end-of-life Windows XP)
  3. L5: Avoidance chosen

way out: Mitigate without patching: controls and reconfiguration

  1. L1: The attack surface around the asset reduced
  2. L3: Disable the vulnerable feature, change network policy, segment, firewall
  3. L5: Mitigation chosen when no patch is viable

way out: Patch: install the fix

  1. L1: The flaw removed from the asset without removing function
  2. L2: Distributed and installed, automatically or by hand, often with reboots
  3. L3: Acquired, authenticity validated, tested
  4. L4: Assigned to maintenance groups and patch windows (usually 4 hours)
  5. L5: Patch prioritised and scheduled through change management

way out: Reports and compliance evidence

  1. L1: Leadership and customers informed
  2. L6: Patch status and progress reported in patch meetings and to management; compliance kept up

way out: Transfer: insurance or SaaS

  1. L1: Cyber insurance bought, or SaaS adopted so the provider patches
  2. L5: Transfer chosen

way out: Vulnerability context handed to the SOC and incident responders

  1. L1: Responders know which assets are exposed
  2. L4: Asset and vulnerability lists shared (SIEM/SOAR integration)

Sources (26) published science

Vulnerability management (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01)
Rescorla E. Security holes... who cares? 12th USENIX Security Symposium, 2003 (behind its links)
Dissanayake N, Jayatilaka A, Zahedi M, Babar MA. Software security patch management: a systematic literature review of challenges, approaches, tools and practices. Information and Software Technology 2022 (arXiv:2012.00544) (behind its links)
Brumley D, Poosankam P, Song D, Zheng J. Automatic patch-based exploit generation is possible: techniques and implications. IEEE S&P 2008 (doi:10.1109/SP.2008.17) (behind its links)
Jacobs J, Romanosky S, Suciu O, Edwards B, Sarabi A. Enhancing vulnerability prioritization: data-driven exploit predictions with community-driven insights. arXiv:2302.14172 (IEEE EuroS&PW 2023) (behind its links)
Dissanayake N, Zahedi M, Jayatilaka A, Babar MA. Why, how and where of delays in software security patch management: an empirical investigation in the healthcare sector. Proc. ACM HCI 6(CSCW2) 362, 2022 (doi:10.1145/3555087; arXiv:2202.09016) (behind its links)
Nurse JRC. To patch or not to patch: motivations, challenges, and implications for cybersecurity. arXiv:2502.17703 (2025) (behind its links)
Li F, Rogers L, Mathur A, Malkin N, Chetty M. Keepers of the machines: examining how system administrators manage software updates. SOUPS 2019 (behind its links)
Koscinski V, Nelson M, Okutan A, Falso R, Mirakhorli M. Conflicting scores, confusing signals: an empirical study of vulnerability scoring systems. ACM CCS 2025 (arXiv:2508.13644) (behind its links)
Patch (computing) (Wikipedia, via Wikimedia Enterprise snapshot) (behind its links)
Vulnerability scanner (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Souppaya M, Scarfone K. Guide to enterprise patch management planning: preventive maintenance for technology. NIST SP 800-40 Rev. 4, 2022 (doi:10.6028/NIST.SP.800-40r4) (behind its links)
Jacobs J, Romanosky S, Edwards B, Roytman M, Adjerid I. Exploit Prediction Scoring System (EPSS). arXiv:1908.04856 (behind its links)
Wash R, Rader E, Vaniea K, Rizor M. Out of the loop: how automated software updates cause unintended security consequences. SOUPS 2014 (behind its links)
Patch Tuesday (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Dissanayake N, Zahedi M, Jayatilaka A, Babar MA. A grounded theory of the role of coordination in software security patch management. ESEC/FSE 2021 (arXiv:2106.03458) (behind its links)
Kotzias P, Bilge L, Vervier P-A, Caballero J. Mind your own business: a longitudinal study of threats and vulnerabilities in enterprises. NDSS 2019 (doi:10.14722/ndss.2019.23522) (behind its links)
Beattie S, Arnold S, Cowan C, Wagle P, Wright C, Shostack A. Timing the application of security patches for optimal uptime. LISA 2002, pp. 233-242 (behind its links)
Durumeric et al., The Matter of Heartbleed, ACM Internet Measurement Conference 2014 (doi:10.1145/2663716.2663755) (behind its links)
Jiang Y, Oo N, Meng Q, Lim HW, Sikdar B. A survey on vulnerability prioritization: taxonomy, metrics, and research challenges. arXiv:2502.11070 (behind its links)
Risk management (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Penetration test (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Common Vulnerability Scoring System (Wikipedia, via Wikimedia Enterprise snapshot) (behind its links)
Common Vulnerabilities and Exposures (Wikipedia, via Wikimedia Enterprise snapshot) (behind its links)
Newgard CD et al. National guideline for the field triage of injured patients: recommendations of the National Expert Panel on Field Triage, 2021. J Trauma Acute Care Surg 2022 (PMC9323557) (behind its links)
Rastogi RP, Richa, Kumar A, Tyagi MB, Sinha RP. Molecular mechanisms of ultraviolet radiation-induced DNA damage and repair. J Nucleic Acids 2010:592980 (PMC3010660, CC BY 3.0) (behind its links)