Remediation vs mitigation in cybersecurity: a five-question tool that picks the response for one finding
Remediation vs mitigation in cybersecurity comes down to what is left afterward: remediation eliminates the vulnerability, mitigation leaves it in place and lowers exposure or impact. The tool below takes five answers about one finding and returns remediate, mitigate now and fix later, or accept with a dated exception, with the record to keep. Read 19 Nov 2026.
Mitigate now, fix later (no answers yet)Outcome for this finding
No answers yet, so each question reads the cautious way; the mapping table below shows how.
Rule 1: The vulnerability is exploited or severe and the vendor has not released a patch yet
NIST SP 800-40 Rev. 4 names emergency mitigation for this case and says to replace it with the permanent fix and remove the mitigation on a schedule. In the KEV feed, 791 of 1786 required actions mention mitigations, most often as 'apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable'.
Record to keep: what the sources say (read 19 Nov 2026)
- Section 3.4 maintenance scenarios, PDF page 20 SP 800-40r4 defines emergency mitigation as a temporary measure before a patch exists.
Emergency mitigation. This is the emergency procedure in a crisis situation, like those described above for the emergency patching scenario, to temporarily mitigate vulnerabilities before a patch is available.
Section 3.4 maintenance scenarios, PDF page 20 3 more sources for this row
- Section 3.5.3 The mitigation is meant to end: both dates are set and enforced.
Once a permanent fix, such as a patch, is available, the patch will need to be deployed and the mitigation removed. Schedules should be set and enforced for both patch deployment and mitigation removal.
Section 3.5.3 - Section 2.1 SP 800-40r4 lists a missing patch as a reason patching is not immediately viable.
A patch may not be available yet.
Section 2.1 - requiredAction field, catalog version 2026.11.18: 260 entries with this exact text KEV feed requiredAction text: the most common mitigation-or-discontinue wording, counted from the live feed.
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
requiredAction field, catalog version 2026.11.18: 260 entries with this exact text
- Section 3.5.3 The mitigation is meant to end: both dates are set and enforced.
Record to keep: fields for mitigate now, fix later
- Tracking identifier and finding reference (CVE ID, scanner finding ID): One internal ID for the exception, plus the CVE ID and scanner finding IDs it covers. (VER-RPT-AVI: Accepted Vulnerability Info)
- Time and source of the detection, and time evaluation completed: When and by what tool or report the finding was first seen, and when it was evaluated. (VER-RPT-AVI: Accepted Vulnerability Info)
- Affected asset or system, environment, and exposure: Hostnames or system IDs, prod or dev, public or internal, asset type. (Required Actions, Phase III, tags)
- Is it internet-reachable?: Yes or no, with the basis (reachability test, architecture). (VER-RPT-AVI: Accepted Vulnerability Info)
- Is it likely exploitable? Is it on the KEV list?: Likelihood of exploitation in this environment, KEV status, exploit automation. (VER-RPT-AVI: Accepted Vulnerability Info)
- Mitigating factors and compensating controls in place: Each control, its owner, how it was verified and when. Link to the controls register entry. (General POA&M Guidance)
- Planned corrective tasks, resources, milestones and scheduled completion dates: What will fix it, who owns each task, what it needs, and the dates. (Task A-6)
- Update trigger and review cadence: What causes the record to be reopened: scan, audit, monitoring finding, change to exposure, new KEV listing. (CA-5 b)
- Vendor dependency: product name, last vendor check-in date, evidence of vendor status: When the fix depends on a vendor patch that does not exist yet. (General POA&M Guidance)
Rule 1: The vulnerability is exploited or severe and the vendor has not released a patch yet
NIST SP 800-40 Rev. 4 names emergency mitigation for this case and says to replace it with the permanent fix and remove the mitigation on a schedule. In the KEV feed, 791 of 1786 required actions mention mitigations, most often as 'apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable'.
Record to keep: what the sources say (read 19 Nov 2026)
- Section 3.4 maintenance scenarios, PDF page 20 SP 800-40r4 defines emergency mitigation as a temporary measure before a patch exists.
Emergency mitigation. This is the emergency procedure in a crisis situation, like those described above for the emergency patching scenario, to temporarily mitigate vulnerabilities before a patch is available.
Section 3.4 maintenance scenarios, PDF page 20 3 more sources for this row
- Section 3.5.3 The mitigation is meant to end: both dates are set and enforced.
Once a permanent fix, such as a patch, is available, the patch will need to be deployed and the mitigation removed. Schedules should be set and enforced for both patch deployment and mitigation removal.
Section 3.5.3 - Section 2.1 SP 800-40r4 lists a missing patch as a reason patching is not immediately viable.
A patch may not be available yet.
Section 2.1 - requiredAction field, catalog version 2026.11.18: 260 entries with this exact text KEV feed requiredAction text: the most common mitigation-or-discontinue wording, counted from the live feed.
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
requiredAction field, catalog version 2026.11.18: 260 entries with this exact text
- Section 3.5.3 The mitigation is meant to end: both dates are set and enforced.
Record to keep: fields for mitigate now, fix later
- Tracking identifier and finding reference (CVE ID, scanner finding ID): One internal ID for the exception, plus the CVE ID and scanner finding IDs it covers. (VER-RPT-AVI: Accepted Vulnerability Info)
- Time and source of the detection, and time evaluation completed: When and by what tool or report the finding was first seen, and when it was evaluated. (VER-RPT-AVI: Accepted Vulnerability Info)
- Affected asset or system, environment, and exposure: Hostnames or system IDs, prod or dev, public or internal, asset type. (Required Actions, Phase III, tags)
- Is it internet-reachable?: Yes or no, with the basis (reachability test, architecture). (VER-RPT-AVI: Accepted Vulnerability Info)
- Is it likely exploitable? Is it on the KEV list?: Likelihood of exploitation in this environment, KEV status, exploit automation. (VER-RPT-AVI: Accepted Vulnerability Info)
- Mitigating factors and compensating controls in place: Each control, its owner, how it was verified and when. Link to the controls register entry. (General POA&M Guidance)
- Planned corrective tasks, resources, milestones and scheduled completion dates: What will fix it, who owns each task, what it needs, and the dates. (Task A-6)
- Update trigger and review cadence: What causes the record to be reopened: scan, audit, monitoring finding, change to exposure, new KEV listing. (CA-5 b)
- Vendor dependency: product name, last vendor check-in date, evidence of vendor status: When the fix depends on a vendor patch that does not exist yet. (General POA&M Guidance)
Federal civilian agencies must remediate within 3 days (14 days if exploitation is not automatable and control is only partial). CISA urges every other organization to prioritize remediation of KEV entries. Mitigation alone, such as removing the system from the internet, changes the timeline but is not the end state.
Record to keep: what the sources say (read 19 Nov 2026)
- Table 1: Remediation Timelines (BOD 26-04, read from the published table image) Row 1 of Table 1 in BOD 26-04: publicly exposed, in the KEV, automatable by an adversary, total control: remediate in 3 calendar days and carry out forensic triage. Rows 2, 3 and 4 (exposed and in the KEV) are 3 days, 3 days with forensic triage, and 14 days.
Yes | Yes | Yes | Total control | 3 days & forensic triage
Table 1: Remediation Timelines (BOD 26-04, read from the published table image) 3 more sources for this row
- cisa.gov CISA's advice to organizations that are not bound by the directive.
CISA strongly recommends all organizations review and monitor the KEV catalog and prioritize remediation of the listed vulnerabilities
cisa.gov - Appendix A, notes to Table 1 Quoted in the text above. Appendix A, notes to Table 1
- VDR-TFR-KEV Quoted in the text above. VDR-TFR-KEV
- cisa.gov CISA's advice to organizations that are not bound by the directive.
Record to keep: fields for remediate
- Tracking identifier and finding reference (CVE ID, scanner finding ID): One internal ID for the exception, plus the CVE ID and scanner finding IDs it covers. (VER-RPT-AVI: Accepted Vulnerability Info)
- Time and source of the detection, and time evaluation completed: When and by what tool or report the finding was first seen, and when it was evaluated. (VER-RPT-AVI: Accepted Vulnerability Info)
- Affected asset or system, environment, and exposure: Hostnames or system IDs, prod or dev, public or internal, asset type. (Required Actions, Phase III, tags)
- Is it likely exploitable? Is it on the KEV list?: Likelihood of exploitation in this environment, KEV status, exploit automation. (VER-RPT-AVI: Accepted Vulnerability Info)
- Planned corrective tasks, resources, milestones and scheduled completion dates: What will fix it, who owns each task, what it needs, and the dates. (Task A-6)
BOD 26-04 Table 1 rows 13 and 14 give 60 days; rows 15 and 16 give 'fix on system upgrade' when exploitation is also not automatable. SP 800-39 says lower-priority risks may be addressed later rather than ignored.
Record to keep: what the sources say (read 19 Nov 2026)
- Table 1: Remediation Timelines (BOD 26-04, read from the published table image) Row 13 of Table 1: not exposed, not in the KEV, automatable, total control.
No | No | Yes | Total control | 60 days
Table 1: Remediation Timelines (BOD 26-04, read from the published table image) 1 more source for this row
- Task 3-3, Chapter 3 Lower priority means later, not never.
This does not necessarily mean that the lower-priority risks would not be addressed. Rather, it could mean that fewer resources might be directed at the lower-priority risks (at least initially), or that the lower-priority risks would be addressed at a later time.
Task 3-3, Chapter 3
- Task 3-3, Chapter 3 Lower priority means later, not never.
Record to keep: fields for remediate
- Tracking identifier and finding reference (CVE ID, scanner finding ID): One internal ID for the exception, plus the CVE ID and scanner finding IDs it covers. (VER-RPT-AVI: Accepted Vulnerability Info)
- Time and source of the detection, and time evaluation completed: When and by what tool or report the finding was first seen, and when it was evaluated. (VER-RPT-AVI: Accepted Vulnerability Info)
- Affected asset or system, environment, and exposure: Hostnames or system IDs, prod or dev, public or internal, asset type. (Required Actions, Phase III, tags)
- Is it likely exploitable? Is it on the KEV list?: Likelihood of exploitation in this environment, KEV status, exploit automation. (VER-RPT-AVI: Accepted Vulnerability Info)
- Planned corrective tasks, resources, milestones and scheduled completion dates: What will fix it, who owns each task, what it needs, and the dates. (Task A-6)
Sources treat a working control as a valid response but not as the fix. NIST allows accepting risk by relying on existing controls. FedRAMP 2026 says a fully mitigated vulnerability still exists until remediated, and requires KEVs to be remediated by the due date anyway. OWASP says a virtual patch does not remove the underlying vulnerability.
Record to keep: what the sources say (read 19 Nov 2026)
- Section 2.1 SP 800-40r4 on Accept.
Accept the risk from vulnerable software as is, such as by relying on existing security controls to prevent vulnerability exploitation
Section 2.1 3 more sources for this row
- VDR-CSO-RES notes FedRAMP 2026 separates mitigation from remediation.
A fully mitigated vulnerability will still exist (with negligible risk) until it has been remediated.
VDR-CSO-RES notes - Definition: Virtual Patching OWASP on virtual patching.
It does not remove the underlying vulnerability.
Definition: Virtual Patching - VER-EVA-EIR notes FedRAMP 2026: a deflecting control changes the exposure rating.
once this prevention is in place the vulnerability should no longer be considered an internet-reachable vulnerability.
VER-EVA-EIR notes
- VDR-CSO-RES notes FedRAMP 2026 separates mitigation from remediation.
Record to keep: fields for mitigate now, fix later
- Tracking identifier and finding reference (CVE ID, scanner finding ID): One internal ID for the exception, plus the CVE ID and scanner finding IDs it covers. (VER-RPT-AVI: Accepted Vulnerability Info)
- Time and source of the detection, and time evaluation completed: When and by what tool or report the finding was first seen, and when it was evaluated. (VER-RPT-AVI: Accepted Vulnerability Info)
- Affected asset or system, environment, and exposure: Hostnames or system IDs, prod or dev, public or internal, asset type. (Required Actions, Phase III, tags)
- Is it internet-reachable?: Yes or no, with the basis (reachability test, architecture). (VER-RPT-AVI: Accepted Vulnerability Info)
- Is it likely exploitable? Is it on the KEV list?: Likelihood of exploitation in this environment, KEV status, exploit automation. (VER-RPT-AVI: Accepted Vulnerability Info)
- Mitigating factors and compensating controls in place: Each control, its owner, how it was verified and when. Link to the controls register entry. (General POA&M Guidance)
- Planned corrective tasks, resources, milestones and scheduled completion dates: What will fix it, who owns each task, what it needs, and the dates. (Task A-6)
- Update trigger and review cadence: What causes the record to be reopened: scan, audit, monitoring finding, change to exposure, new KEV listing. (CA-5 b)
- Vendor dependency: product name, last vendor check-in date, evidence of vendor status: When the fix depends on a vendor patch that does not exist yet. (General POA&M Guidance)
BOD 26-04 Table 1 sets 'Fix on system upgrade' for rows 15 and 16 (not exposed, not in the KEV, not automatable): the fix waits for the next scheduled major upgrade or rebuild, and the timeline restarts if conditions change.
Only BOD 26-04 and FedRAMP set this as a rule for federal systems. Other organizations set their own dates under NIST SP 800-39 and 800-53 RA-7.
Record to keep: what the sources say (read 19 Nov 2026)
- Table 1: Remediation Timelines (BOD 26-04, read from the published table image) Row 15 of Table 1: not exposed, not in the KEV, not automatable, total control.
No | No | No | Total control | Fix on system upgrade
Table 1: Remediation Timelines (BOD 26-04, read from the published table image) 3 more sources for this row
- Appendix A, notes to Table 1 Defines the deferred outcome.
Fix on system upgrade means that, unless conditions change as described in item (e) above, the vulnerability should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild.
Appendix A, notes to Table 1 - Task 3-1, Chapter 3 page 42 NIST SP 800-39 on when acceptance fits.
Risk acceptance is the appropriate risk response when the identified risk is within the organizational risk tolerance.
Task 3-1, Chapter 3 page 42 - VER-EVA-ELX notes FedRAMP 2026 on evaluating exploitability before responding.
The simple reality is that most traditional vulnerabilities discovered by scanners or during assessment are not likely to be exploitable
VER-EVA-ELX notes
- Appendix A, notes to Table 1 Defines the deferred outcome.
Record to keep: fields for accept with a dated exception
- Tracking identifier and finding reference (CVE ID, scanner finding ID): One internal ID for the exception, plus the CVE ID and scanner finding IDs it covers. (VER-RPT-AVI: Accepted Vulnerability Info)
- Time and source of the detection, and time evaluation completed: When and by what tool or report the finding was first seen, and when it was evaluated. (VER-RPT-AVI: Accepted Vulnerability Info)
- Affected asset or system, environment, and exposure: Hostnames or system IDs, prod or dev, public or internal, asset type. (Required Actions, Phase III, tags)
- Is it internet-reachable?: Yes or no, with the basis (reachability test, architecture). (VER-RPT-AVI: Accepted Vulnerability Info)
- Is it likely exploitable? Is it on the KEV list?: Likelihood of exploitation in this environment, KEV status, exploit automation. (VER-RPT-AVI: Accepted Vulnerability Info)
- Estimated impact if exploited: Impact rating using the organization's scale (FedRAMP uses a Potential Agency Impact N-rating). (VER-RPT-AVI: Accepted Vulnerability Info)
- Reason the finding is accepted instead of fixed or mitigated: The business, technical or legal constraint, in plain words. (VER-RPT-AVI: Accepted Vulnerability Info)
- Mitigating factors and compensating controls in place: Each control, its owner, how it was verified and when. Link to the controls register entry. (General POA&M Guidance)
- Planned corrective tasks, resources, milestones and scheduled completion dates: What will fix it, who owns each task, what it needs, and the dates. (Task A-6)
- Update trigger and review cadence: What causes the record to be reopened: scan, audit, monitoring finding, change to exposure, new KEV listing. (CA-5 b)
- Residual risk statement and reference to risk tolerance: What risk remains after the controls, compared to the organization's stated tolerance. (Task R-3)
- Approver name, title and date of decision: The person with authority to accept the risk, signing and dating the decision. (Task R-4)
- Expiry date (termination date) of the exception: A date after which the exception lapses unless renewed by the approver. (Task R-4)
Rule 7: A patch is available but it would disrupt or has broken a business-critical system
Guidance accepts delay for testing and outage windows and expects an interim control plus a dated plan. NIST names a flawed or disruptive patch as a reason for emergency mitigation. For KEV entries on federal systems, CISA says it grants no waivers and the fallback is to remove the asset from the network.
Record to keep: what the sources say (read 19 Nov 2026)
- Section 2.1 SP 800-40r4 accepts testing and outage windows as reasons not to patch immediately.
The organization may need to wait for a scheduled outage window, perform testing first, update other software that interacts with the software to be patched, or train employees on new features or interfaces.
Section 2.1 3 more sources for this row
- Section 3.4 A problematic patch is a stated reason for emergency mitigation.
Emergency mitigations are sometimes needed because of issues with a patch.
Section 3.4 - SI-2 b SI-2 requires testing for side effects before installation.
Test software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation;
SI-2 b - Implementation guidance FAQ Federal KEV deadlines have no waiver path.
CISA does not issue waivers or exceptions for actions required in cyber directives.
Implementation guidance FAQ
- Section 3.4 A problematic patch is a stated reason for emergency mitigation.
Record to keep: fields for mitigate now, fix later
- Tracking identifier and finding reference (CVE ID, scanner finding ID): One internal ID for the exception, plus the CVE ID and scanner finding IDs it covers. (VER-RPT-AVI: Accepted Vulnerability Info)
- Time and source of the detection, and time evaluation completed: When and by what tool or report the finding was first seen, and when it was evaluated. (VER-RPT-AVI: Accepted Vulnerability Info)
- Affected asset or system, environment, and exposure: Hostnames or system IDs, prod or dev, public or internal, asset type. (Required Actions, Phase III, tags)
- Is it internet-reachable?: Yes or no, with the basis (reachability test, architecture). (VER-RPT-AVI: Accepted Vulnerability Info)
- Is it likely exploitable? Is it on the KEV list?: Likelihood of exploitation in this environment, KEV status, exploit automation. (VER-RPT-AVI: Accepted Vulnerability Info)
- Mitigating factors and compensating controls in place: Each control, its owner, how it was verified and when. Link to the controls register entry. (General POA&M Guidance)
- Planned corrective tasks, resources, milestones and scheduled completion dates: What will fix it, who owns each task, what it needs, and the dates. (Task A-6)
- Update trigger and review cadence: What causes the record to be reopened: scan, audit, monitoring finding, change to exposure, new KEV listing. (CA-5 b)
- Vendor dependency: product name, last vendor check-in date, evidence of vendor status: When the fix depends on a vendor patch that does not exist yet. (General POA&M Guidance)
The 13 situations, by where guidance points
solid: guidance points here light: also allowed empty: not named by the sources
Remediate3
- A patch exists, the vulnerability is on the CISA KEV catalog, and the asset is reachable from the internet
- The product or version is end of life or end of support, so no patch will ever ship
- A patch exists, the asset is not exposed to the internet, the vulnerability is not on the KEV list, and exploitation is automatable
Mitigate now, fix later7
- The vulnerability is exploited or severe and the vendor has not released a patch yet
- A patch is available but it would disrupt or has broken a business-critical system
- The affected product is third-party SaaS or a managed service whose code you cannot patch
- A control already sits in front of the vulnerable component (WAF rule, segmentation, access restriction)
- A PCI DSS in-scope system cannot meet a requirement as written (for example a patch cannot be installed in time)
- A medical or OT/ICS device cannot be patched on the usual cycle (manufacturer approval, safety certification, uptime)
- A federal civilian agency cannot meet a KEV remediation date
Accept with a dated exception2
Verify, then close (not one of the three)1
- The scanner reports a vulnerability that does not exist on the system
The source behind each of the five questions
The tool takes one finding at a time. It runs in the browser and sends nothing. On load, with no answers, each question reads cautiously, Rule 1 matches, and the tool shows Mitigate now, fix later. The questions above are the ones published guidance asks, in the order that settles most findings fastest; each is listed here with its source.
- Question 1, vendor fix. NIST SP 800-40 Rev. 4 lists "A patch may not be available yet" as a reason a patch cannot go in immediately (NIST SP 800-40 Rev. 4).
- Question 2, reachability. Exposure is one of four inputs to CISA's BOD 26-04 Table 1, with KEV status, whether an adversary can automate exploitation, and technical impact (BOD 26-04).
- Question 3, KEV status. BOD 26-04 states that "Known exploited vulnerabilities are a frequent attack vector for malicious cyber actors", and makes KEV listing one of its four inputs; the clock starts when CISA adds the entry. The feed held 1,786 entries in catalog version 2026.11.18, read 19 Nov 2026 (BOD 26-04; KEV feed).
- Question 4, fix in time. SP 800-40 Rev. 4, Section 2.1, accepts waiting for an outage window, testing first, or updating interacting software (NIST SP 800-40 Rev. 4).
- Question 5, tested control. SP 800-40 Rev. 4, Section 2.2, step 3c, says to "ensure they are functioning as intended" when additional controls are deployed (NIST SP 800-40 Rev. 4).
The answers land on 6 of the 13 situations in the Decision Table: no fix yet, a KEV item that can be fixed in time, a non-KEV item that can, a control already in front, an unreachable flaw outside the KEV catalog, and a patch that breaks a critical system. The other seven are reached from the Decision Table directly: end-of-life software, SaaS that cannot be patched, a scheduled decommission, a PCI requirement that cannot be met, an OT or medical device, a federal agency that cannot meet a KEV date, and a false positive. The tool's usual answer is wrong in three cases. It does not ask whether exploitation can be automated, which BOD 26-04 treats as an input, so a non-KEV flaw with a public automated exploit needs a faster response than the tool returns. It does not ask whether you are a federal civilian agency, for whom the KEV date is binding. It does not ask what the product is, so end-of-life, SaaS and OT cases need your own reading of the matching rows in the Decision Table, listed at the foot of the rules table below. The rules table says where each rule assumes an answer. The method page explains how the answers pick a row.
One finding worked through
Four entries were added to the KEV catalog on 18 Nov 2026: Synology DiskStation Manager, BerriAI LiteLLM, Vanderbilt REDCap and Apache Axis. CVE-2024-10441, in Synology DiskStation Manager, has a due date of 21 Nov 2026, three days later, with forensic triage marked Yes. CVE-2026-40217, in BerriAI LiteLLM, has a due date of 2 Dec 2026, 14 days later, with forensic triage marked No. The REDCap and Axis entries are also due 21 Nov 2026 (KEV feed, catalog version 2026.11.18). The walk-through takes the Synology entry. The feed answers question 3; the other answers are assumptions that an asset owner replaces with facts.
| Question | Answer used | Basis |
|---|---|---|
| 1. Vendor fix exists? | Yes (assumed) | The entry's notes link Synology advisory Synology_SA_24_20; the owner confirms a fixed release exists |
| 2. Reachable from the internet? | Yes (assumed) | The owner's architecture drawing |
| 3. On the KEV catalog? | Yes | Added 18 Nov 2026, due 21 Nov 2026 |
| 4. Fix in before the due date? | No (assumed) | 21 Nov 2026 is a Saturday; the next change window is assumed to be 24 Nov 2026 |
| 5. Tested control in front? | Yes (assumed) | A tested access restriction on the management interface |
Rule 5 matches (fix yes, date missed, tested control yes), so the result is Mitigate now, fix later, on the row for a control already in front. The control goes into the record with its test date, the hosts it covers, the approver, and the date it comes off, which is after the fix lands on 24 Nov 2026. Had the control been untested, rule 7 would return the row for a patch that breaks a critical system, with the same response. The entry's required action is to apply mitigations per vendor instructions "or discontinue use of the product if mitigations are unavailable".
For a federal civilian agency the date stays 21 Nov 2026, and its KEV date row applies, not rule 5: CISA "does not issue waivers or exceptions for actions required in cyber directives" (implementation guidance). Outside that scope the KEV date is guidance, and FedRAMP providers have a separate rule, quoted in the section on the primary sources below. The dates page sets this entry's clocks side by side.
The three responses and the record to keep for each
| Response | What it means | Record to keep |
|---|---|---|
| Remediate | Eliminate the vulnerability through patching, decommissioning the system, or another action (BOD 26-04 wording). | Fixed version and date, the scan or test that no longer finds the flaw, the change ticket. |
| Mitigate now, fix later | A control reduces exposure or impact while the flaw stays in place. | Control and mode (block or log-only), test date and tester, hosts and routes covered, approver, the date the control comes off and the date the fix lands. |
| Accept with a dated exception | The residual risk stays under a signed decision with an end date. | Reason, residual risk against stated tolerance, controls in place, approver and date, expiry date, the event that reopens it. |
The mitigate record is the one most often missing a date. NIST SP 800-40 Rev. 4, Section 3.5.3, says "Schedules should be set and enforced for both patch deployment and mitigation removal." The Compensating Controls Register lists the evidence to keep for each of 11 controls. The Risk Acceptance Form holds the 15 fields of an exception, and the exception register tracks them to expiry.
Remediation and mitigation in the primary sources
NIST's glossary gives mitigation as "A decision, action, or practice intended to reduce the level of risk associated with one or more threat events, threat scenarios, or vulnerabilities" (SP 800-160 Vol. 2 Rev. 1) and as "The temporary reduction or lessening of the impact of a vulnerability or the likelihood of its exploitation" (SP 800-216) (NIST glossary, mitigation). Mitigation lowers risk and leaves the flaw in place; remediation removes it. The glossary has both wordings.
CISA's BOD 26-04 revoked BOD 22-01 on 10 Jun 2026. It sets 3, 14 or 60 calendar days, or "fix on system upgrade", from exposure, KEV status, automation and technical impact, and defines remediation as the vulnerability being "eliminated through patching, decommissioning the system, or another action" (BOD 26-04).
FedRAMP's 2026 rules go further on vocabulary: "A fully mitigated vulnerability will still exist (with negligible risk) until it has been remediated." Providers should remediate KEV entries by the CISA due date even when fully mitigated, and the rules are required for Rev5 certification from 7 Dec 2026 (FedRAMP VDR). The difference guide sets the definitions of each source side by side.
What the tool cannot settle
Some decisions belong to a named party. In PCI DSS, "QSAs are responsible to determine whether a compensating control is sufficient to meet the intent of a requirement" (PCI SSC FAQ 1046). PCI SSC also separates two words: critical vulnerabilities under Requirement 6.3.3 "must be resolved within one month of release", while a vulnerability that is "addressed" may be handled with a compensating control or by disabling a vulnerable service (PCI SSC FAQ 1597). In federal systems, "the authorizing official is the only person who can accept risk" (NIST SP 800-37 Rev. 2, Task R-3). How long an acceptance may run is on the maximum durations page, and who may sign is on the who may sign page.
How the five answers pick a row
| Rule | Vendor fix exists | Internet-reachable | On the KEV catalog | Fix in before due date | Tested control in front | Decision Table row | Guidance points to | Assumes |
|---|---|---|---|---|---|---|---|---|
| 1 | No | Any | Any | Any | Any | kev-no-patch-yet | Mitigate now, fix later | Nothing else is asked once there is no fix. The row is written for an exploited or severe flaw (its KEV example). For a finding outside the KEV catalog the response, mitigate now and fix later, is the same, but the row says nothing about a deadline: set the interim control and a dated plan from the finding's own exposure and impact, and record that it is not a KEV entry. |
| 2 | Yes | Any | Yes | Yes | Any | kev-patch-available-exposed | Remediate | The row is written for an asset reachable from the internet. Not reachable gives the same response, remediate; BOD 26-04 Table 1 sets that clock. |
| 3 | Yes | No | No | Yes | Any | internal-asset-not-kev-moderate | Remediate | Assumes exploitation is automatable, which the tool does not ask. If it is not, Table 1 gives fix on system upgrade. |
| 4 | Yes | Yes | No | Yes | Any | kev-patch-available-exposed | Remediate | No row covers a reachable flaw outside the KEV catalog. The nearest row is written for a KEV entry; the response is the same, remediate, and Table 1 sets the clock. |
| 5 | Yes | Any | Any | No | Yes | compensating-control-in-front | Mitigate now, fix later | Matches whatever the KEV and reachability answers are. |
| 6 | Yes | No | No | No | Any | not-reachable-low-risk | Accept with a dated exception | Assumes an adversary cannot automate exploitation, which the tool does not ask. |
| 7 | Yes | Any | Any | No | Any | patch-breaks-critical-system | Mitigate now, fix later | Catches a missed change window with no tested control: the row lists "an outage window is not available yet" as a signal, so the closest row is the patch-breaks-a-critical-system row, which has the same response, mitigate now and fix later. A federal civilian agency with a KEV date it cannot meet goes to the KEV date row in the Decision Table; the tool does not ask who you are. |
Rows the five questions do not reach: end-of-life-software; saas-cannot-patch; decommission-scheduled; pci-cannot-meet-requirement; ot-medical-cannot-patch; kev-due-date-cannot-be-met; false-positive.
Sources
- CISA, BOD 26-04, Table 1 and Appendix A, read 19 Nov 2026
- CISA, BOD 26-04 implementation guidance, FAQ, read 19 Nov 2026
- FedRAMP, Consolidated Rules 2026, Vulnerability Detection and Response, read 19 Nov 2026
- NIST SP 800-40 Rev. 4, Sections 2.1, 2.2, 3.5.3, read 19 Nov 2026
- NIST SP 800-37 Rev. 2, Task R-3, read 19 Nov 2026
- CISA KEV catalog JSON feed, catalogVersion 2026.11.18, read 19 Nov 2026
- PCI SSC FAQ 1046, read 19 Nov 2026
- PCI SSC FAQ 1597, read 19 Nov 2026
- NIST CSRC glossary, mitigation, read 19 Nov 2026
Last reviewed