Skip to content
←Back to glossaryCyber

End-of-life software

Software its vendor no longer patches: every flaw found after the end-of-support date stays open, and cyber underwriters treat it as a permanent vulnerability.

Definition

On May 12, 2017, WannaCry encrypted hundreds of thousands of machines, and a good share of them still ran Windows XP, which Microsoft had stopped patching in April 2014. A fix for the exploited flaw had been out since March for supported versions. On May 13, Microsoft shipped an exceptional patch for XP, and the move stood out precisely because it broke the rule. End-of-life software is a product whose vendor has stopped issuing security updates on a date announced well in advance. Windows 7 has received none since January 14, 2020, and Windows 10 none since October 14, 2025, except for customers paying for Extended Security Updates. For an underwriter the date matters more than the brand: after it, every newly published flaw stays exploitable indefinitely across the affected fleet. The application therefore asks what share of the estate is out of support, and which systems cannot be migrated (controllers, workstations driving a machine, line-of-business software tied to an old version). A candid answer backed by documented isolation usually carries more weight than a no that turns out to be false at the first claim. On the wording side, several market forms carry an unpatched vulnerability exclusion, or a retention and sublimit that worsen as the flaw ages; an XP workstation falls into it by design. Network segmentation serves as the compensating control when migration is impossible, and the underwriter will credit it as long as it can be verified. One caveat: an unsupported system that talks to nothing is a modest risk; network exposure is what makes it dangerous. Not to be confused with a zero-day: there, nobody has a fix yet; here, the vendor has decided not to write one.

Its 6 cross-references, woven across the glossary's 18 categories
End-of-life software: Cyber glossary illustration, AlgoPolis
Example

Hypothetical: a manufacturing company reports 400 workstations, 30 of them still on Windows 7 because they drive machine tools whose maker certifies no other system. The underwriter asks for the network diagram: are those 30 machines on an isolated segment, with no email or web browsing, and a single filtered connection to the production server? If so, the file notes a compensating control and the review goes on. If they share the office network, the quote comes back with an unpatched vulnerability exclusion applied to those machines, or a higher retention for any loss that starts there.

Read next
Put it to work
Related terms
Also known as

end of life software, end-of-support software, unsupported operating system, EOL software, out-of-support system

Stay informed

Follow the research

One letter a week. First, the week's underwriting note, when one is published: a dated, argued decision, signed by Paul Bernardski. Then what the observatory published on cyber risk, political risk and insurance. No account, no tracking.

No spam, one-click unsubscribe, no data ever sold.