On February 5, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) issued Binding Operational Directive (BOD) 26-02, a significant policy mandate aimed at reducing the attack surface of federal government networks. The directive requires all Federal Civilian Executive Branch (FCEB) agencies to identify, report, and ultimately remove all unsupported network edge devices from their environments. This includes hardware and software that has reached its end-of-life (EOL) or end-of-support (EOS) status. Agencies have 12 months to comply with the directive, which targets devices like firewalls, routers, and VPN gateways that are frequently exploited by sophisticated threat actors as an entry point into federal systems. This move underscores a strategic push by CISA to address systemic risk and reduce technical debt across the U.S. government.
Binding Operational Directive 26-02, titled "Strengthening Edge Device Security," was issued in response to a documented increase in the exploitation of unsupported network edge devices by persistent cyber threats, including nation-state actors. These devices are attractive targets because they sit at the perimeter of a network, are often unmonitored, and, once compromised, can provide a pivot point for deeper intrusion.
The directive outlines several required actions for FCEB agencies:
"Unsupported devices pose a serious risk to federal systems and should never remain on enterprise networks," stated CISA Acting Director Madhu Gottumukkala, highlighting the urgency and importance of the directive.
The core requirement is the complete removal of unsupported edge devices. This category includes, but is not limited to:
Any device that is internet-accessible and no longer receives security updates from its manufacturer falls under the scope of this directive. Compliance involves not just a one-time cleanup but the implementation of a sustainable asset and vulnerability management program focused on the network edge.
The directive will have a significant operational and budgetary impact on federal agencies.
T1190 - Exploit Public-Facing Application).Binding Operational Directives are compulsory for FCEB agencies. While specific penalties for non-compliance are not detailed in the source articles, CISA has the authority to report on compliance status to the Office of Management and Budget (OMB) and Congress. Continued non-compliance can result in budgetary scrutiny and other administrative actions.
Organizations seeking to align with BOD 26-02 should take the following steps:
M1047 - Audit.M1028 - Operating System Configuration.This directive is a formal enforcement of replacing software/hardware that can no longer be updated, which is the ultimate form of this mitigation.
Mapped D3FEND Techniques:
The directive mandates a comprehensive inventory (audit) of all edge devices to identify unsupported assets.
A core component of replacing old devices is ensuring new ones are deployed with secure, hardened configurations.
Mapped D3FEND Techniques:
BOD 26-02 is the ultimate enforcement of the 'Software Update' defensive technique by mandating the complete removal of assets that can no longer receive updates. For any organization, public or private, this directive should serve as a model for proactive security. The core tactical recommendation is to establish a non-negotiable, budget-supported technology refresh program. For network edge devices like firewalls and routers, a 3-to-5-year replacement cycle is standard. This program must be tightly integrated with asset management and vendor communication channels to track End-of-Life (EOL) and End-of-Support (EOS) dates proactively. By replacing hardware before it becomes unsupported, organizations eliminate the risk of being unable to patch a critical, remotely exploitable vulnerability, directly countering the tactics of nation-state actors who systematically scan for and exploit these legacy devices.
Simply replacing old hardware is not enough; new devices must be securely configured. As agencies comply with BOD 26-02, they must implement robust platform hardening for all new edge devices. This includes: changing default administrator credentials, disabling unused services and ports (e.g., Telnet, HTTP management), enforcing strong encryption protocols for VPNs and management traffic (e.g., TLS 1.3, SSHv2), and configuring logging to send all relevant events to a central SIEM. Crucially, administrative interfaces should never be exposed to the public internet. Access should be restricted to a secure, internal management network. This hardening process reduces the device's inherent attack surface, making it more resilient to exploitation even if a zero-day vulnerability is discovered.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats