What is remediation in cyber security

Remediation in cyber security means eliminating the vulnerability: CISA BOD 26-04 (10 Jun 2026) says it is eliminated "through patching, decommissioning the system, or another action". FedRAMP adds that a remediated vulnerability is "no longer detected". In CISA's KEV feed of 19 Nov 2026, 893 of 1,786 entries carry the exact action "Apply updates per vendor instructions."

  1. RemediateThis page is about it
  2. Mitigate now, fix later
  3. Accept with a dated exception

The definition that deadlines use

BOD 26-04 states that "the vulnerability shall be remediated (that is, the vulnerability is eliminated through patching, decommissioning the system, or another action)". Footnote 8 says the use is consistent with DoD Instruction 8531.01, NIST SP 800-53 Rev. 5 and NIST SP 800-216 (BOD 26-04). NIST SP 800-216 words it as "The neutralization or elimination of a vulnerability or the likelihood of its exploitation". FedRAMP's 2026 definition adds the test: a remediated vulnerability "has been neutralized or eliminated and is no longer detected", and its rule text says "FedRAMP does not use the terms "mitigation" and "remediation" interchangeably" (FedRAMP definitions, VDR rules).

Older glossary wording is looser. The NIST glossary entry lists CNSSI 4009-2022 definitions of remediation as "The act of mitigating a vulnerability or a threat" and as "Actions taken to correct known deficiencies and weaknesses once a vulnerability has been identified". A contract or policy that borrows the first wording lets a mitigation count as remediation, so state which definition applies. The comparison with mitigation is in the difference guide.

What counts, and what does not

What the sources count as remediation, read 19 Nov 2026.
ActionCounts as remediation?Why
Vendor patch or upgrade installed and in effectYesEliminates the flaw in the code (BOD 26-04)
Software removedYesThe flaw is no longer present
System decommissionedYesNamed in the BOD 26-04 definition
Update installed but the scan still detects the flawNot yetFedRAMP: a remediated vulnerability is "no longer detected"
WAF or IPS ruleNoOWASP: a virtual patch "does not remove the underlying vulnerability"
System taken off the internetNoBOD 26-04 calls it a valid mitigation that changes the timeline
Finding closed as a false positiveNot a responseVerify and record; see false positive handling

Six steps, who does them and what each leaves behind

NIST SP 800-40 Rev. 4 Section 2.2 gives the life cycle of a software vulnerability response: know, plan, prepare, implement, verify, monitor. Applied to remediation:

Steps from NIST SP 800-40 Rev. 4 Sections 2.2 and 2.3, owners and records as this site's practice, read 19 Nov 2026.
StepUsual ownerRecord it leavesHow it usually fails
1. Know the asset is affectedVulnerability managementFinding with product, version, asset and dateStale inventory; SP 800-40 says inventories updated "monthly or quarterly" by scan is a model that "should no longer be used"
2. Choose remediationSystem owner with securityDecision: remediate, mitigate or accept, with the reasonA mitigation chosen with no fix date; track it in a plan of action and milestones
3. PrepareChange manager, system ownerTested update, change ticket, windowSP 800-40 names the trade-off: testing "decreases the risk of operational disruption but increases the window of opportunity for attackers"
4. ImplementSystem administratorInstall log, new versionInstalled but not in effect: SP 800-40 lists restarting software and rebooting the platform as steps that make a patch take effect
5. VerifySecurity analystRescan result showing the finding no longer detected, scan ID, dateChecking the installer's log instead of the scanner; SP 800-40 asks that a patch be shown "installed successfully and taken effect"
6. Keep watching, then closeVulnerability managementClose note with the scan ID; monitoring ruleRollback: SP 800-40 lists a patch uninstalled, an unpatched version restored from backup, and a device reset to a vulnerable factory default

A worked case: CVE-2026-20320 in Cisco BroadWorks

Cisco's advisory cisco-sa-bworks-xxe-uwUd7CEt, first published 19 Aug 2026, rates the flaw High (CVSS base 7.5): an unauthenticated, remote attacker could read sensitive configuration information. It affects four products, BroadWorks Application Delivery Platform, Application Server, Profile Server and Xtended Services Platform, on releases earlier than RI.2026.07, and Cisco states that there are no workarounds. CISA added it to the KEV catalog on 10 Nov 2026, 83 days after the advisory, with a due date of 24 Nov 2026, 14 days later. On 12 Nov Cisco revised the advisory to say exploitation was known, and on 13 Nov corrected it to say only that the CVE was added to the KEV catalog.

With no workaround, the KEV action leaves two paths: install the fixed release, or, in the feed's words, "discontinue use of the product if mitigations are unavailable". An operator running an affected Application Server on 19 Nov 2026 has this schedule. The dates after 19 Nov are the example's plan.

Example schedule against the advisory of 19 Aug 2026 and the KEV due date of 24 Nov 2026.
DateStepOwnerRecord
19 Nov 2026Find every affected BroadWorks server; note release and exposureVulnerability managementFinding list with versions
20 Nov 2026Approve the upgrade to RI.2026.07 and book the windowSystem owner, change managerChange ticket
21 Nov 2026Install RI.2026.07, restart as the release notes directSystem administratorInstall log, release shown after the change
23 Nov 2026Rescan; the finding reads as no longer detected; closeSecurity analystScan ID, close note
24 Nov 2026KEV due date, one day of marginClosed finding on file

If the window slips past 24 Nov, Cisco offers no workaround to hold the position, so the only interim step is taking the service out of reach. BOD 26-04 treats that as a mitigation that changes the timeline, not as remediation.

How the KEV wording changed after BOD 26-04

The KEV catalog (version 2026.11.18, 1,786 entries) shows the shift when its required-action field is counted. Counts were made on 19 Nov 2026 by text match on that field in the KEV feed: exact string match for the first row, case-insensitive match on "apply updates" and "mitigations" for the rest.

KEV required-action wording by date added, catalog 2026.11.18, counted 19 Nov 2026.
GroupEntriesRequired action wording
Added before 10 Jun 20261,617893 carry exactly "Apply updates per vendor instructions."; 24 more contain "apply updates" in another form
Added 10 Jun to 18 Nov 2026169All 169 begin "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04"; 108 are flagged for forensic triage
Whole catalog1,786917 contain "apply updates", all added before BOD 26-04; 791 contain "mitigations", of which 169 are the new wording

So the older entries are the ones that say "update", and the newer ones say "mitigations" even where the vendor ships a fix, as the Cisco case shows. Read the vendor advisory for whether a fixed release exists; do not infer it from the KEV wording.

Cases where the usual answer is wrong

  • Decommissioning counts. Retiring the system is remediation under BOD 26-04, so a scheduled retirement can close a finding without any patch, provided the date is kept (decommission row).
  • PCI DSS separates two words. PCI SSC FAQ 1597 defines "Resolved" as the entity "solves or fixes the vulnerability" and "Addressed" as the entity determining "whether to resolve the vulnerability or to mitigate the risk by addressing the vulnerability in another way (e.g., with a compensating control or by disabling a vulnerable service)". Critical and high-risk findings must be resolved; the rest need only be addressed.
  • A fix that waits on a vendor. Until the update exists, remediation is not available; the decision table and mitigation when no patch exists cover the interim step.

Sources

Last reviewed