Checklist: inventorying, replacing and reporting end-of-support edge devices under CISA BOD 26-02

Twelve steps for federal civilian agencies, following the directive’s deadlines from issuance on February 5, 2026: immediate updates, an inventory at three months, decommissions at 12 and 18 months, and a continuous discovery process at 24 months.

Who this is for

Binding Operational Directive 26-02, Mitigating Risk From End-of-Support Edge Devices, is dated February 5, 2026 on CISA’s website. It binds Federal Civilian Executive Branch agencies, not contractors, though agencies may need to modify contracts to comply [1]. It covers edge devices on an agency’s network boundary that are accessible from the internet and that the vendor or CISA considers end of support (EOS) [1]. Our explainer sets out the directive in full.

Deadlines as the directive states them

Each required action runs from issuance: immediately, then within 3, 12, 18 and 24 months [1]. The directive gives no calendar dates, so the steps state each deadline as the period the directive gives. As checked on November 14, 2026, the directive is listed on CISA’s directives page [2]. Each step names the required action it rests on; where a step is our suggestion, it says so. The owner under each step is a typical role; the directive assigns actions to agencies. This page is not legal advice.

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

The checklist

Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.

  1. CISO with network engineering

    The directive defines edge devices to include load balancers, firewalls, routers, switches, wireless access points, network security appliances, IoT edge devices and software-defined networks, physical or virtual. It covers devices on systems the agency operates or that are hosted by third parties for it, and excludes operational technology and FedRAMP cloud products M-24-15 places out of scope [1].

  2. Network operations

    Required action 1 applies immediately after issuance and until the directive is rescinded or superseded, where the update does not adversely affect mission-critical functionality [1]. Recording each case where an update was deferred for that reason is our suggestion.

  3. IT asset management

    Required action 2 sets this deadline and says the list is a preliminary repository; after the first three months, agencies remain responsible for identifying, tracking and refreshing all edge devices [1]. If the deadline was missed, contacting CyberDirectives@cisa.dhs.gov, the address the directive gives for assistance and reporting, is our suggestion [1].

  4. IT asset management with network engineering

    Required action 2 makes agencies responsible for continuing to identify and track all edge devices after the first three months, and required action 5 asks for an inventory of every in-scope device that is EOS or will become EOS within the next 12 months [1].

  5. CIO with the CFO and acquisition

    The directive cites OMB Circular A-130, which requires unsupported systems and components to be phased out as rapidly as possible and planning and budgeting to include migration, and says agencies should identify devices nearing EOS, plan timely replacements and procure vendor-supported alternatives [1].

  6. Enterprise architect

    The directive says agencies planning technical refreshes should keep M-22-09 in mind and names multifactor authentication, asset management and identification, isolation of critical workloads with strong access policy, and encryption of data in transit, pointing to NIST SP 800-207, TIC 3.0 and CISA’s Zero Trust Maturity Model [1].

  7. Network operations with IT asset management

    Required action 3 requires decommissioning those devices from systems operated by or for the agency, replacing them as needed with vendor-supported devices that can receive security updates, and required action 4 requires reporting the decommissions on CISA’s template [1].

  8. IT asset management

    Required action 5 sets this inventory, on the CISA-provided template [1].

  9. Contracting officer with the CISO

    The directive applies to systems hosted by third parties on an agency’s behalf, applies to agencies rather than contractors, and says agencies may need to modify contracts to comply [1].

  10. Network operations

    Required action 6 extends decommissioning to all identified EOS edge devices on agency networks, with replacement as needed by vendor-supported devices that can receive current security updates, and required action 7 requires reporting each decommission on CISA’s template [1].

  11. CISO with IT asset management

    Required action 8 requires a process for continuous discovery of all edge devices and an inventory of those that are or will be EOS within 12 months; required action 9 requires decommissioning on or before the EOS date and reporting in accordance with current CISA guidance [1].

  12. CISO

    Within 15 months of issuance CISA will assess agency progress and report to the Secretary of Homeland Security, the Director of OMB and the National Cyber Director. CISA will also evaluate automated, machine-readable submissions and may issue supplemental direction [1]. Keeping inventories and decommission reports in one place is our suggestion.

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

  • CISA
  • BOD 26-02
  • edge devices
  • end of support
  • asset inventory
  • lifecycle management
  • federal agencies