← All posts
Managed ITVulnerability management

Understanding Vulnerability Risk Management for Your Business

An assessment tells you where you stand. Risk management is the routine that keeps the list short.

A vulnerability is a weakness an attacker can use: a flaw in software that hasn’t been patched, a setting left at its default, a password that’s too easy, a device nobody updates. Every business has some, and new ones are published every week for software you probably run.

Vulnerability risk management is what you do about that, over and over. There’s no end date. It’s a routine: find the weak spots, decide which ones matter, fix those first, and keep a record of the ones you can’t fix yet. A one-off vulnerability risk assessment tells you where you stand on one day; this post is about keeping it that way.

The monthly cycle

Most of the work fits into a monthly rhythm, which suits the way software makers release fixes. Microsoft, for instance, releases most of its security updates on the second Tuesday of each month.

1. Keep the list of what you have

Every computer, server, network device, printer and cloud service, with the software on each. New equipment gets added the day it arrives; retired equipment comes off. Anything missing from this list is missing from everything that follows.

2. Find what’s weak

Scanning tools check each device against public databases of known flaws and report missing updates and risky settings. Run them at least monthly and after any big change. Scans that sign in to the device find much more than scans from outside.

3. Decide what matters

Not every finding is urgent, and treating them all the same is how teams drown. Rank them by a few plain questions:

  • Is anyone known to be using this flaw in real attacks? The US Cybersecurity and Infrastructure Security Agency (CISA) keeps a free Known Exploited Vulnerabilities catalog for exactly this, and recommends using it as one input to deciding what to fix first.
  • Can it be reached from the internet?
  • Does the device hold or reach sensitive information, such as client files, payroll or the bank?
  • How bad would it be if this device stopped working tomorrow?

A flaw that scores yes on the first two goes to the top, whatever severity number the scanner gives it.

4. Fix it, or decide what to do instead

For most findings the fix is an update or a settings change. For some, there isn’t a fix yet, or the fix would break something you depend on. Those need a decision, written down: limit what the device can reach, add extra monitoring, or accept the risk for a set period and revisit it.

5. Check the fix worked

Rescan. Updates fail quietly more often than people expect, and a fix nobody checked is a guess.

6. Record it

What was found, what was done, what was left open and why. That record is what you hand an insurer, an auditor or a customer who asks how you manage security.

Patching is most of the work

The bulk of vulnerability management is patching, and the patching that gets skipped is rarely Windows on office computers, which mostly updates itself. The gaps tend to be elsewhere:

  • Third-party software: PDF readers, browsers other than the default, remote access tools, accounting and practice software.
  • Servers, which people are nervous to restart during the day and then forget to restart at night.
  • Network equipment: firewalls, switches and Wi-Fi access points, which need firmware updates applied by hand.
  • Printers and copiers, which are computers too. Our post on print network security covers them.
  • Anything past its support date, which no longer gets fixes at all. That’s a replacement decision, not a patching one; our post on how often to upgrade technology helps with the timing.

A sensible routine: test updates on a few machines first, roll them out to everyone within days, and keep a short list of devices that need special handling, with a named person responsible for each.

A fix nobody checked is a guess.

When you can’t fix it

Every business ends up with something it can’t patch: an old machine that runs one essential program, a piece of equipment whose maker stopped updating it. Leaving it alone and hoping isn’t a plan. The usual options are:

  • move it to its own part of the network so it can’t reach, or be reached from, anything it doesn’t need
  • take it off the internet entirely if it doesn’t need to be on it
  • watch it more closely
  • set a date to replace it, and put the cost in the budget

Write down which option you chose and why. An exception with a reason and a date is risk management. An exception nobody remembers making is just a weak spot.

Three numbers worth tracking

You don’t need a dashboard. Three numbers, checked monthly, tell you whether the routine is working:

  1. Open critical findings, especially anything on the CISA list. This should trend toward zero.
  2. How long critical findings stay open. Days is good; months is a problem.
  3. Devices behind on updates. A handful is normal. A growing number means something in the routine has slipped.

Who owns it

The most common failure has nothing to do with technology: nobody is clearly responsible. The scanning tool sends a report to an inbox, everyone assumes someone else is handling it, and the same findings show up month after month.

Someone has to own the routine, whether that’s a person on your staff with the time and know-how or your IT provider. If it’s your provider, ask to see the three numbers above every month or quarter.

For how an unpatched weakness turns into a real incident, read our breakdown of the anatomy of a cyberattack.

Handing over the routine

For our Managed IT customers, keeping operating systems and software updated on a schedule and checking afterward is part of the monthly work, alongside endpoint detection and response on every computer. Printers and copiers are kept current as part of our print security setup. If you’d like to know where you stand before deciding anything, our free technology review looks at what you have, how old it is, whether it’s supported and how well it’s protected, and puts it in writing. Call (386) 252-2292.

More on Managed IT

Let's build your foundation.

Tell us where your business is today and we'll help map the next step.