Guide Vulnerability Management Cybersecurity

Vulnerability and Patch Management: A Practical Guide for UK Organisations

Software vulnerabilities are now the most common way attackers get in. Most organisations patch, but few can say how long a critical fix actually takes to reach every device, or which exposed system they would fix first.

20 October 2026
Updated 19 November 2026
8 min read
Key takeaways
  • 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.

31%
of breaches analysed in the study started with an exploited software vulnerability, overtaking stolen credentials as the top way in within that sample (Verizon 2026)
40%
of the vulnerabilities exploited by China-nexus actors targeted internet-facing edge devices (CrowdStrike 2026)
14 days
maximum time to apply critical and high-risk security updates under Cyber Essentials

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.

1
Know what you have
Build and maintain an inventory of hardware, software, cloud services and internet-facing assets, with a named owner and a business criticality rating for each. Include the things that are easy to miss: network appliances, printers, building management systems, test environments, SaaS applications and anything a supplier manages for you. Record which software versions are in use and when vendor support ends. If you do not know an asset exists, you cannot confirm it is patched.
2
Find vulnerabilities
Use several sources, because no single one sees everything. Authenticated vulnerability scanning of internal systems, external scanning of your internet-facing attack surface, endpoint agents that report missing updates, and cloud security posture tools for misconfigurations. Subscribe to vendor security advisories for your critical products. UK organisations can also register for the free NCSC Early Warning service, which alerts you to vulnerable or exposed services and signs of compromise on your networks. Penetration testing adds a periodic, human-led check on top of automated scanning. If you build or deploy your own software, add dependency scanning, container image scanning and application security testing, because infrastructure scans do not see those layers. For systems a supplier runs, agree how they will tell you about vulnerabilities and fixes, and keep evidence of it.
3
Prioritise
A typical scan produces thousands of findings. Rank them by how likely they are to be exploited and how much damage exploitation would do, using the factors in the next section. The output is a short list of what must be fixed now, and a schedule for the rest.
4
Remediate or mitigate
Apply the update, change the configuration, or remove the software. Where no fix exists yet, apply the vendor’s workaround or a compensating control. Agree maintenance windows in advance, so that urgent fixes do not wait for a change board meeting. Test critical updates on a small group first, but keep the test period short and defined.
5
Verify
Rescan to confirm the vulnerability is closed. Patch deployment tools report what they attempted, not always what succeeded. Devices that were offline, failed reboots and updates that need a manual step are common reasons a “deployed” patch is still missing weeks later.
6
Report and improve
Track performance against your remediation targets, report it to leadership, and review the exceptions. Look for patterns: the same team always late, the same application always unpatched, the same asset class missing from scans. Fix the process, not only the individual finding.

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.

🚨
Known exploitation
The CISA KEV catalogue lists vulnerabilities with confirmed exploitation in the wild. It is free, updated regularly and widely supported by scanning tools. Anything on KEV that affects your environment goes to the top of the list for urgent assessment. Vendor advisories that mention active exploitation count the same way. KEV is not exhaustive, so a vulnerability missing from it can still be urgent.
📈
Likelihood of exploitation
The Exploit Prediction Scoring System (EPSS) from FIRST estimates the probability that a vulnerability will be exploited in the next 30 days. It helps separate the small share of vulnerabilities that attackers actually use from the large number they ignore. Use it to rank findings that are not yet on KEV. It estimates likelihood only and says nothing about the impact if a particular system is compromised, so weigh it alongside exposure and criticality.
🌐
Exposure
An internet-facing system is potentially reachable by anyone on the internet; whether a flaw is actually exploitable depends on configuration, authentication and the controls around it. An internal server behind several layers of control can usually only be reached by someone already inside. Firewalls, VPN gateways, remote access tools, email gateways and public web applications deserve the fastest response.
🏢
Asset criticality
Use the criticality rating from your inventory. A vulnerability on a domain controller, an identity provider, a backup server or a system that holds personal data has a larger blast radius than the same flaw on a kiosk PC. Your risk assessment should already tell you which systems these are.

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 Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

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

Common questions

What is the difference between vulnerability management and patch management?

Patch management is the process of testing and deploying vendor updates. Vulnerability management is the wider programme that finds weaknesses across your environment, decides which ones matter, fixes or mitigates them within a set time and verifies the result. It covers misconfigurations, exposed services, default credentials and unsupported software as well as missing patches. Patch management is one of the main tools vulnerability management uses, but it does not tell you what you have missed.

How often should we run vulnerability scans?

As a starting point, scan internet-facing systems continuously or at least weekly, and internal systems at least monthly. Rescan after every significant change and after remediation to confirm the fix. Endpoint agents that report missing updates in near real time reduce the dependence on scheduled scans. The right frequency also depends on how quickly you can act on the results: weekly scans add little if remediation only happens once a quarter.

Is CVSS enough to decide what to patch first?

No. CVSS measures technical severity, not the likelihood of exploitation or the importance of the affected system. Combine it with known exploitation (the CISA KEV catalogue and vendor advisories), the probability of exploitation (EPSS), whether the system is reachable from the internet, and how critical the system is to your business. That combination puts the small number of vulnerabilities attackers are actually using at the top of the list.

Cybersecurity Assessment

Find out which vulnerabilities matter before an attacker does

Our assessment reviews your asset visibility, patching performance and exposure alongside four other security domains. You leave with a prioritised roadmap.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.