# Difference between remediation and mitigation

Canonical: https://remediationvsmitigation.com/guides/difference-between-remediation-and-mitigation/

Remediation eliminates a vulnerability; mitigation lowers the chance or impact of exploiting it while it remains. NIST SP 800-216 and CISA BOD 26-04 use the words this way, and FedRAMP's 2026 rules insist on it. NIST SP 800-40 Rev. 4 still counts patching as a form of mitigating risk.

## What each word means in the sources

The NIST glossary lists several definitions for each word, taken from different publications. Two of them settle the common meaning. SP 800-216 defines remediation as "The neutralization or elimination of a vulnerability or the likelihood of its exploitation" and mitigation as "The temporary reduction or lessening of the impact of a vulnerability or the likelihood of its exploitation" ([remediation](https://csrc.nist.gov/glossary/term/remediation), [mitigation](https://csrc.nist.gov/glossary/term/mitigation)).

The glossary also holds a definition that blurs the line: CNSSI 4009-2022 gives remediation as "The act of mitigating a vulnerability or a threat." A reader who finds that entry first will think the words are the same. A reader who finds SP 800-216 will think they are opposites. Both are in NIST's own glossary.

Five uses of the pair. Read 19 Nov 2026. Sources: NIST CSRC glossary, BOD 26-04, FedRAMP VDR rules, PCI SSC FAQ 1597.

| Source | Treats remediation as | Treats mitigation as |
|---|---|---|
| NIST SP 800-216 | Elimination of the vulnerability | Temporary reduction of impact or likelihood |
| CNSSI 4009-2022 | Correcting known deficiencies; also "the act of mitigating" | Not defined in the CNSSI remediation entry |
| CISA BOD 26-04 | Elimination through patching, decommissioning or another action | A valid action that can change the timeline, such as removing the system from the internet |
| FedRAMP 2026 rules | The end state; required for KEVs by the CISA due date | Leaves the vulnerability in place "with negligible risk" |
| PCI SSC FAQ 1597 | "Resolved" | Part of "addressed", for example a compensating control or disabling a vulnerable service |

## What each action changes

Five actions and the word each source uses. Read 19 Nov 2026.

| Action | What changes | What the sources call it |
|---|---|---|
| Install the vendor patch | The vulnerable code is replaced | Remediation in BOD 26-04; "Mitigate" in SP 800-40 Rev. 4 |
| Decommission the asset | The asset is gone | Remediation in BOD 26-04; "Avoid" in SP 800-40 Rev. 4 |
| Remove the system from the internet | The exposure value moves from Yes to No; the flaw stays | A "valid mitigation" in BOD 26-04 |
| Add a WAF rule | Matching requests are blocked | OWASP: the underlying vulnerability stays |
| Disable the vulnerable feature | The code path is not reachable; the software stays installed | Listed under Mitigate in SP 800-40 Rev. 4 |

The test that works in every row: after the action, does a scan or test of the asset still find the vulnerability? If not, it was remediated. If it does, it was mitigated, and the record needs a control, a test and an end date.

## Worked example: CVE-2026-0322 on a firewall

Palo Alto Networks published its advisory for the PAN-OS management interface flaw CVE-2026-0322 on 14 Oct 2026, with fixed builds for every affected train (for the 11.2 train, 11.2.13-h3 or 11.2.16 among them). The advisory states "No known workarounds exist for this issue" and also says "You can reduce the risk of exploitation by restricting access to a jump box that is the only system allowed to access the management interface" ([Palo Alto Networks](https://security.paloaltonetworks.com/CVE-2026-0322)). The vendor's own wording keeps the two apart: no workaround that removes the flaw, one step that lowers the risk.

CISA added the CVE to the KEV catalog on 14 Oct 2026 with a due date of 17 Oct 2026, three days later ([KEV feed, version 2026.11.18](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json)). Its required action reads "Apply mitigations in accordance with vendor instructions", although BOD 26-04 defines remediation as elimination, so a catalog entry may say mitigations where the directive's timeline means a fix. The table follows one invented firewall, fw-01, on build 11.2.13-h2.

Invented firewall, real CVE and dates. Palo Alto advisory and CISA KEV entry read 19 Nov 2026.

| Date | What happens | Word to record |
|---|---|---|
| 14 Oct 2026 | Advisory published and KEV entry added; due date 17 Oct 2026 | Detection; clock starts |
| 15 Oct 2026 | Management interface limited to one jump box; vendor rating 8.5 against 8.6; a scan of fw-01 still reports the flaw | Mitigation, with the control, a test and an end date |
| 16 Oct 2026 | fw-01 upgraded to 11.2.13-h3; `show system info` shows the new build; the next scan no longer reports the flaw | Remediation, 2 days after the KEV entry and 1 day before the due date |

Suppose instead the upgrade waits for a change window on 24 Oct 2026. The mitigation from 15 Oct stays valid, but the remediation is 7 days past the 17 Oct due date. A FedRAMP provider is told to remediate KEVs by the CISA due date "even if the vulnerability has been fully mitigated". For a federal agency, BOD 26-04 names one case where mitigation moves the timeline: removing the system from the internet changes the exposure value. A narrower restriction such as a jump box is not that example, so record which exposure value was used and why.

## Where NIST SP 800-40 Rev. 4 differs

SP 800-40 Rev. 4 names four responses to software vulnerabilities: accept, mitigate, transfer and avoid. Under Mitigate it lists "patching the vulnerable software, disabling a vulnerable feature, or upgrading to a newer software version". So in that publication patching is a way of mitigating risk, and a patch is one of "the only forms of risk response that can completely eliminate the vulnerabilities without removing functionality" ([NIST SP 800-40 Rev. 4](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf), Section 2.1).

Use the narrower meaning when a deadline is involved. FedRAMP's 2026 rules say "A fully mitigated vulnerability will still exist (with negligible risk) until it has been remediated" ([FedRAMP VDR](https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/)). The [decision tool](https://remediationvsmitigation.com/) applies that meaning, and the [Decision Table](https://remediationvsmitigation.com/decision-table/) shows it by situation. See also [remediation in cybersecurity](https://remediationvsmitigation.com/guides/remediation-in-cybersecurity/).

Vendors use the two words with their own senses. What is left after a mitigation is covered in [residual risk after mitigation](https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/), and the line between a mitigation and a requirement substitute is on [compensating controls vs mitigating controls](https://remediationvsmitigation.com/guides/compensating-controls-vs-mitigating-controls/).

## Sources

- NIST CSRC glossary, remediation: https://csrc.nist.gov/glossary/term/remediation (read 19 Nov 2026)
- NIST CSRC glossary, mitigation: https://csrc.nist.gov/glossary/term/mitigation (read 19 Nov 2026)
- NIST SP 800-40 Rev. 4, Section 2.1: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf (read 19 Nov 2026)
- CISA, BOD 26-04, Appendix A and footnote 8: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 19 Nov 2026)
- FedRAMP, VDR rules: https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/ (read 19 Nov 2026)
- PCI SSC FAQ 1597: https://www.pcisecuritystandards.org/faqs/1597 (read 19 Nov 2026)
- OWASP Virtual Patching Cheat Sheet: https://cheatsheetseries.owasp.org/cheatsheets/Virtual_Patching_Cheat_Sheet.html (read 19 Nov 2026)
- Palo Alto Networks advisory CVE-2026-0322: https://security.paloaltonetworks.com/CVE-2026-0322 (read 19 Nov 2026)
- CISA KEV feed, catalog version 2026.11.18: https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 19 Nov 2026)

Last reviewed 19 Nov 2026

## Related

- [What Is Remediation in Cyber Security? Steps and Proof](https://remediationvsmitigation.com/guides/remediation-in-cybersecurity/index.md)
- [Workaround vs Mitigation in Real Vendor Advisories](https://remediationvsmitigation.com/guides/workaround-vs-mitigation/index.md)
- [Decision Table: Remediate, Mitigate or Accept by Situation](https://remediationvsmitigation.com/decision-table/index.md)
- [Mitigation vs Remediation Wording in Vendor Advisories](https://remediationvsmitigation.com/guides/mitigation-vs-remediation-in-vendor-advisories/index.md)
- [Residual Risk After Mitigation: Define, Estimate, Record](https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/index.md)
- [Compensating Controls vs Mitigating Controls](https://remediationvsmitigation.com/guides/compensating-controls-vs-mitigating-controls/index.md)
