CISA BOD 26-02: retiring end-of-support edge devices from federal networks, explained

CISA’s directive of February 5, 2026 gives federal civilian agencies three months to inventory listed end-of-support edge devices, 12 and 18 months to decommission them, and 24 months to have a process that removes devices before support ends.

A binding operational directive is a compulsory direction to federal executive branch departments and agencies for safeguarding federal information and information systems. 44 U.S.C. 3553(b)(2) authorizes the Secretary of Homeland Security to develop and oversee them, and agencies must comply under 44 U.S.C. 3554(a)(1)(B)(ii) [1]. BOD 26-02 deals with one class of risk: devices at the edge of agency networks that vendors no longer support. CISA’s directives page lists it under February 5, 2026 [1] [2].

Why CISA issued it

The directive says CISA is aware of widespread exploitation campaigns by advanced threat actors targeting end-of-support edge devices, and that public reports describe attempts to use these devices to pivot into federal networks [1]. It gives two reasons edge devices attract attackers: their reach into the network and their integration with identity management systems. Once out of support, they no longer receive vendor updates [1].

CISA developed the directive with OMB and frames it as implementing OMB policy on phasing out unsupported systems. It quotes Circular A-130’s requirement that unsupported information systems and components be phased out as rapidly as possible, with planning and budgeting for migration [1]. It also points agencies planning a technical refresh to OMB M-22-09 on zero trust, naming multi-factor authentication, asset management, isolation of critical workloads and encryption of data in transit [1].

Definitions and scope

  • End of support (EOS): hardware, firmware and software versions that no longer receive timely, supported updates from the original equipment manufacturer, including patches for CVEs, security updates, hotfixes and defect fixes.
  • Edge devices: all technology devices on the boundary of an agency’s network that are accessible from the public internet. The directive’s list includes load balancers, firewalls, routers, switches, wireless access points, network security appliances, IoT edge devices, software defined networks and other physical or virtual networking devices that route traffic and provide privileged access [1].

A device is in scope if it is an edge device operating as a component of an information system owned or operated by or on behalf of an agency, is considered EOS by its vendor or by CISA, and is physically or logically located on an agency’s network boundary [1]. The directive also states:

  • it applies to federal information systems on agency networks and to those hosted by third parties on an agency’s behalf;
  • it applies to Federal Civilian Executive Branch agencies, not contractors, but agencies may need to modify contracts to comply;
  • it does not apply to operational technology devices or to FedRAMP-authorized cloud products and services defined as out of scope by OMB M-24-15;
  • like all directives, it does not apply to national security systems or to certain Department of War and Intelligence Community systems [1].

The edge is the directive’s focus, but it adds that EOS devices should not reside anywhere on federal networks [1].

The required actions and their deadlines

Every deadline is stated as a period from issuance. The directive gives no calendar dates [1].

  1. Immediately, until rescinded or superseded: update each vendor-supported edge device that is running EOS software, including firmware, to a vendor-supported version, where the update does not adversely affect mission-critical functions.
  2. Within three months: inventory all devices on CISA’s EOS Edge Device List and send the inventory to CISA on its template.
  3. Within 12 months: decommission every device on the list with an EOS date on or before that deadline, replacing devices as needed with vendor-supported ones, and report the decommissions to CISA.
  4. Also within 12 months: inventory all in-scope edge devices that are EOS or will become EOS within the following 12 months, and send that inventory to CISA.
  5. Within 18 months: decommission all identified EOS edge devices from agency networks, replacing them as needed with devices that receive current security updates, and report to CISA.
  6. Within 24 months: establish a process for continuous discovery of all edge devices; maintain an inventory of those that are EOS or will be within 12 months; decommission such devices on or before the date they reach EOS; and report decommissions to CISA under current CISA guidance [1].

The EOS Edge Device List is described as a preliminary repository meant to help agencies identify devices in the first three months. After that, agencies are responsible for identifying, tracking and refreshing all edge devices themselves [1].

What CISA commits to

  • Provide the initial list of EOS and soon-to-be EOS edge devices, with product name, version number and end-of-support date.
  • Evaluate ways to automate agencies’ discovery and reporting, and provide a way to submit them in machine-readable form.
  • Review the directive as needed and consider Supplemental Direction.
  • Within 15 months of issuance, assess agency progress and report to the Secretary of Homeland Security, the Director of OMB and the National Cyber Director [1].

Why the directive is as much about budgets as about patching

Only the first action is a software update. The others call for inventories, decommissioning and, as needed, replacement devices, and two of the inventories cover devices that will reach end of support within the following 12 months [1]. The directive says agencies should identify hardware and software nearing EOS, plan replacements, procure vendor-supported alternatives and plan decommissioning with minimal disruption [1]. In our view, the 24-month requirement to retire devices on or before their EOS date turns lifecycle data, such as vendor support dates, into an input to the budget cycle. That is our reading, not a requirement stated in the directive.

For contractors that operate edge infrastructure for agencies, the directive applies through their customers: it covers systems hosted by third parties on an agency’s behalf, and agencies may need to change contracts [1]. As listed on CISA’s directives page when we checked it on November 14, 2026, BOD 26-02 was not marked revoked [2]. A companion explainer covers BOD 26-04 on risk-based remediation.

This explainer describes the directive; it is not legal advice, and agencies and their suppliers should confirm with counsel and their contracting officers how it applies to them.

Moraph’s teams help organizations with work like this. See our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • CISA
  • BOD 26-02
  • binding operational directive
  • end of support
  • edge devices
  • asset lifecycle
  • FCEB