Every business that runs computers faces the same uncomfortable choice. Install updates quickly and you risk an update breaking something your team depends on. Wait to test them and you leave a known weakness open for attackers. For years, waiting a few weeks was a reasonable compromise. That window is getting smaller, and that changes how a small business should approach patch management.
Recent high-profile outages have made many IT teams more cautious about installing updates. At the same time, attackers are using AI to turn newly announced vulnerabilities into working attacks faster than before. Both pressures are real. Below is how we would balance them for a business with 10, 50 or 100 employees, where there is no dedicated patching team and an outage lands on the owner’s desk.
Why both risks are real
Updates can cause outages. The clearest recent example is July 2024, when a faulty security-software update crashed Windows computers around the world. Microsoft estimated that about 8.5 million Windows devices were affected. Airlines, hospitals and banks spent days recovering. Small businesses see smaller versions of this all the time: a printer driver that stops working, an accounting program that won’t open after a Windows update, a line-of-business app that needs a vendor fix before it runs again.
Not updating gets businesses breached. Attackers routinely target weaknesses that already have a fix available. The U.S. Cybersecurity and Infrastructure Security Agency keeps a public Known Exploited Vulnerabilities catalog listing flaws that are being used in real attacks, and most entries have a patch. As attackers use AI to study new fixes and build attacks against them, the time between “a patch is released” and “someone is exploiting the problem” keeps shrinking.
So “always patch immediately” and “always wait and test” are both wrong. The better answer is to decide in advance which updates go fast, which go carefully, and what you do in between.
Not every update carries the same risk
The most useful step a small business can take is to stop treating every computer and every update the same. Two questions sort most decisions:
- How bad is it if this system goes down for a day? One employee’s laptop being offline is an inconvenience. Your file server, accounting system or the computer that runs your phones or scheduling is a business stoppage.
- How exposed is the weakness? A flaw in something that faces the internet (firewall, VPN, remote access, email, web browser) is far more urgent than a flaw in a tool only one person uses inside the office.
Put those together and you get a simple map:
- Low impact, high exposure (laptops, desktops, browsers): patch quickly. If an update breaks one laptop, you fix one laptop. If you leave browsers unpatched, every employee is a way in.
- High impact, high exposure (firewalls, VPNs, remote access, internet-facing servers): these are the hard ones. Patch on a short, planned timeline, with a backup and a rollback plan ready first. When an actively exploited flaw is announced, this group moves to the front of the line.
- High impact, low exposure (internal servers, line-of-business applications): test first, schedule a maintenance window, confirm the software vendor supports the update, and keep a recent backup.
- Low impact, low exposure: normal schedule.
A practical patching approach for a small business
1. Know what you have
You cannot patch what you don’t know about. Keep a current list of computers, servers, network equipment and the software running on them, including the old PC in the back office that “just runs one program.” Unknown devices are where unpatched problems hide.
2. Roll updates out in waves
Instead of updating everyone at once, update a small test group first: a few computers belonging to people who will notice and report problems quickly. If nothing breaks after a short wait, update everyone else. This catches most bad updates while they affect two people instead of the whole office.
3. Back up before you touch critical systems
Before updating a server or business-critical application, confirm there is a recent backup and that it can actually be restored. A backup that has never been tested is a hope, not a plan. Our guide on how to test business backups explains what a real restore test looks like.
4. Have a way back
For each important system, know in advance how you would undo an update: uninstall it, restore a snapshot, or recover from backup. Decide who makes the call and how long you will troubleshoot before rolling back. Making that decision in the middle of an outage is how a two-hour problem becomes a two-day problem.
5. Patch at sensible times
Schedule restarts for servers and key systems outside business hours when possible, and tell staff in advance when something needs to reboot. Most update-related frustration comes from surprise restarts, not the updates themselves.
6. Protect what you can’t patch yet
Sometimes you can’t update right away: the vendor hasn’t certified the fix, or the system can’t go down this week. In that case, reduce the exposure while you wait. Options include turning off the affected feature, limiting who can reach the system from the internet, requiring multi-factor authentication, and making sure endpoint security is watching it closely. Write down the exception and the date you will revisit it, so “temporarily” doesn’t become “forever.”
7. Check that patches actually installed
Updates fail silently more often than people think. A computer that has been off for a month, or an update that needs a restart nobody did, leaves a gap. Regular reporting and vulnerability scanning show what is still missing so it can be fixed.
Questions to ask your IT provider
If someone else manages your technology, these questions will tell you quickly whether patching is under control:
- Which of our devices and applications do you update, and which are left to us or to a software vendor?
- How do you decide which updates go out quickly and which are tested first?
- What happens when an actively exploited vulnerability is announced?
- Do you update a test group before everyone else?
- How do you confirm updates installed, and can we see a report?
- Is there a recent, tested backup before you update our servers?
- What is the plan if an update breaks something?
Clear answers to these questions matter more than any single tool.
How SupportMax handles updates
As part of our managed IT services, SupportMax proactively monitors client devices and manages updates and patches. When our vulnerability scans find known weaknesses, we close them with patching and configuration changes. We pair that with managed backups with restore testing, so there is a way back if an update goes wrong, and endpoint protection that keeps watch while a fix is pending. If you already have in-house IT, our co-managed IT service can take on security tools, monitoring and patching alongside your team.
If you’re not sure where your business stands, our Cybersecurity Assessment includes a vulnerability scan and a written, plain-English report ranking the gaps by business risk. Or start smaller: schedule a 15-minute consultation, or call us at (310) 331-8119, and we’ll talk through how updates are handled in your office today.
Frequently asked questions
What is patch management?
Patch management is the routine of finding, testing, installing and confirming software updates across your computers, servers, network equipment and applications. Many updates fix security weaknesses, so keeping up with them is one of the most effective ways to reduce the risk of a breach.
Should a small business turn on automatic updates?
For most employee laptops, desktops and web browsers, yes. Automatic updates close common security gaps quickly, and a bad update usually affects only one device. Servers, firewalls and critical business applications need a more controlled approach: a backup first, a planned time, and a way to undo the change.
How quickly should security patches be installed?
It depends on the system and the risk. Updates for internet-facing systems and for flaws that are already being exploited should be at the front of the line. Lower-risk internal systems can follow a regular schedule after testing. The important thing is having a written rule so decisions aren’t made from scratch each time.
What if a software vendor won’t support the latest update?
Ask the vendor for a timeline, and reduce the exposure in the meantime: limit internet access to the system, require multi-factor authentication, and monitor it closely. If a vendor regularly lags far behind on security updates, that is worth raising at your next technology review.






