Nullify

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Product Security Terms

BOD 22-01

NT
Tim Thacker
November 14, 2026

What Is
BOD 22-01
?

BOD 22-01 was a CISA binding operational directive, issued on November 3, 2021, that created the Known Exploited Vulnerabilities (KEV) catalog and required US federal civilian agencies to fix listed vulnerabilities by set deadlines. CISA revoked it in June 2026, when BOD 26-04 replaced it.

Also known as:

Binding Operational Directive 22-01, CISA BOD 22-01, KEV directive

What BOD 22-01 Required

BOD 22-01, "Reducing the Significant Risk of Known Exploited Vulnerabilities", told federal civilian agencies to remediate every vulnerability in the new KEV catalog by its due date. The default deadlines were two weeks for vulnerabilities with CVE IDs assigned from 2021 onward and six months for older CVEs, and agencies had to report their status to CISA.

Why It Mattered Beyond Government

The directive only bound federal agencies, but the KEV catalog it created became a widely used signal for prioritization. Many private-sector teams adopted "is it in KEV?" as a trigger for faster remediation, and many vulnerability tools display KEV status next to CVSS and EPSS.

BOD 26-04 Replaced BOD 22-01

On June 10, 2026, CISA issued BOD 26-04, "Prioritizing Security Updates Based on Risk", which supersedes and revokes BOD 22-01 and BOD 19-02. The KEV catalog continues, but deadlines now depend on four factors:

  • Public exposure. Whether the vulnerable asset can be reached from the internet.
  • KEV status. Whether the CVE is in the Known Exploited Vulnerabilities catalog.
  • Exploit automation. Whether an attacker can automate every step of the exploit.
  • Technical impact. Whether exploitation gives partial or total control of the asset.

Timelines range from 3 days, plus forensic triage in the worst cases, to 14 days, 60 days or the next scheduled system upgrade for the lowest-risk combinations.

What This Means for Security Teams

The shift from one deadline for all KEVs to risk-based timelines mirrors what many private-sector programs already do: combine exploitation evidence with exposure and impact instead of severity alone. Teams that copied BOD 22-01's two-week window into their own SLAs may want to revisit those policies against BOD 26-04.

How Nullify Helps

Nullify moves actively exploited vulnerabilities and zero-days affecting your stack to the top of the backlog, checks whether the vulnerable code is reachable and writes a validated fix for the owner to review. Stalled fixes are escalated in Slack against your SLA, and reports show MTTR and SLA compliance. See how Nullify prioritizes and fixes findings.

Key Takeaways

  • BOD 22-01 created the CISA KEV catalog and set federal remediation deadlines in 2021.
  • Default deadlines were two weeks for newer CVEs and six months for CVEs assigned before 2021.
  • CISA revoked it in June 2026; BOD 26-04 now sets risk-based timelines.
  • BOD 26-04 weighs exposure, KEV status, exploit automation and technical impact.

Read More About
BOD 22-01

Reduce MTTR

See Nullify in Action

Nullify puts exploited, reachable vulnerabilities first and gets the fix merged on time.

See how to reduce MTTR

Reduce your vulnerability backlog and lower your MTTR

The AI harness that finds, proves and fixes vulnerabilities across your codebase.

Book a demo