- In the Verizon 2026 Data Breach Investigations Report sample, exploited software vulnerabilities started more breaches than stolen credentials: 31% of the breaches the study analysed.
- You cannot patch what you do not know you have. An accurate asset inventory with a named owner for each system comes before any scanning tool.
- Prioritise by real-world risk, not CVSS score alone. A vulnerability on the CISA Known Exploited Vulnerabilities catalogue on an internet-facing device outranks a higher-scoring issue on an isolated internal server.
- Cyber Essentials requires security updates that the vendor rates critical or high, or that fix a vulnerability with a CVSS v3 score of 7 or above, to be applied within 14 days of release. Under the Danzell question set used from 27 April 2026, missing that deadline on operating systems, firmware or applications is an automatic fail.
- When you cannot patch, mitigate, record the risk and set an expiry date. The NCSC is clear that deciding not to apply an update is a senior-level risk decision.
What vulnerability management covers
Patch management is the process of getting vendor updates onto your systems. Vulnerability management is wider. It covers finding weaknesses across everything you run, deciding which ones matter most, fixing or mitigating them within a set time, and proving that the fix worked. Missing patches are one type of vulnerability. Misconfigurations, default credentials, exposed management interfaces and unsupported software are others, and a patching tool will not find them.
Treat it as a continuous operational process with owners, targets and reporting, not a monthly IT task. The NCSC’s vulnerability management guidance sets the baseline: apply updates as soon as possible and ideally automatically, keep an inventory of your assets and who owns them, and have a specific process for vulnerabilities that attackers are already exploiting.
Why the window is shrinking
Attackers are exploiting vulnerabilities faster than many organisations fix them. The Verizon 2026 DBIR found that organisations fully remediated only 26% of the vulnerabilities on the CISA Known Exploited Vulnerabilities (KEV) catalogue, down from 38% the year before. The median time to fully patch rose from 32 to 43 days. Those are vulnerabilities with confirmed, active exploitation, and most stayed open for weeks.
At the same time, CrowdStrike’s 2026 Global Threat Report reported growth in zero-day vulnerabilities exploited before public disclosure, and found that 40% of the vulnerabilities exploited by China-nexus actors targeted internet-facing edge devices such as firewalls, VPNs and remote access gateways. AI is also speeding up vulnerability research on the attacking side, as our article on AI and incident response explains. A monthly patch cycle that takes six weeks to reach the last device leaves a long gap.
Faster patching only solves part of this. You also need to know where your exposure is, so that the vulnerabilities that matter get fixed first and the rest follow a predictable schedule.
The vulnerability management lifecycle
Most mature programmes follow the same six steps. Each one depends on the one before it, and gaps in the early steps undermine everything that follows.
Prioritising beyond CVSS
The Common Vulnerability Scoring System (CVSS) rates the technical severity of a vulnerability. It does not tell you whether anyone is exploiting it, or whether the affected system matters to your business. Sorting by CVSS alone sends teams chasing high scores on isolated systems while an actively exploited flaw on the VPN waits. Combine four signals.
Prioritisation tells you what to fix first. Our companion guide, Vulnerability remediation: patch deadlines, exceptions and what the frameworks require, turns it into commitments: remediation targets by tier, a separate process for edge devices, what to do when you cannot patch, what Cyber Essentials, ISO 27001 and the NIS Regulations expect, and the metrics to report to the board.
Common mistakes
Scanning without an inventory. A scanner only checks what it is pointed at. Without an inventory to compare against, you cannot tell which assets it missed, and the missed ones are usually the least maintained.
Treating every high CVSS score as urgent. When everything is urgent, nothing is. Teams burn out working through thousands of findings in score order while the few that attackers are using wait their turn.
Forgetting firmware and third-party applications. Operating system updates are usually automated. Browser plugins, PDF readers, developer tools, network appliance firmware and line-of-business applications often are not, and they are where the gaps tend to sit. Endpoint management tools and Microsoft 365 and Intune policies can close much of this.
Trusting deployment reports. A patch marked as deployed is not a patch confirmed installed. Verify with a rescan.
Exceptions that never expire. Every accepted risk needs an owner, a review date and compensating controls. Otherwise the exception list quietly becomes the list of systems an attacker should try first.
Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile