Remediate, mitigate or accept: the Decision Table

Thirteen situations, each with the decision, the deadline, who signs and the record to keep (read 19 Nov 2026). Published guidance points to remediation in 3, mitigation now with a dated fix in 7, a dated exception in 2 and verify-then-close in 1. CISA BOD 26-04 grants federal agencies no waiver.

  1. RemediateCovered here
  2. Mitigate now, fix laterCovered here
  3. Accept with a dated exceptionCovered here

The 13 situations on the bar

CISA KEV catalog 2026.11.18: what the required action asks for, 1786 entries, feed read 19 Nov 2026.
CISA KEV required actions by wording, catalog 2026.11.18, 1786 entriesRequired action contains "apply updates" (any wording): 917 of 1786Required action contains "apply updates" (any wording)917Exact text: apply updates per vendor instructions: 893 of 1786Exact text: apply updates per vendor instructions893Contains "discontinue" (any wording): 815 of 1786Contains "discontinue" (any wording)815Contains "mitigations" (any wording): 791 of 1786Contains "mitigations" (any wording)791Exact text: mitigations per BOD 22-01 cloud guidance, or discontinue: 323 of 1786Exact text: mitigations per BOD 22-01 cloud guidance, or discontinue323Exact text: mitigations per vendor instructions, or discontinue: 260 of 1786Exact text: mitigations per vendor instructions, or discontinue260Exact text: mitigations per BOD 26-04, with forensic triage: 169 of 1786Exact text: mitigations per BOD 26-04, with forensic triage169Contains end-of-life wording (any wording): 83 of 1786Contains end-of-life wording (any wording)83Bar length: share of all 1786 entries. Wordings overlap.

Downloads: Decision Table CSV, Decision Table JSON.

The 13 situations

Decision is the response the cited text points to most directly. It is not an order of preference. Deadline is a date or interval a source sets, and the cell says so where none does. Who signs names the role a source gives. Each linked situation page quotes the rule, works one real CVE through it and says when the usual answer is wrong. The sources for each linked row are named on its page.

Decision Table, 13 situations. Sources: CISA BOD 26-04 and its implementation guidance, CISA BOD 26-02, FedRAMP Consolidated Rules for 2026, PCI SSC FAQs 1046 and 1597, NIST SP 800-40 Rev. 4 and SP 800-37 Rev. 2. Read 19 Nov 2026.
SituationDecisionDeadlineWho signsRecord to keep
A patch exists, the flaw is on the KEV catalog and the asset is internet-reachableRemediateFederal: 3 days from the KEV listing or the agency's own detection, whichever comes first; 14 days where exploitation is not automatable and control is partial. Forensic triage rides with the 3-day rows for total controlNo one for a federal agency: CISA issues no waivers. Elsewhere, the risk ownerClock start, fix date, forensic triage report
Exploited or severe, and the vendor has no patch yetMitigate now, fix laterMitigation at once. NIST: set and enforce schedules for patch deployment and for mitigation removal. A KEV entry keeps its due dateThe risk owner. On a federal system the authorizing official accepts what remainsMitigation, its removal date, planned patch date
A patch would break a critical systemMitigate now, fix laterThe next outage window after testing. On a federal KEV entry the due date standsThe risk owner for the delay. No one for a federal KEV entryRegression result, outage window, interim control
The software is end of lifeRemediate (replace or remove)Federal edge devices under BOD 26-02 (issued 5 Feb 2026): identified end-of-support devices decommissioned within 18 months, by 5 Aug 2027. Elsewhere, the replacement date you setThe authorizing official or risk owner, for any SA-22 exceptionReplacement date, isolation evidence, SA-22 reason
Not reachable, not on the KEV catalog, not automatableAccept with a dated exceptionFix on system upgrade: the next scheduled major upgrade or rebuild. The timeline restarts when exposure, KEV status or automation changesThe risk owner, within stated tolerance. In BOD 26-04 scope the timeline is the ruleExposure basis, the upgrade, the conditions that reopen it
SaaS or a managed service you cannot patchMitigate now, fix laterThe provider's fix. FedRAMP providers must categorize a flaw not mitigated or remediated within 192 days of evaluation as acceptedThe provider records it. The agency authorizing official signs any agency POA&MProvider notice, your configuration changes, provider status date
A control already sits in frontMitigate now, fix laterA fix date written the day the control goes in. A KEV due date still stands; FedRAMP's 192 days is the outer limitThe risk owner. In PCI DSS the QSA judges the controlControl, test date, exposure value, fix date
The asset is scheduled to be retiredAccept with a dated exceptionThe decommission date, no later. On a federal KEV entry the due date standsThe risk owner. The authorizing official on a federal systemDecommission date, interim control, confirmation of removal
A PCI DSS system cannot meet a requirementMitigate now, fix laterCritical patches within one month of release (Requirement 6.3.3, PCI SSC FAQ 1597)The QSA judges a compensating control. PCI SSC does not approve oneAssessor's finding, corrective actions, targeted risk analysis
A medical or OT device cannot be patched on cycleMitigate now, fix laterNone set. NIST: reevaluate the alternatives to patching periodicallySecurity architects review the long-term mitigations in advance. The risk owner accepts what remainsApproved long-term methods, re-evaluation date, impact analysis
A federal agency cannot meet a KEV dateMitigate: remove the asset from the networkThe due date stands. Removing exposure moves the asset to another Table 1 rowNo one: CISA issues no waivers. Agencies contact CISA about special casesRemoval from the network, contact with CISA, new clock
Internal asset, patch exists, not on the KEV catalog, automatableRemediate60 days (Table 1 rows 13 and 14)No one for a federal agency. Elsewhere, the risk ownerClock start, 60-day fix date, reason for any exception
The scanner reports a flaw that is not thereVerify, then closeNone setNo risk is accepted. FedRAMP's legacy playbook holds a false positive that is not validated as pending approvalEvidence of absence, validator, closing date

Federal deadlines in BOD 26-04 Table 1

Most deadline cells above come from this table. CISA publishes it as an image; the rows below are transcribed from that image. Days are calendar days. In the directive's words, "The timelines for each asset are dynamic as facts change": removing a system from the internet changes "Publicly Exposed" from Yes to No and moves the asset to another row, while a new KEV listing shortens the timeline. The clock starts when CISA adds the flaw to the KEV catalog or the agency identifies it on an asset, whichever comes first.

BOD 26-04 Table 1, Remediation Timelines, transcribed 19 Nov 2026. Totals: 5 rows at 3 days (3 of them with forensic triage), 6 at 14 days, 3 at 60 days, 2 at fix on system upgrade.
RowPublicly exposedIn the KEVAutomatable by adversaryTechnical impactAgency timeline
1YesYesYesTotal3 days and forensic triage
2YesYesYesPartial3 days
3YesYesNoTotal3 days and forensic triage
4YesYesNoPartial14 days
5YesNoYesTotal3 days
6YesNoYesPartial14 days
7YesNoNoTotal14 days
8YesNoNoPartial60 days
9NoYesYesTotal3 days and forensic triage
10NoYesYesPartial14 days
11NoYesNoTotal14 days
12NoYesNoPartial14 days
13NoNoYesTotal60 days
14NoNoYesPartial60 days
15NoNoNoTotalFix on system upgrade
16NoNoNoPartialFix on system upgrade

The directive defines remediation as eliminating the vulnerability "through patching, decommissioning the system, or another action". "Fix on system upgrade" means remediation "the next time the vulnerable asset receives a scheduled major upgrade or rebuild". These two definitions are why the table treats retirement as a fix and a compensating control as a step.

Who signs depends on the rule that binds you

For a federal system under NIST's risk management framework, "The explicit acceptance of risk is the responsibility of the authorizing official and cannot be delegated to other officials within the organization." (SP 800-37 Rev. 2, Task R-4). For BOD 26-04 deadlines nobody signs: "CISA does not issue waivers or exceptions for actions required in cyber directives." (implementation guidance). In PCI DSS the entity proposes a compensating control and the assessor judges it: PCI SSC "is not able to approve specific configurations or compensating controls" (FAQ 1046). Everyone else decides inside its own tolerance: NIST SP 800-39 says organizations "determine acceptable degrees of residual risk based on organizational risk tolerance and the specific risk tolerances of particular decision makers". Titles for that last case are on the who may sign page.

KEV due dates since BOD 26-04

In catalog 2026.11.18 (1,786 entries), 169 entries were added on or after 10 Jun 2026, the date of BOD 26-04. For 131 of them the due date is 3 days after the add date and for 38 it is 14 days. None is at 60 days. The feed marks 108 of the 169 for forensic triage and 61 not. Counted from the CISA feed on 19 Nov 2026. How the older required-action wording splits is on the KEV required actions guide.

What the table does not decide

Only federal civilian agencies are bound by BOD 26-04. For everyone else CISA "strongly recommends all organizations review and monitor the KEV catalog and prioritize remediation of the listed vulnerabilities". FedRAMP's 2026 rules go further for cloud providers: "A fully mitigated vulnerability will still exist (with negligible risk) until it has been remediated." That is why mitigation is a step in most rows and the end state in none. Where a row ends in an exception, the risk acceptance form and the exception register hold the fields and the maximum durations page lists every limit found. The definitions behind the labels are in remediation versus mitigation. The table is also available as CSV and JSON.

Sources

Last reviewed