Join our Newsletter — 33% off our NHI Course
Home› Guides› Edge Device End of Life Replacement Playbook: Find,…
Template Network Security

Edge Device End of Life Replacement Playbook: Find, Isolate and Replace Unsupported Devices

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 10 min read
On this page

An end-of-support firewall, VPN gateway or router on the internet edge will never be patched again, and attackers know which models those are. In February 2026 CISA, the FBI and the UK NCSC jointly warned that nation-state actors exploit end-of-support edge devices to enter networks and keep access, and CISA issued Binding Operational Directive 26-02 requiring US federal civilian agencies to manage edge device lifecycles. This template treats an unsupported edge device as a security event with an owner, a deadline and evidence, not a procurement line item. It is for network, infrastructure and security teams, and is written so that [Organisation] can adopt it as-is. For edge device hardening in general see the Edge Device Security Guide; for a device you suspect is already compromised use the Edge Device Compromise Investigation Playbook.

How to use this template

  • Replace the placeholders: text in square brackets, such as [Organisation], [CISO] and [30 days], is for you to set.
  • Run it per device class: open one record per model or software train reaching end of support, listing every affected unit.
  • Treat it as an incident workflow: the sections follow the incident lifecycle because an exposed, unsupported device carries incident-level risk. Containment here means reducing exposure until replacement.
  • Escalate on evidence of compromise: if triage finds signs of tampering, stop and switch to your edge device compromise investigation process before wiping or swapping anything.
  • Definitions: a device is end of support (EOS) when the manufacturer stops monitoring it for software or firmware defects and stops releasing patches, the definition used in the 2026 CISA, FBI and NCSC fact sheet. Vendors use their own milestone names (for example End-of-Sale and Last Date of Support); record the date security fixes stop, which may differ from both.

1. Scope and triggers

1.1 This playbook covers internet-facing and boundary devices owned or operated by [Organisation] or by suppliers on its behalf: firewalls, VPN and remote access gateways, routers, load balancers, web application firewalls, email gateways, wireless controllers, SD-WAN appliances and their management software.

1.2 The playbook is triggered when any of the following occurs:

TriggerSourceTarget response
Vendor announces an end-of-life or end-of-sale date for a model or software train in useVendor bulletins, lifecycle feedsOpen a record within [10 working days]; plan replacement before the security support end date
Security support end date is within [12 months]Asset inventory lifecycle fieldFunded replacement plan approved
Device has passed its security support end dateInventory, scanApply section 4 containment within [7 days]
A vulnerability affecting the device appears in the CISA KEV catalogue with no fix for its versionKEV feed, vendor advisoryTreat as an emergency: contain within [48 hours]
Discovery scan finds an undocumented edge deviceExternal attack surface scanIdentify owner and support status within [5 working days]
Supplier-operated device on [Organisation]'s boundary is found to be unsupportedThird-party assuranceNotify the supplier and agree a dated plan

1.3 The KEV catalogue regularly tells defenders to discontinue unsupported products. In the catalogue version of 21 October 2026, 83 of 1,754 entries mention end-of-life in their required action or notes, across vendors that include D-Link, Zyxel, NETGEAR and Ivanti. See the CISA KEV Catalogue Guide.

2. Roles and contacts

RoleResponsibilityNamed contact
Device ownerAccountable for replacement on time; approves change windows[Name, team]
Network engineeringConfiguration export, replacement design, cutover and rollback[Name]
Security operationsTriage for compromise, monitoring during the exposure window[Name, on-call number]
Vulnerability managementTracks EOS status, KEV matches and exceptions[Name]
Procurement and financeReplacement purchase and vendor lifecycle commitments[Name]
Risk ownerSigns any continue-at-risk exception[CISO or delegate]
Vendor and resellerLifecycle confirmation, extended support options, trade-in[Account contact, support portal]

3. Detection and triage

3.1 Confirm the inventory. Record for each unit: model, serial, software version, location, internet exposure, management interface exposure, owner and the vendor's security support end date. Australian, Canadian and US guidance all start here: keep the support timeline in the inventory and scan for undocumented edge devices, which are often the oldest.

3.2 Score the exposure. Use the matrix below to set priority.

FactorHighest priorityLower priority
ExposureInternet-facing service or management interfaceInternal only, behind a supported boundary
FunctionVPN, remote access, firewall, email gatewayBranch switch, lab equipment
Known exploitationKEV entry or public exploit for the running versionNo known exploited vulnerability
Credential weightHolds directory bind accounts, RADIUS secrets, VPN certificates or API keysLocal accounts only
StatusAlready past security support end dateEnd date more than 12 months away

3.3 Check for compromise before you touch it. Unsupported edge devices are prime targets, so before replacement collect running configuration, local account list, software image hashes where the platform allows, and off-device logs for the last [90 days]. Look for unknown administrator accounts, unexpected configuration changes, unfamiliar outbound connections and image or boot changes (MITRE ATT&CK T1601 Modify System Image, T1556.004 Network Device Authentication). Any positive finding moves the device to the compromise investigation playbook.

4. Containment

Containment reduces exposure for the period between detection and replacement. It never makes an unsupported device safe: the UK NCSC states that the only fully effective mitigation for obsolete products is to stop using them.

  1. Remove management exposure: close internet access to management interfaces and restrict them to a management network or jump host, in line with CISA BOD 23-02.
  2. Reduce services: disable unused features, especially web portals, clientless VPN and remote management services with a history of exploitation.
  3. Front it with a supported control: where possible, place a supported firewall or proxy in front, or move the public service to a supported device or cloud service.
  4. Treat it as untrusted: segment traffic from the device, limit what it can reach internally, and do not rely on its own filtering.
  5. Raise monitoring: enable centralised off-device logging at the most detailed level, and alert on administrative logons, configuration changes and hardware changes, as the Canadian Centre for Cyber Security recommends.
  6. Apply the last available update: run the latest software the vendor still offers for the model, as the joint 2026 fact sheet advises for devices that cannot be replaced immediately.
  7. Record an exception if needed: any device that stays in service past its support date needs a signed exception from the risk owner with a replacement date of no more than [90 days] and a review at least every [30 days].

5. Eradication

5.1 Rotate every secret the device held. Edge devices carry non-human credentials: directory bind accounts, RADIUS and TACACS+ shared secrets, VPN server certificates and private keys, IPsec pre-shared keys, SNMP communities, API tokens for cloud management and backup accounts. Assume any of them may have been read from an unpatched device and issue new ones on the replacement rather than importing old ones. See the Leaked Credential Response Playbook.

5.2 Rebuild, do not copy blindly. Migrate configuration by intent, reviewing every rule, local account and allowed peer, rather than importing a config file that may contain attacker changes or obsolete exceptions.

5.3 Verify the new device. Confirm integrity on delivery and install trusted firmware from the vendor before first use, as the Australian Signals Directorate recommends, then apply the vendor's hardening guidance.

6. Recovery

  1. Pilot: cut over one site or one service first, with the old device left powered but disconnected for [48 hours] as the rollback path.
  2. Rollback criteria: define in advance which failures (authentication, routing, throughput) trigger rollback, who decides, and the maximum rollback window. Rolling back to an unsupported device restarts the containment clock.
  3. Full cutover: move remaining services, then remove the old device from the network and the inventory's active list.
  4. Revoke old trust: revoke the old device certificates, remove its accounts from directories and RADIUS clients, and delete its API keys from management platforms.
  5. Dispose securely: sanitise or destroy storage following NIST SP 800-88 Rev. 2 before resale, recycling or trade-in, because configuration files hold secrets and network maps.
  6. Update records: new support end date in the inventory, and a replacement review date set [18 months] before it.

7. Communication and notification

  • Internal: device owner, change advisory board, service desk and affected business units, with cutover dates and expected impact.
  • Leadership: monthly report of devices past support, exceptions and age of each exception.
  • Suppliers and managed service providers: written request for their EOS inventory and dated plans where they operate boundary devices for [Organisation]. NCSC advises checking whether third parties connecting to your environment use obsolete products.
  • Regulators and customers: normally none for planned replacement; if triage found compromise, notification follows the incident response plan.
  • US federal agencies and their contractors: reporting under BOD 26-02 follows the directive's own requirements; confirm the current text on cisa.gov.

8. Post-incident review

Within [20 working days] of closure, record: date the vendor announced end of life, date [Organisation] opened the record, date security support ended, cutover date, days in service past support, compensating controls used and whether any compromise was found. Ask why replacement was not funded before the support end date, and fix that in procurement and budgeting.

Implementation guidance

Decision guidance

SituationOptionWhen it fits
Supported successor model existsLike-for-like replacementDefault choice; shortest project
Service can move to cloud or a managed serviceDecommission the applianceRemote access and email filtering are common candidates; NCSC suggests considering SaaS or cloud where it removes outdated software risk
Vendor sells paid extended security supportShort bridge onlyOnly if fixes are genuinely still produced, under a dated exception
Replacement blocked by budget or supplyContain and exceptInternal-only devices; never for an internet-facing VPN past support

Small and large organisations

  • Small organisations: one router or firewall is often the entire edge. Check its support status at purchase and annually, and replace it the month support ends. See the SOHO and SMB Router Hardening Guide.
  • Large organisations: feed vendor lifecycle data into the CMDB, report devices within 12 months of support end every quarter, and make lifecycle commitments (patch history, response times, published hardening guidance) a procurement criterion, as ASD recommends.

Metrics

  • Number of internet-facing edge devices past security support end date (target zero).
  • Median days in service past support end date.
  • Percentage of edge devices with a recorded support end date in the inventory.
  • Percentage of replacements funded at least 12 months before support end.
  • Open exceptions and their age.

Framework mapping

FrameworkReference
NIST CSF 2.0ID.AM-02, ID.AM-08, PR.PS-02, PR.PS-03
NIST SP 800-53 Rev. 5SA-22 Unsupported System Components, CM-8, SI-2, RA-3, SR-12 Component Disposal, MP-6
CIS Controls v8.1Safeguard 1.1 (asset inventory) and 2.2 (ensure software is supported)
MITRE ATT&CK v20T1190 Exploit Public-Facing Application, T1133 External Remote Services, T1601, T1556.004

References

Related NHI Mgmt Group resources: Edge Device Security Guide · Edge Device Exploitation by Threat Actors Guide · Operating System End of Life and Extended Support Guide · Vulnerability Management for Network Devices Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.