"Our insurer never asked about our old file server, so it can't matter, can it?" It matters more than most owners think. End-of-life software and hardware are no longer just an IT hygiene issue that underwriters might mention; at least one major carrier now defines vendor support status directly into its policy wording, which means the age of your technology can change how much of a loss you carry yourself.
The common belief is that patching discipline protects you. If your team installs updates on time, you have done your part. The problem with unsupported systems is that there is nothing to install. When a vendor stops shipping fixes, a well-run patch program and a neglected one end up in the same place, and an insurer reading the wording strictly can treat them the same way.
Yes. End-of-life software can reduce or complicate cyber insurance coverage in three ways: it can trigger policy provisions that shift more of a loss onto you, it can make application answers about supported systems inaccurate, and it measurably raises the odds of an incident. The exposure exists whether or not anyone mentioned it at renewal.
"Void" is usually the wrong word. Policies rarely disappear because one server is old. What happens more often is quieter: a loss that traces back to unsupported technology lands under a sublimit or a coinsurance band you did not plan for, or the insurer questions the accuracy of what you attested on the application. Both outcomes leave the business paying for something it assumed was insured.
The clearest published example comes from Chubb. Its Cyber Enterprise Risk Management policy wording defines a "Neglected Software Exploit" as the exploitation of a vulnerability in software that has been withdrawn, is no longer supported, or has reached end-of-life or end-of-support status with its vendor, "where extended support from such vendor has no longer been purchased." A second trigger covers high-severity CVEs that had an available patch you did not apply within set time bands.
Losses arising from a Neglected Software Exploit are subject to their own sublimit, excess, and coinsurance under that wording. Chubb's U.S. cyber product page describes the patch side as a 45-day grace period, after which risk sharing shifts progressively to the policyholder at the 45-, 90-, 180-, and 365-day marks. Your percentages will be set in your own schedule, so treat this as a structure to look for, not a quote.
The detail worth underlining is the extended support language. Paying for a vendor's extended support program, such as Microsoft's Extended Security Updates, changes how the end-of-life trigger reads. Letting that support lapse on a machine that still runs a critical workload can move that machine from "supported" to "neglected" in the policy's eyes, even though nothing about it changed on your network.
Carriers did not invent this concern. Coalition's 2023 Cyber Claims Report found that policyholders of every size that kept using end-of-life software were three times more likely to suffer an incident. Underwriters price that kind of finding into questions, terms, and exclusions.
The attack data points the same direction, especially for network gear. In a May 2025 public service announcement, the FBI warned that criminals were compromising end-of-life routers with a variant of TheMoon malware and selling access to them as proxies, noting that routers dated 2010 or earlier likely no longer receive manufacturer updates. In February 2026, CISA, the FBI, and the U.K. National Cyber Security Centre published a joint fact sheet on end-of-support edge devices urging organizations to inventory edge devices with their support timelines and replace end-of-support devices promptly. It pairs with CISA's BOD 26-02, which applies only to federal civilian agencies but which the agencies strongly encouraged every organization to follow.
That is the real example SMBs should take seriously. When three national security agencies publish guidance that boils down to "know when your firewalls and VPN appliances lose support, and replace them," underwriters read the same guidance, and so do the attackers looking for the devices nobody replaced. We covered a related edge-device scenario in what happens when a firewall can be rebooted on command.
Underwriters typically ask whether critical systems run vendor-supported software, how quickly critical patches are applied, and whether you maintain an asset inventory. Those questions look routine, but your answers become part of the contract, and an answer that was true at binding can drift out of date as machines age past their support dates.
That drift is the hidden link between lifecycle management and coverage. The controls underwriters now expect evidence for, from patch management to documented inventories, are laid out in what underwriters actually require in 2026. If an outside provider manages your environment, it is also worth checking whether your agreement makes anyone responsible for tracking support dates at all, a gap we examine in why your MSP contract might be your biggest unreviewed risk.
For most small and mid-sized businesses, the dates that matter over the next year are Windows 10 Extended Security Updates, Windows Server 2016, and the support timelines of edge devices like firewalls, routers, and VPN appliances. Each has a different cost to stay supported, and each is a likely question at your next renewal.
Windows 10 support ended on October 14, 2025. According to Microsoft's Extended Security Updates documentation, commercial ESU costs $61 per device for year one and doubles every consecutive year, for a maximum of three years, and only devices on Windows 10 version 22H2 are eligible. Organizations now in year two are paying twice the first-year rate for every machine they have not migrated. If you are still deciding what to do with those devices, our guide on whether to upgrade or replace Windows 10 devices walks through the options, and what happens to your applications after Windows 10 support ends covers the line-of-business software that often keeps old machines in service.
Server is where SMBs most often get caught. Microsoft's Windows Server 2016 lifecycle page lists the extended end date as January 12, 2027. For a business renewing in late 2026 or early 2027, file servers, domain controllers, and accounting application hosts on 2016 will lose support inside the coming policy period. Migrations that involve line-of-business applications rarely finish quickly, so a project that has not started by now is likely to overlap that date.
Edge devices have the least predictable timelines because each vendor publishes its own end-of-sale and end-of-support dates by model. They also carry the highest exposure, since they sit directly on the internet. A firewall that stops receiving firmware updates turns every future vulnerability in that product into a permanent opening.
Treat this as a lifecycle problem with an insurance deadline, not an insurance problem. The steps below line up your technology plan with your policy so that the answers you give an underwriter are accurate and the wording in your policy does not surprise you after an incident.
Isolation deserves a word of caution. Segmenting an unsupported machine reduces the chance it is exploited, but it does not change its support status, so under wording like Chubb's it can still be the system that moves a claim into a less favorable band. Isolation is a risk control, not a coverage fix.
The underlying discipline is the same one we describe in the technical debt time bomb: deferred upgrades accumulate quietly until an outside party, whether an insurer, an auditor, or an attacker, forces the issue. Risk-based patching helps with the systems you can still fix, as we explain in what CISA's BOD 26-04 means for small business patching, but it cannot fix systems the vendor has stopped supporting.
For managed clients, we maintain a living hardware and software inventory with vendor support dates attached, and we review it on a set schedule so end-of-life decisions happen in budget cycles instead of emergencies. Before a renewal, we flag every system that is unsupported or will be within the policy period, and we give leadership a short list of replace, isolate, or extend decisions with their costs.
Because we also help clients prepare insurance applications, we check that answers about supported systems match the environment as it actually exists, and we document the controls around any system that has to stay in service. That record is what lets a broker negotiate from facts and lets you answer an underwriter's question without guessing.
If you cannot name the end-of-support date of your firewall, your oldest server, and your remaining Windows 10 machines, start there. That one list tells you where your security risk and your insurance risk overlap, and how much time you have to act before renewal.
Securafy's managed IT plans include lifecycle tracking and planned refreshes, so unsupported systems are replaced on a schedule rather than discovered during a claim.
If you would rather review your environment and policy together first, book a strategy call with Securafy and we will walk through what is running, when it loses support, and what that means for your coverage.