# Remediation vs Mitigation > Remediation vs mitigation in cybersecurity: five questions about one finding return remediate, mitigate now and fix later, or accept with a dated exception. ## Decide - [Remediation vs Mitigation in Cybersecurity: Decision Tool](https://remediationvsmitigation.com/index.md): Remediation vs mitigation in cybersecurity: five questions about one finding return remediate, mitigate now and fix later, or accept with a dated exception. ## Decision Table - [Decision Table: Remediate, Mitigate or Accept by Situation](https://remediationvsmitigation.com/decision-table/index.md): 13 situations with the decision, the deadline, who signs and the record to keep, from CISA BOD 26-04 Table 1, FedRAMP, PCI SSC and NIST. Read 19 Nov 2026. - [A Compensating Control Is in Front: Why a Fix Date Stays](https://remediationvsmitigation.com/decision-table/compensating-control-in-front/index.md): A restricted management interface covers the flaw. Six statements from four sources on what a control buys, worked on PAN-OS CVE-2026-0322, 14 to 17 Oct 2026. - [Decommission Date Set: An Exception That Ends on the Date](https://remediationvsmitigation.com/decision-table/decommission-scheduled/index.md): An asset retiring on a known date still has a finding. When an exception to that date holds, worked on CVE-2026-85880 with the 22 Sep 2026 KEV due date. - [End-of-Life Software: Replace, Isolate or Accept With Dates](https://remediationvsmitigation.com/decision-table/end-of-life-software/index.md): No patch will ever ship. The BOD 26-02 timetable to 5 Aug 2027, NIST SA-22 exceptions, 83 KEV entries counted, and CVE-2026-111497 on Node.js 20 worked through. - [Internal Asset, Not on the KEV, Automatable: 60 Days](https://remediationvsmitigation.com/decision-table/internal-asset-not-kev-moderate/index.md): Unexposed asset, patch out, CVE not in the KEV but automatable: BOD 26-04 rows 13 and 14 give 60 days. Langflow CVE-2026-9198: 18 Sep became 7 Aug 2026. - [Exploited Flaw, No Patch Yet: Mitigate and Set Two Dates](https://remediationvsmitigation.com/decision-table/kev-no-patch-yet/index.md): KEV-listed flaw, no fix for your version: apply the vendor mitigation, set a patch date and a removal date. FortiMail CVE-2026-104286, 1 Oct to 19 Nov 2026. - [KEV Entry, Patch Out, Internet-Exposed: 3 or 14 Days](https://remediationvsmitigation.com/decision-table/kev-patch-available-exposed/index.md): Exposed asset, flaw on the CISA KEV catalog, patch available: BOD 26-04 Table 1 rows 1 to 4, a GitLab case with 20 Oct and 1 Nov dates, and the record to keep. - [Not Exposed, Not on the KEV, Not Automatable: Accept](https://remediationvsmitigation.com/decision-table/not-reachable-low-risk/index.md): CISA BOD 26-04 rows 15 and 16 say fix on system upgrade. Worked on CVE-2026-16723 (fastjson, 23 Jul 2026), with the three tests and the record to keep. - [OT and Medical Devices You Cannot Patch: Mitigate, Review](https://remediationvsmitigation.com/decision-table/ot-medical-cannot-patch/index.md): NIST SP 800-40 Rev. 4 section 3.5.4 and 21 U.S.C. 360n-2 on devices that wait for the maker. Worked on Siemens SSA-724261 (OT) and a medical-device request. - [A Patch Would Break a Critical System: Mitigate, Then Fix](https://remediationvsmitigation.com/decision-table/patch-breaks-critical-system/index.md): NIST SP 800-40 Rev. 4 accepts testing and outage windows; CISA grants no waivers. Worked on PHP CVE-2026-109618: fix 21 Oct 2026, KEV due 29 Oct 2026. - [SaaS You Cannot Patch: Mitigate and Track the Vendor](https://remediationvsmitigation.com/decision-table/saas-cannot-patch/index.md): A worked SaaS case, BeyondTrust CVE-2026-102764, 29 Aug to 16 Oct 2026: who owes what, which tenant records to review, and when vendor proof closes it. ## Compensating Controls Register - [Access Restriction as a Compensating Control: PAN-OS](https://remediationvsmitigation.com/compensating-controls/access-restriction/index.md): One jump box in front of a management interface moved CVE-2026-0322 from 8.6 to 8.5 on Palo Alto's scale. When access restriction counts, its cost and record. - [Application Allow-Listing as a Compensating Control](https://remediationvsmitigation.com/compensating-controls/application-allow-listing/index.md): Allow-listing stops a flaw that needs a new program to run, not one in an approved program. NIST CM-7(5), a four-CVE test, audit vs enforced events, a record. - [Configuration Change as a Mitigation: Cisco ASA Case](https://remediationvsmitigation.com/compensating-controls/configuration-change/index.md): A setting can mitigate a flaw if it removes a precondition. Cisco's CVE-2026-76418 mitigation, the read-back that catches the wrong fix, cost and record. - [Disable a Vulnerable Feature: When It Counts as Mitigation](https://remediationvsmitigation.com/compensating-controls/disable-feature-or-service/index.md): Turning off a feature, service or port can mitigate a KEV flaw. FortiMail IBE (CVE-2026-104286) worked through with exact settings, cost, checks and record. - [EDR Rule as a Compensating Control: Coverage](https://remediationvsmitigation.com/compensating-controls/edr-rule/index.md): An EDR rule mitigates only on hosts with a healthy agent and a blocking action. PHP2Shell (CVE-2026-109618): a vendor prevention claim, CISA SIGMA rule, record. - [Increased Monitoring as a Compensating Control](https://remediationvsmitigation.com/compensating-controls/increased-monitoring/index.md): Monitoring prevents nothing. CISA's PHP2Shell SIGMA rule (CVE-2026-109618) worked through: eight match branches, log sources, retention, tests, a record. - [IPS Signature as a Mitigation: When It Counts](https://remediationvsmitigation.com/compensating-controls/ips-signature/index.md): An IPS signature mitigates only in prevent mode, inline, on current content. PAN-OS Threat IDs 510046 and 510047 (CVE-2026-0322) worked through, with cost. - [Network Segmentation as a Mitigation: Cisco ISE Case](https://remediationvsmitigation.com/compensating-controls/network-segmentation/index.md): Cisco named infrastructure ACLs as the only mitigation for ISE CVE-2026-76460 (CVSS 10.0). Costs, the access.log review Cisco lists, verification and a record. - [Remove Internet Exposure as a Mitigation: What It Buys](https://remediationvsmitigation.com/compensating-controls/remove-internet-exposure/index.md): Taking a product off the internet changes its BOD 26-04 clock for some KEV entries and not others. Table 1 pairs worked on four real CVEs, with records. - [WAF Rule as a Virtual Patch: Atlassian Case and Limits](https://remediationvsmitigation.com/compensating-controls/waf-rule/index.md): A WAF rule counts as a mitigation only in block mode on every route. Atlassian's CVE-2026-21589 rule, its cost, a dated plan, and what to record. ## Risk acceptance - [Exception Register: 15 Columns, States and Blank CSV](https://remediationvsmitigation.com/exception-register/index.md): A complete exception register: 15 columns, a filled CVE-2026-65660 row, two status fields, FedRAMP's six states, a blank CSV header and a monthly review. - [Risk Acceptance Form: Free Template With 15 Fields](https://remediationvsmitigation.com/risk-acceptance-form/index.md): A risk acceptance form for security findings: 15 fields, what goes in each and the NIST, FedRAMP, CISA or PCI SSC wording that asks for it. Read 19 Nov 2026. - [Risk Acceptance Form Example: Filled-In Worked Sample](https://remediationvsmitigation.com/risk-acceptance-form/example/index.md): A filled-in risk acceptance form for real kernel flaw CVE-2026-80521 on six invented appliances: all 15 fields, dates worked out, and four ways a record fails. - [Maximum Duration of a Risk Acceptance: 9 Sources](https://remediationvsmitigation.com/risk-acceptance-form/maximum-durations/index.md): FedRAMP reports a finding as accepted after 192 days; NIST sets no maximum; CISA allows no waivers; PCI DSS 6.3.3 says one month. Nine sources, three expiries. - [Who Can Accept Risk: Signer by Standard (2026)](https://remediationvsmitigation.com/risk-acceptance-form/who-may-sign/index.md): Who may sign a risk acceptance: the NIST authorizing official, FedRAMP providers and agencies, a PCI assessor, and a sample rule for other organizations. ## Guides - [Accepting Risk on End-of-Life Software: Limits and Record](https://remediationvsmitigation.com/guides/accepting-risk-on-end-of-life-software/index.md): Write the exception for end-of-life software: SA-22 limits, six steps, a Node.js 20 case from 30 Apr to 10 Nov 2026, and 83 KEV end-of-life entries by vendor. - [Compensating Controls in Audit: What Assessors Check](https://remediationvsmitigation.com/guides/compensating-controls-in-audit/index.md): What assessors check in a compensating control: PCI SSC FAQs 1046, 1093, 1572 and 1597, a Node.js patch deadline worked to 20 Nov 2026, and a filled packet. - [Compensating Controls vs Mitigating Controls](https://remediationvsmitigation.com/guides/compensating-controls-vs-mitigating-controls/index.md): A mitigating control lowers a flaw's risk; a compensating control meets a stated requirement another way. Definitions quoted, plus a worked PCI DSS example. - [Difference Between Remediation and Mitigation in IT Security](https://remediationvsmitigation.com/guides/difference-between-remediation-and-mitigation/index.md): Remediation removes the vulnerability; mitigation lowers its risk while it stays. NIST, CISA BOD 26-04, FedRAMP and PCI SSC wording, with CVE-2026-0322 dated. - [Risk Exception Expiry: What Happens and How to Renew](https://remediationvsmitigation.com/guides/exception-expiry-and-renewal/index.md): What NIST and FedRAMP say about when a risk exception ends, and a worked case on CVE-2026-41709: a 90-day acceptance from 24 Aug 2026 ended by a KEV listing. - [Vulnerability False Positive: Close It With Evidence](https://remediationvsmitigation.com/guides/false-positive-handling/index.md): A false positive is a finding for a condition that is absent. NIST and FedRAMP definitions, a backported-kernel example dated 29 Oct 2026, and the record. - [FedRAMP Deviation Requests and Their 2026 Replacements](https://remediationvsmitigation.com/guides/fedramp-deviation-requests/index.md): FedRAMP's legacy false positive, risk adjustment and operational requirement requests field by field, the 2026 rules that replace them, and one worked finding. - [How Virtual Patching Works: Six Phases and a Real Rule](https://remediationvsmitigation.com/guides/how-virtual-patching-works/index.md): How a virtual patch is built, tested and removed: OWASP's six phases with owner and record, plus a log-only ModSecurity rule for CVE-2026-40217 with dates. - [Inherent vs Residual Risk on a Security Decision Record](https://remediationvsmitigation.com/guides/inherent-vs-residual-risk/index.md): Inherent risk is risk before management action; residual risk is what remains. Quoted definitions, phrase counts across NIST and FedRAMP, one worked record. - [KEV Required Action: Mitigate or Discontinue Use](https://remediationvsmitigation.com/guides/kev-required-actions-mitigate-or-discontinue/index.md): What CISA's KEV required action means and how many of 1,786 entries carry each kind (catalog 2026.11.18), with due dates by wording and two entries compared. - [Mitigating Risk vs Managing Risk, With a Worked Case](https://remediationvsmitigation.com/guides/mitigate-vs-manage-risk/index.md): Managing risk is NIST's process; mitigating is one response. One exploited Cisco ISE flaw, CVE-2026-76460, worked through four steps with owners and dates. - [SaaS Vulnerability Mitigation: Steps for the Customer](https://remediationvsmitigation.com/guides/mitigation-in-cloud-and-saas/index.md): In SaaS the vendor patches and you keep identity, data and settings. Five customer steps, 13 Microsoft October 2026 records marked no action, BOD 25-01 dates. - [Mitigation vs Remediation Wording in Vendor Advisories](https://remediationvsmitigation.com/guides/mitigation-vs-remediation-in-vendor-advisories/index.md): CSAF 2.0 categories and advisory wording: 50 Fortinet advisories and 50 Red Hat errata for one CVE counted, Cisco and Microsoft wording quoted, one record. - [POA&M Example: A Filled Plan of Action and Milestones Entry](https://remediationvsmitigation.com/guides/poam-plan-of-action-and-milestones/index.md): When a finding needs a POA&M entry, the fields an entry holds, and one entry filled for CVE-2026-19868 with five dated milestones and owners. Read 19 Nov 2026. - [Recording an Exception an Auditor Accepts: Eight Items](https://remediationvsmitigation.com/guides/recording-an-exception-an-auditor-accepts/index.md): Eight items to keep with every risk acceptance, what an assessor asks of each, weak and strong reason wording, and a record filled for CVE-2026-75604. - [What Is Remediation in Cyber Security? Steps and Proof](https://remediationvsmitigation.com/guides/remediation-in-cybersecurity/index.md): Remediation eliminates the vulnerability. CISA, NIST and FedRAMP wording, six steps with owner and record, and a worked case on CVE-2026-20320 with dates. - [Residual Risk After Mitigation: Define, Estimate, Record](https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/index.md): Residual risk is what is left after a control: NIST wording, the same-scale rule, and CVE-2024-10441 rated High, then Moderate, with the next reduction dated. - [Risk Acceptance Criteria: 7 Tests From NIST and CISA](https://remediationvsmitigation.com/guides/risk-acceptance-criteria/index.md): Seven tests a finding must pass before anyone signs a risk acceptance, each tied to NIST or CISA text and run on CVE-2026-0322 and CVE-2026-80521. - [Risk Acceptance vs Risk Avoidance in Cyber Security](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-avoidance/index.md): How NIST SP 800-39 separates accepting a risk from avoiding it, a decision table for findings, and a worked edge-device case under CISA BOD 26-02 dates. - [Risk Acceptance vs Risk Exception in Cyber Security](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-exception/index.md): A risk acceptance records who took on a risk; an exception records a departure from a rule. NIST wording, a decision table and two hosts for CVE-2026-80521. - [Risk Acceptance vs Risk Tolerance: Who Sets the Limit](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-tolerance/index.md): Tolerance is the limit set once; acceptance keeps one finding inside it. NIST SP 800-39 wording, a sorting table and a CVSS 7.8 Linux flaw that left it. - [Risk Transfer vs Risk Acceptance for Security Findings](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-transfer/index.md): Transfer shifts liability to another party; acceptance keeps it. NIST SP 800-39 on what transfer cannot do, a decision table and a Cisco ISE case from Sep 2026. - [Who Is the Risk Owner for a Security Finding?](https://remediationvsmitigation.com/guides/risk-owner/index.md): NIST IR 8286 defines the risk owner; SP 800-37 Rev. 2 names who signs acceptance. One role-by-question table and a SharePoint case, 11 Aug to 14 Oct 2026. - [Risk Register vs Exception Register: How They Link](https://remediationvsmitigation.com/guides/risk-register-vs-exception-register/index.md): A risk register tracks risks; an exception register tracks approved departures. NIST IR 8286's 12 elements against 15 columns, and one finding in both. - [How to Verify a Mitigation Works: Checks for 5 Real CVEs](https://remediationvsmitigation.com/guides/verifying-a-mitigation-works/index.md): The exact check for five mitigations from real CVEs (FortiMail, PAN-OS, Brotli, SonicOS, Atlassian), the FedRAMP re-check ladder and a drift case by date. - [When Virtual Patching Is Enough, and When It Is Not](https://remediationvsmitigation.com/guides/virtual-patching-and-when-it-is-enough/index.md): Seven conditions that decide whether a WAF or IPS rule is enough for a flaw, tested on FortiMail CVE-2026-104286, with the FedRAMP KEV and PCI resolved rules. - [Workaround vs Mitigation in Real Vendor Advisories](https://remediationvsmitigation.com/guides/workaround-vs-mitigation/index.md): How BerriAI, Cisco, F5, Fortinet, Palo Alto Networks, Red Hat and others word workaround and mitigation in 2026 advisories, quoted, with CISA's KEV wording. ## Reference - [Remediation and Mitigation Glossary: 31 Terms, Sourced](https://remediationvsmitigation.com/glossary/index.md): Thirty-one terms for remediation, mitigation and risk acceptance, each with the issuer's wording and a sourced example or note, from NIST, FedRAMP and CISA. ## About this site - [About Remediation vs Mitigation: Scope and Hosting](https://remediationvsmitigation.com/about/index.md): What the site covers (13 situations, 9 controls, a 15-field risk acceptance form), what it leaves out, how it is hosted, and its CC BY 4.0 license. - [Contact: editor@remediationvsmitigation.com](https://remediationvsmitigation.com/contact/index.md): One address for corrections, source suggestions and questions about reuse: editor@remediationvsmitigation.com. What to include so a report can be checked fast. - [Corrections Log: How to Report an Error](https://remediationvsmitigation.com/corrections/index.md): The corrections log for Remediation vs Mitigation (empty since the first edition, 19 Nov 2026), what counts as an error, what to send and what each entry shows. - [Editorial Policy: Sources, Labels and Corrections](https://remediationvsmitigation.com/editorial-policy/index.md): How facts get onto the site: primary text first, short exact quotes, a 19 Nov 2026 read date, labeled vendor claims, alphabetical vendors and a corrections log. - [Privacy: Cookies, Logs and the 400-Day Limit](https://remediationvsmitigation.com/privacy/index.md): The site sets no cookies, runs no analytics and loads no third-party scripts. CloudFront access logs sit in a private bucket and are deleted after 400 days. - [Terms of Use and CC BY 4.0 License](https://remediationvsmitigation.com/terms/index.md): Data and forms on Remediation vs Mitigation are licensed CC BY 4.0. The cite line to use, what stays under its issuer's terms, and how the pages may be quoted. ## Data - [Decision Table CSV](https://remediationvsmitigation.com/data/decision-table.csv): 13 situations - [Decision Table JSON](https://remediationvsmitigation.com/data/decision-table.json): with the decision tool rules - [Compensating Controls Register CSV](https://remediationvsmitigation.com/data/compensating-controls.csv): 11 controls - [Compensating Controls Register JSON](https://remediationvsmitigation.com/data/compensating-controls.json) - [Risk Acceptance Form fields CSV](https://remediationvsmitigation.com/data/risk-acceptance-form-fields.csv): 15 fields - [Risk Acceptance Form fields JSON](https://remediationvsmitigation.com/data/risk-acceptance-form-fields.json)