Skip to main content
Open menu
Resources & insights

Patching Isn’t Enough – Why Vulnerability Management Matters

 

Regular patching doesn’t automatically mean you’re secure. Effective vulnerability management is the ongoing discipline of identifying weaknesses across your IT estate, prioritising the risks that matter, fixing them and proving that remediation has taken place. It isn’t a product or a one-off exercise. It’s a continuous process, and that’s the part many organisations underestimate.

Why vulnerability management has moved up the agenda – and why it is now proportionate for smaller firms

Two things have changed. The volume of newly disclosed software vulnerabilities has climbed year on year with no sign of levelling off, and the time between a weakness becoming public and attackers actively exploiting it has shortened dramatically – from months, to weeks, to a matter of days for internet-facing systems.

That has quietly redrawn the line on what counts as proportionate. A decade ago, a structured vulnerability management programme was the preserve of large institutions with in-house security teams; for a thirty-person PE firm it would have looked like overkill, and reasonably so.

That no longer holds. Attackers now sweep the internet automatically for known weaknesses, then decide who is worth their attention – and a small firm holding deal data, investor information and client money is an attractive answer. Meanwhile the cost of doing this properly has fallen sharply, from a dedicated internal function to a managed service that fits within a small firm’s IT budget. The risk has risen, the cost has fallen, while investor and insurer expectations have hardened. What was once a large-firm discipline is now part of running a credible one.

What a vulnerability management service actually covers

A credible service runs a repeating cycle rather than a one-off exercise:

  • Assessment – scanning your environment regularly for known weaknesses and misconfigurations
  • Prioritisation – deciding which findings carry genuine business risk to your firm
  • Remediation – applying the fix, or a mitigation where no fix yet exists
  • Reporting – evidencing what was found, what was resolved, how quickly, and what risk remains

Take any step away and the cycle stops working. Discovery without remediation produces a list. Remediation without reporting leaves you unable to demonstrate the work to anyone who asks.

Vulnerability management vs patching – why they are not the same thing

This is the most common objection, and a fair one: isn’t this just patching under a grander name? No – patching is one possible remedy within vulnerability management, not the whole of it.

Patching applies vendor updates to software. Vulnerability management asks a broader question: where is this firm exposed, and does it matter? Plenty of serious exposure has no patch at all – a misconfigured network device, an over-permissioned administrator account, an internet-facing service nobody remembers commissioning, or software the vendor no longer supports. No amount of patching resolves any of those.

“We already have a patching service” – what that does and does not cover

Most firms of this size have an IT partner applying updates, and that’s a genuine control worth having. But a patching service typically covers a defined list of devices and applications it already knows about, on a schedule, using vendor-supplied updates.

The questions it usually can’t answer are the ones that matter most: what’s on our estate that isn’t being patched at all? Which of our exposures would an attacker reach first? And can we show, with dates, how quickly the serious ones were closed?

Finding weaknesses is not the same as fixing them

The scanning technology is now commoditised and inexpensive. What’s genuinely difficult is what follows – reading several thousand findings and determining which handful demand attention this week.

A scanner has no idea what your business does. It will flag an issue on an isolated test machine with the same urgency as one on the system your finance team uses to authorise payments. Prioritisation is where a raw technical output becomes a decision a COO can act on – and it’s the step cheaper offerings tend to leave with the client.

Why continuous vulnerability management beats a periodic check

Most firms already carry out some form of periodic assessment – an annual penetration test or recertifying against Cyber Essentials. Both are worthwhile, and both are often contractually required. But they share a limitation: they tell you the state of your security on the day they were run, and no more.

A penetration test completed in March says nothing about the vulnerability disclosed in June. A Cyber Essentials certificate confirms the controls were in place at the point of assessment, not that a newly published weakness has since been closed. New vulnerabilities appear daily, and your environment shifts constantly as people join and systems are added – so the gap between that snapshot and reality widens from the moment the report is signed off.

Continuous vulnerability management fills that gap. It finds and addresses new weaknesses as they emerge, and treats critical, actively exploited issues as what they are – a security event needing immediate attention, not a line item in next quarter’s report.

Evidencing the work to clients, investors and insurers

The final step is the one firms most often overlook, and the one they’re most frequently asked about. Operational due diligence questionnaires, cyber insurance renewals and FCA operational resilience expectations all assume you can describe how known weaknesses are identified and addressed – in practice, not in principle.

Useful reporting shows exposure trending down over time, how quickly serious issues were resolved against agreed targets, and what residual risk has been consciously accepted and why. A technical export doesn’t answer that. A short, clear management report does.

Vulnerability management – the bottom line

A vulnerability management service is not a scan, and it isn’t patching with a more impressive name. It’s the continuous business of knowing where you’re exposed, deciding what matters, closing it, and being able to prove it.

That last point – exposed – is where this is heading. Not every vulnerability is an exposure, and the firms getting this right are shifting from counting flaws to understanding which ones an attacker could genuinely reach. In part two, we’ll look at what exposure management means in practice, and how to tell a service that reduces risk from one that simply reports it.

How we can help

At Doherty Associates, we’ve spent over 34 years helping organisations in highly regulated, risk-sensitive industries strengthen their cyber resilience – with vulnerability management now forming a core part of that mission.

Whether you’re looking to establish what’s genuinely on your estate, prioritise the exposures that carry real business risk, or evidence that work to your board, clients and insurers, our team can act as an extension of your internal IT and security function.

If you’re reviewing how a vulnerability management service could reduce risk for your firm, our specialists would be happy to guide you through the best next steps. Learn more on our Vulnerability Management Services page.

Related content

Doherty Associates IT Solutions

Blogs

What does Anthropic’s Mythos mean for our AI cyber security risk?

Read more
Doherty Associates IT Solutions

Blogs

Should our firm move to passwordless sign-in and passkeys?

Read more
Doherty Associates IT Solutions

Blogs

Should I be worried about privacy and security when working remotely?

Read more

We’re here to help

If you want to achieve better outcomes for your business through a more intelligent use of technology, talk to us.

Contact us