Blog
The 30-Day Patch and the Software Nobody Wants to Touch
Every computer, server, firewall and phone in your company runs software, and software has flaws. When a maker finds a security flaw, it releases a fix, usually called a patch or an update. Patching is simply installing those fixes.
It sounds routine, and mostly it is. But cyber-insurance carriers have started asking how fast you do it, and what you do about the systems that can't be patched at all.
What the forms ask
In our review of 13 public carrier applications (November 2026), 8 asked about patching cadence: a process for installing security updates on a stated timetable. The wording varies:
- Travelers asks whether critical patches are installed within 30 days.
- Markel offers choices such as within two weeks, within a month, or within two months.
- Beazley asks for the average time to fix the most serious known vulnerabilities, with options going down to 48 hours.
- CFC asks you to describe the process, including what you'd do with a "zero-day," a flaw criminals are already using before a fix is widely available.
Only 3 of the 13 asked directly about end-of-life or unsupported software (Beazley, Markel and Coalition's ransomware supplement). All three want to know whether those leftover systems are separated from the rest of the network.
Why speed matters now
When a serious flaw is announced, criminals don't wait. They scan the internet looking for systems that haven't been patched, often within days. Internet-facing equipment such as firewalls, VPN devices and remote-access tools is the most exposed, because anyone in the world can reach it.
CISA keeps a public list called the Known Exploited Vulnerabilities catalog: flaws it has evidence are being actively used in attacks. You don't need to read it yourself, but your IT provider should know whether anything on that list applies to you, and how quickly it gets fixed.
Three kinds of patching
It helps to think of patching in three buckets, because they're usually handled differently.
1. Workstations. Windows, macOS, browsers and Office. These are the easiest to automate, and most IT providers do it well. Ask what percentage of computers are fully up to date, and what happens to laptops that are rarely connected.
2. Servers and business applications. Patching these can mean downtime, so it gets scheduled and sometimes postponed. Accounting systems, file servers and line-of-business applications often fall into this bucket.
3. Network equipment. Firewalls, VPN devices, switches and Wi-Fi gear. These are the most often forgotten, and the firewall and VPN are among the most targeted. Their updates are usually manual and are the ones I'd ask about first.
The software nobody wants to touch
Every company of 50 to 250 people seems to have one. An old accounting program. A computer that runs a piece of equipment. A server that hosts an application the vendor stopped supporting years ago. "It can't be upgraded yet," and it's been in that state for a long time.
End-of-life means the maker no longer releases security fixes. Windows 10 is a recent example: Microsoft ended regular support on October 14, 2025, outside of a paid extended-update program. Older server operating systems, firewalls and network gear reach end-of-life too, and they're easier to forget because nobody looks at them every day.
When I ran IT at a company of about 200 people, the leftover system was almost never a mystery. Everyone knew which one it was. What was missing was an owner for replacing it and a written answer to the question, "If it has to stay, how is it fenced off?"
Fencing off what must stay
If a system genuinely has to remain for now, the goal is to make sure a problem on it can't spread, and that the internet can't reach it. In practice that means:
- No direct internet access to or from it unless it's truly needed.
- A separate network segment, so the rest of the office can't easily reach it, and it can't easily reach the rest of the office.
- Limited logins: only the few people who need it, with their own accounts.
- A replacement date and an owner, written down and reviewed.
That's exactly what the carriers are asking about. "We have an old system, and here's how it's isolated, and here's the replacement plan" is a far better answer than hoping the question doesn't come up. And some of those systems are visible from the outside, so hoping isn't really an option.
Setting a realistic target
A sensible goal for a company your size is something like this: critical security updates on workstations within two weeks; critical updates on internet-facing equipment (firewall, VPN, remote access) as fast as possible, ideally within days when a flaw is being actively used; and everything else within 30 days. Ask your provider to report against those targets monthly in a simple form.
The target matters less than knowing your real numbers and being able to show them.
What to do Monday morning
- Ask your IT person or provider when critical updates were last fully deployed to workstations, servers and the firewall or VPN, as three separate dates.
- Ask for a list of every system that's out of support, including network equipment, and whether each one can be reached from the internet or from the rest of the office.
- For each leftover system, write down how it's isolated, who owns the replacement project, and a target date.
- Agree on a patching target (for example, 14 days for critical workstation updates and 30 days for everything else) and a short monthly report against it.
- Ask how your provider hears about actively exploited flaws, such as those in CISA's catalog, and how fast they act on them.