CISA

Cybersecurity and Infrastructure Security Agency — directives and guidance — CISA (US Department of Homeland Security)

Also known as: Cybersecurity and Infrastructure Security Agency, Binding Operational Directive, BOD, Emergency Directive, KEV catalog, Known Exploited Vulnerabilities

At a glance

Current version
BOD 26-04: Prioritizing Security Updates Based on Risk
Published 10 June 2026. source
Status
In force
Who must comply
Binding and emergency directives apply to US Federal Civilian Executive Branch agencies, not to national security systems or certain Defense and Intelligence Community systems. CISA's wider guidance is voluntary for everyone else. source
Authority
44 U.S.C. § 3553(b)(2) authorizes the Secretary of Homeland Security to develop and oversee binding operational directives; CISA does this work, and agencies must comply under 44 U.S.C. § 3554(a)(1)(B)(ii). source source
Last change

Binding Operational Directives, Emergency Directives, and cross-sector guidance from the US federal cyber defence agency. The directives bind federal civilian agencies directly; the surrounding catalogue, including the Known Exploited Vulnerabilities list, Secure by Design and the Cross-Sector Cybersecurity Performance Goals, is what their contractors and critical-infrastructure operators are measured against in practice.

Recent changes

  1. Info
    CISA, FBI and partners release advisory on SafePay ransomware actors targeting critical infrastructure

    CISA, FBI, U.S. Secret Service and international partners released a joint advisory warning of SafePay ransomware actors, identified as one of the most active ransomware groups …

    Other Enforcement

  2. Low
    CISA releases CVE Program Quality Era Framework to advance vulnerability identification standards

    CISA released a whitepaper, CVE Program: Establishing a Quality Era Framework, detailing its strategy to mature the Common Vulnerabilities and Exposures (CVE) Program—the global standard for …

    Guidance

  3. Low
    CISA releases guidance on implementing cyber decoy strategies for critical infrastructure

    CISA released new guidance titled "Using Cyber Decoys to Strengthen Detection and Response" to help critical infrastructure owners and operators implement cyber decoy systems that detect …

    New document

  4. Medium
    CISA and NIST release guidelines to protect federal cloud identity systems from token theft, forgery…

    CISA and NIST released Interagency Report (IR) 8587 providing comprehensive guidelines for federal agencies and cloud service providers to defend identity tokens and assertions used in …

    New document Action required

  5. Medium
    CISA releases updated Insider Threat Mitigation Guide addressing hybrid work and AI risks

    CISA released an updated version of its Insider Threat Mitigation Guide, originally published in 2020, to address evolving threats in the modern operational landscape. The updated …

    New version Action required

  6. Critical
    CISA publishes Logging Reference Architecture to guide federal agencies on enterprise logging standards

    CISA has published the Logging Reference Architecture, an outcome-driven guide developed with OMB and the CISO Council to help federal civilian executive branch (FCEB) agencies establish …

    New document Deadline 2026-11-18 Action required

  7. Medium
    CISA releases K-12 Cybersecurity Foundations Resource Package with guides and video series

    CISA released the K-12 Cybersecurity Foundations Resource Package on August 12, 2026, providing guides, videos, and supplemental materials to help K-12 schools and districts prevent and …

    New document Action required

That is the last 90 days. Sign in to read further back.

  1. in 9 days CISA Logging Reference Architecture: outcome-driven guidance for FCEB agencies to build Agency Logging Plans under OMB M-26-14
  2. BOD 26-04 issued; BOD 19-02 and BOD 22-01 revoked. Within 60 days of issuance agencies must update vulnerability management procedures (Phase II); within 180 days of issuance they must remediate within the Table 1 timelines and tag all externally reachable assets (Phase III)
  3. Emergency Directive ED 26-03: Mitigate Vulnerabilities in Cisco SD-WAN Systems
  4. BOD 26-02 issued. Agencies must decommission devices on CISA's EOS Edge Device List within 12 months of issuance, all identified end-of-support edge devices within 18 months, and continuously discover edge devices within 24 months
  5. CISA retires ten Emergency Directives issued between 2019 and 2024
Show 3 earlier dates
  1. Emergency Directive ED 26-01: Mitigate Vulnerabilities in F5 Devices
  2. Emergency Directive ED 25-03: Identify and Mitigate Potential Compromise of Cisco Devices
  3. BOD 25-01 deadline to implement mandatory SCuBA cloud configuration policies

Amendments

  1. BOD 26-04: Prioritizing Security Updates Based on Risk AmendmentCurrent text

    Consolidates vulnerability remediation rules and revokes BOD 19-02 and BOD 22-01. source

    More
    • Deadlines now depend on whether an asset is publicly exposed, whether the CVE is in the Known Exploited Vulnerabilities (KEV) catalog, whether exploitation can be automated, and the technical impact.
    • The most urgent cases require remediation within three days plus a forensic triage.
    • The KEV catalog itself continues.
  2. BOD 26-02: Mitigating Risk From End-of-Support Edge Devices Amendment

    Requires agencies to update or remove end-of-support edge devices: inventory devices on CISA's EOS Edge Device List within three months, decommission listed devices within 12 months and all EOS edge devices within 18 months. source

    More
    • Within 24 months agencies need a continuous discovery process.
  3. BOD 25-01: Implementing Secure Practices for Cloud Services Amendment

    Requires agencies to inventory in-scope cloud tenants, deploy CISA's SCuBA assessment tools with continuous reporting, and implement mandatory SCuBA secure configuration baselines. source

  4. BOD 23-02: Mitigating the Risk from Internet-Exposed Management Interfaces Amendment source

    Not confirmed by an official source yet.

  5. BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks Amendment source

    Not confirmed by an official source yet.

Show 3 older amendments
  1. BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities Amendment

    Established the Known Exploited Vulnerabilities catalog and required agencies to remediate listed vulnerabilities. source

    More
    • Revoked on 10 June 2026 by BOD 26-04.
  2. BOD 20-01: Develop and Publish a Vulnerability Disclosure Policy Amendment source

    Not confirmed by an official source yet.

  3. BOD 19-02: Vulnerability Remediation Requirements for Internet-Accessible Systems Amendment

    Remediation deadlines for internet-accessible systems. source

    More
    • Revoked on 10 June 2026 by BOD 26-04.

Who it applies to

Binding Operational Directives and Emergency Directives are compulsory for Federal Civilian Executive Branch agencies; CISA says organizations should use the KEV catalog in their vulnerability prioritization.

Federal civilian agencies
Binding Operational Directives and Emergency Directives are compulsory for Federal Civilian Executive Branch agencies. source source
Not covered
They do not cover national security systems or certain systems operated by the Department of War or the Intelligence Community. source
Everyone else
CISA says organizations should use the KEV catalog as an input to their vulnerability management prioritization framework. source

How compliance is assessed

Agencies report to CISA as each directive specifies.

BOD 26-04
Agencies report to CISA as each directive specifies: under BOD 26-04, automated KEV status reporting through the CDM dashboard (or manual reports every two weeks) and quarterly attestation of public IP addresses and domains. source
BOD 26-02
Under BOD 26-02, agencies submit inventories and decommission reports on CISA templates. source

Enforcement and penalties

Agencies are required by statute to comply, and CISA reports cross-agency status.

Statutory duty
Federal agencies are required to comply with these directives under 44 U.S.C. § 3554(a)(1)(B)(ii). source source
Oversight
CISA tracks progress and reports cross-agency status to the Secretary of Homeland Security, the Director of OMB and the National Cyber Director. source

Documents

  1. Law text CISA Cybersecurity Directives (current BODs and EDs)
  2. Law text BOD 26-04: Prioritizing Security Updates Based on Risk
  3. Guidance BOD 26-04: Implementation Guidance
  4. Guidance Known Exploited Vulnerabilities Catalog
  5. Guidance Secure by Design
Show 1 more document
  1. Law text Directives archive (revoked and closed directives)

Frequently asked questions

What is the latest CISA Binding Operational Directive?

BOD 26-04, "Prioritizing Security Updates Based on Risk", issued 10 June 2026. It revokes BOD 19-02 and BOD 22-01 and sets risk-based remediation timelines using the KEV catalog. source

Is BOD 22-01 still in effect?

No. BOD 26-04 revoked BOD 22-01 on 10 June 2026. The Known Exploited Vulnerabilities catalog that BOD 22-01 created continues, and BOD 26-04 uses it to set deadlines. source

Do CISA directives apply to private companies?

No. Binding Operational and Emergency Directives are compulsory only for Federal Civilian Executive Branch agencies. source

Verified against official sources on 18 October 2026. We monitor the official sources for this framework. Watching since 10 September 2026. Subscribe to CISA (RSS)