Hardware lifecycle basics
What happens when hardware goes end-of-life?
By Nico De Muynck · Updated July 18, 2026
The short version
Nothing visibly breaks. The switch keeps switching, the server keeps serving — and that's exactly the trap. What actually changes is invisible: security patches stop, compliance status quietly flips, insurance answers change, spare parts dry up, and every remaining month makes the eventual replacement more expensive and more urgent.
Risk 1 — Security: vulnerabilities stop getting fixed
The day support ends, the flow of patches ends with it. Every vulnerability discovered afterwards stays open forever on your device. Attackers know this and specifically hunt unsupported systems: when Windows Server 2012 reached end-of-support it had accumulated over a thousand CVEs, including in the exact services (RDP, SMB, IIS) that ransomware crews target first. Network gear is no different — an unpatched firewall or VPN appliance is one of the most common initial-access points in real breaches. Not sure which milestone means “patches stop”? See EOL vs EOS vs EOSL explained.
Risk 2 — Compliance: audits treat unsupported as failing
GDPR, HIPAA, PCI-DSS, SOC 2, ISO 27001 — nearly every framework expects systems to be supported and patchable. Running end-of-life equipment in scope is frequently an automatic audit finding, and for payment environments it can threaten your ability to process cards at all. The awkward part: auditors usually find the EOL device before you do, because they check vendor lifecycle lists as routine.
Risk 3 — Insurance: the question you must answer honestly
Cyber-insurance questionnaires now routinely ask: “Do you run unsupported software or hardware?” Answer yes and premiums climb or coverage is refused. Answer no incorrectly, suffer a breach through an EOL device, and the insurer has grounds to deny the claim. Either way, not knowing your fleet's lifecycle status is the most expensive option.
Risk 4 — Operations: no parts, no RMA, no ticket
Past the final support date, the vendor won't answer a ticket or ship a replacement part. A failed power supply becomes a grey-market scavenger hunt; a corrupted OS image becomes a dead end. Mean-time-to-repair stretches from hours into weeks — and for a core switch or hypervisor, that's the difference between a maintenance window and a multi-day outage.
Risk 5 — Money: emergency replacements cost multiples
A planned refresh gets budget approval, competitive quotes, scheduled downtime, and staged rollout. An emergency replacement gets expedited shipping, whatever model is in stock, weekend labour, and unplanned downtime on top. The hardware itself might cost the same; everything around it doesn't. Discovering an EOL date after the failure is how a €3,000 switch becomes a €15,000 incident.
What to do about it (this week, not someday)
The fix is unglamorous: know your dates before they matter. Inventory every asset — our free Excel template takes care of the structure. Look up each device's vendor-published dates — the vendor EOL guides show where to check for Cisco, Fortinet and others. Then stop relying on memory: EOL Tracking watches the calendar for you and flips assets to Warning up to two years ahead, with alerts by email, Slack or Teams. Free for your first 5 assets.
Find your riskiest device in the next 10 minutes
Import your fleet, see what's already expired, and get warned before the next one.
Start free — up to 5 assetsNo credit card · no agents · set up in minutes