Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Patch management is the structured process of identifying, prioritising, testing, and deploying software updates so that known vulnerabilities are fixed before attackers can exploit them.

What Is Patch Management?
Patch management is the process of identifying, acquiring, testing, and installing updates for operating systems, applications, firmware, and network devices. Patches fix bugs and add features, but from a security perspective their main job is to close known vulnerabilities before someone exploits them.
It sounds routine, yet unpatched software remains one of the most common causes of serious breaches. Attackers do not need a zero-day vulnerability when organisations leave well-known flaws open for months.
Two incidents from 2017 still illustrate the point. In March that year Microsoft released the MS17-010 update for a flaw in the SMBv1 protocol. Two months later the WannaCry ransomware used that same flaw to spread across around 150 countries, disrupting parts of the NHS. Also in March 2017, a patch was released for a critical Apache Struts vulnerability (CVE-2017-5638); Equifax had not applied it when attackers exploited the flaw from May onwards, exposing personal data of around 147 million people, including UK residents.
The window between disclosure and exploitation keeps shrinking. For widely used internet-facing products such as VPN gateways and file transfer tools, mass exploitation can start within days, sometimes hours, of a patch being published.
A mature process usually runs as a repeating cycle:
Large estates receive hundreds of updates every month, so deciding what comes first matters. CVSS severity scores are a useful starting point, but they describe technical severity, not real-world risk. Better prioritisation combines several factors:
In the UK, the Cyber Essentials scheme requires critical and high-risk security updates to be installed within 14 days of release, which is a sensible baseline for most organisations.
Patching is rarely as simple as clicking “update”. Typical obstacles include legacy systems that are no longer supported, business-critical applications that break after updates, limited maintenance windows, remote devices that rarely connect to the corporate network, and third-party libraries buried inside in-house software. Operational technology adds further constraints, since stopping an industrial process to patch it may be costly or unsafe.
Where a patch cannot be applied, compensating controls reduce the risk: isolating the system with network segmentation, disabling the vulnerable feature, adding hardening measures, or placing a web application firewall in front of an exposed service.
Patch management is one part of the wider discipline of vulnerability management, which also covers misconfigurations, weak credentials, and design flaws that no patch can fix. Measuring metrics such as mean time to patch and the percentage of critical vulnerabilities closed within target timescales shows whether the process is actually reducing risk.
Automation helps enormously. Endpoint management platforms can deploy operating system and browser updates on a schedule, while software composition analysis tools flag outdated libraries in your own code. Even so, someone needs to own the process end to end, with clear service levels agreed between security and IT operations and a documented route for approving exceptions.
At Privia Security, our Continuous Vulnerability Scanning Services show which missing patches matter most in your environment and confirm when they have been fixed.
The UK Cyber Essentials scheme requires critical and high-risk security updates to be applied within 14 days of release. For vulnerabilities that are actively exploited, particularly on internet-facing systems such as VPNs and firewalls, many organisations aim for 48 to 72 hours or apply emergency mitigations immediately while patches are tested.
Patch Tuesday is the informal name for Microsoft’s monthly security update release, which takes place on the second Tuesday of each month. Many other vendors, including Adobe and SAP, release updates on the same day. Organisations often plan their patching cycle around it, while staying ready to deploy out-of-band emergency fixes when necessary.
Testing reduces the risk of a patch breaking business applications, so it is good practice for servers and critical systems. However, testing must not become an excuse for long delays. A staged rollout, starting with a small pilot group and expanding quickly, balances stability with security, and emergency patches may justify a shorter testing window.
Unsupported or fragile systems should be isolated through network segmentation, have unnecessary services disabled, and be monitored closely for signs of compromise. Document the risk, agree who owns it, and plan a replacement. Virtual patching through an intrusion prevention system or web application firewall can provide temporary protection for exposed services.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.