Patch Management Policy

CISA BOD 26-04 remediation timelines

CISA Binding Operational Directive 26-04, issued 10 Jun 2026, revoked BOD 19-02 and BOD 22-01 and replaced them with a 16-row table: 3 days (three rows add forensic triage), 14 days, 60 days, or fix on system upgrade. FedRAMP reads the binding timelines as starting 7 Dec 2026. Table 1 was read on 19 Nov 2026.

Build a policy with CISA BOD 26-04

4.3 Patch windows

CISA BOD 26-04

SeverityWindow3143090180 daysClock startsSet by
Critical3 days, with forensic triageKEV listing or agency identification, whichever comes firstCISA BOD 26-04, Table 1, highest-risk rows
High14 daysKEV listing or agency identification, whichever comes firstCISA BOD 26-04, Table 1, 14-day rows
Medium60 daysKEV listing or agency identification, whichever comes firstCISA BOD 26-04, Table 1, 60-day rows

Framework clauses, read 19 Nov 2026:

  • CISA BOD 26-04: Required action 6 and Table 1: Remediation Timelines: 3 days (with forensic triage for the highest-risk rows), 14 days, 60 days, or fix on system upgrade, depending on Table 1

What the directive replaced

BOD 26-04 states that it "supersedes and hereby revokes BOD 19-02" (15 calendar days for critical and 30 for high findings on internet-accessible systems) and BOD 22-01 (two weeks for Known Exploited Vulnerabilities with a CVE ID assigned in 2021 or later, six months for older ones). Both pages now carry the word Revoked and are dated 10 Jun 2026 in CISA's directive list. The old figures survive only as history in the Patch Window Table.

The directive "consolidates and clarifies vulnerability remediation guidelines for federal agencies." It does not use the severity labels of the two older directives. It uses four yes-or-no inputs instead, listed below.

The four inputs and the clock

  • Publicly exposed: yes if the asset is "accessible to unauthenticated or untrusted entities via public networks, such as the internet, regardless of its physical or logical location." If any one of several methods finds it exposed, the value is Yes.
  • In the KEV: the CVE ID has an entry in CISA's Known Exploited Vulnerabilities Catalog; the criteria for inclusion are unchanged.
  • Automatable by adversary: defined as documented by CISA's Vulnrichment program (the page points to the CERTCC/SSVC project on GitHub).
  • Technical impact: total control means the exploit "gives the adversary total control over the behavior of the software, including if the exploit reliably reveals log-in credentials"; partial control is everything less, and a denial-of-service attack counts as limited control.

Days are calendar days. The timeline begins when either CISA adds the vulnerability to the KEV Catalog or the agency identifies it on an asset and updates the CDM dashboard, "whichever event occurs first." The clock is not fixed: removing an asset from the internet changes Publicly Exposed from Yes to No and moves the required timeline back, while a new KEV listing shortens it.

Table 1to policy 4.3

Table 1, all 16 rows

BOD 26-04, Appendix A, Table 1: Remediation Timelines. CISA publishes the table as an image; every row was read from the image and checked against CISA's text on 19 Nov 2026. CISA reassesses the table once per fiscal year.
RowPublicly exposedIn the KEVAutomatable by adversaryTechnical impactTimeline (calendar days)
1YesYesYesTotal control3 days and forensic triage
2YesYesYesPartial control3 days
3YesYesNoTotal control3 days and forensic triage
4YesYesNoPartial control14 days
5YesNoYesTotal control3 days
6YesNoYesPartial control14 days
7YesNoNoTotal control14 days
8YesNoNoPartial control60 days
9NoYesYesTotal control3 days and forensic triage
10NoYesYesPartial control14 days
11NoYesNoTotal control14 days
12NoYesNoPartial control14 days
13NoNoYesTotal control60 days
14NoNoYesPartial control60 days
15NoNoNoTotal controlFix on system upgrade
16NoNoNoPartial controlFix on system upgrade

Counting the rows: three rows carry 3 days with forensic triage, two carry 3 days, six carry 14 days, three carry 60 days and two carry fix on system upgrade. Every asset that is in the KEV and publicly exposed has a 3 or 14 day limit; no row sets 60 days or later for a publicly exposed asset that is in the KEV.

"Forensic triage" means the agency completes remediation or mitigation within the three days and also checks whether the asset is already compromised, following the Forensic Triage Guidance in the implementation guide. "Fix on system upgrade" means remediation at the next scheduled major upgrade or rebuild, unless conditions change.

Table 1to policy 4.3

Phases and the date the table binds

  • Phase I, effective immediately: update vulnerability management policies; assign roles; set validation, enforcement, tracking and reporting; monitor the KEV Catalog; report KEV status through the CDM dashboard (agencies not fully automated report manually every two weeks); continue Cyber Hygiene scanning.
  • Phase II, within 60 days of issuance: update processes to support ongoing remediation based on the CVE database and the KEV Catalog.
  • Phase III, within 180 days of issuance: remediate each vulnerability "no later than the timelines set forth in Table 1" and tag every externally reachable asset with organization, environment, exposure and asset type.

FedRAMP's public notice NTC-0014 puts dates on the phases: by 7 Aug 2026 agency policies must support ongoing remediation, and by 7 Dec 2026 agencies "must begin evaluating and remediating vulnerabilities following the timelines in BOD 26-04." That is why FedRAMP's own deadline is also 7 Dec 2026.

What a policy must write to meet it

  1. State the four inputs by name and say who sets each one for an asset (the page says CISA's Cyber Hygiene service, the CDM program or third-party scanners may supply publicly exposed).
  2. Copy the 16-row table or reference it by version, and say what happens when CISA changes it at its yearly reassessment.
  3. Say that days are calendar days and that the clock starts at KEV listing or first identification on an asset, whichever is earlier.
  4. Define forensic triage for the 3-day rows by pointing to CISA's guidance, and name who performs it.
  5. Define remediation the way the directive does: eliminated "through patching, decommissioning the system, or another action", consistent with DoD Instruction 8531.01, NIST SP 800-53 Rev. 5 and NIST SP 800-216.
  6. Name the enforcement and tracking steps the directive requires of agency policy: validation, enforcement, internal tracking and reporting to CISA on request.

A private-sector policy that borrows the four inputs still needs an owner for each one; the severity and patch window policy section shows where that fits. NIST's account of the older two-week rule is in NIST SP 800-40, and the dates are in dates to know.

Evidence the text names

The directive asks for a copy of agency vulnerability management policies and procedures "if requested by CISA", automated reporting of KEV status through the CDM dashboard (or a manual report every two weeks), a machine-readable asset report to CISA every seven days for agencies not fully automated, and a quarterly attestation of publicly exposed IP addresses and domain names through the Cyber Hygiene scope change process.

Scope matters before copying any number into a private-sector policy. The directive applies to agency assets in a federal information system and, unless the procurement contract says so, not to contractors. For cloud offerings with a FedRAMP certification, agencies work through the FedRAMP program office.

Sources

Last reviewed 19 Nov 2026