<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Remediation vs Mitigation</title>
<link>https://remediationvsmitigation.com/</link>
<description>Remediation vs mitigation in cybersecurity: five questions about one finding return remediate, mitigate now and fix later, or accept with a dated exception.</description>
<language>en-us</language>
<lastBuildDate>Thu, 19 Nov 2026 12:00:00 GMT</lastBuildDate>
<atom:link href="https://remediationvsmitigation.com/feed.xml" rel="self" type="application/rss+xml"/>
<item><title>7 Mar 2027: FedRAMP 2026 vulnerability rules: grace period ends</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Sun, 07 Mar 2027 12:00:00 GMT</pubDate><description>End of the grace period listed with the effective dates for the 2026 rules.</description></item>
<item><title>7 Dec 2026: FedRAMP 2026 vulnerability rules required for initial and ongoing Rev5 certification</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Mon, 07 Dec 2026 12:00:00 GMT</pubDate><description>Date from which the rules are required for new and maintained certifications. Optional adoption was allowed from 4 Jul 2026, so before 7 Dec 2026 the KEV rule VDR-TFR-KEV applied only to providers that adopted early.</description></item>
<item><title>Accepting Risk on End-of-Life Software: Limits and Record</title><link>https://remediationvsmitigation.com/guides/accepting-risk-on-end-of-life-software/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/accepting-risk-on-end-of-life-software/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Compensating Controls in Audit: What Assessors Check</title><link>https://remediationvsmitigation.com/guides/compensating-controls-in-audit/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/compensating-controls-in-audit/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Compensating Controls vs Mitigating Controls</title><link>https://remediationvsmitigation.com/guides/compensating-controls-vs-mitigating-controls/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/compensating-controls-vs-mitigating-controls/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Difference Between Remediation and Mitigation in IT Security</title><link>https://remediationvsmitigation.com/guides/difference-between-remediation-and-mitigation/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/difference-between-remediation-and-mitigation/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Risk Exception Expiry: What Happens and How to Renew</title><link>https://remediationvsmitigation.com/guides/exception-expiry-and-renewal/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/exception-expiry-and-renewal/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Vulnerability False Positive: Close It With Evidence</title><link>https://remediationvsmitigation.com/guides/false-positive-handling/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/false-positive-handling/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>FedRAMP Deviation Requests and Their 2026 Replacements</title><link>https://remediationvsmitigation.com/guides/fedramp-deviation-requests/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/fedramp-deviation-requests/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>FedRAMP's legacy false positive, risk adjustment and operational requirement requests field by field, the 2026 rules that replace them, and one worked finding.</description></item>
<item><title>How Virtual Patching Works: Six Phases and a Real Rule</title><link>https://remediationvsmitigation.com/guides/how-virtual-patching-works/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/how-virtual-patching-works/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Inherent vs Residual Risk on a Security Decision Record</title><link>https://remediationvsmitigation.com/guides/inherent-vs-residual-risk/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/inherent-vs-residual-risk/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>Inherent risk is risk before management action; residual risk is what remains. Quoted definitions, phrase counts across NIST and FedRAMP, one worked record.</description></item>
<item><title>KEV Required Action: Mitigate or Discontinue Use</title><link>https://remediationvsmitigation.com/guides/kev-required-actions-mitigate-or-discontinue/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/kev-required-actions-mitigate-or-discontinue/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Mitigating Risk vs Managing Risk, With a Worked Case</title><link>https://remediationvsmitigation.com/guides/mitigate-vs-manage-risk/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/mitigate-vs-manage-risk/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>SaaS Vulnerability Mitigation: Steps for the Customer</title><link>https://remediationvsmitigation.com/guides/mitigation-in-cloud-and-saas/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/mitigation-in-cloud-and-saas/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Mitigation vs Remediation Wording in Vendor Advisories</title><link>https://remediationvsmitigation.com/guides/mitigation-vs-remediation-in-vendor-advisories/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/mitigation-vs-remediation-in-vendor-advisories/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>POA&amp;M Example: A Filled Plan of Action and Milestones Entry</title><link>https://remediationvsmitigation.com/guides/poam-plan-of-action-and-milestones/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/poam-plan-of-action-and-milestones/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>When a finding needs a POA&amp;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.</description></item>
<item><title>Recording an Exception an Auditor Accepts: Eight Items</title><link>https://remediationvsmitigation.com/guides/recording-an-exception-an-auditor-accepts/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/recording-an-exception-an-auditor-accepts/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>What Is Remediation in Cyber Security? Steps and Proof</title><link>https://remediationvsmitigation.com/guides/remediation-in-cybersecurity/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/remediation-in-cybersecurity/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Residual Risk After Mitigation: Define, Estimate, Record</title><link>https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Risk Acceptance Criteria: 7 Tests From NIST and CISA</title><link>https://remediationvsmitigation.com/guides/risk-acceptance-criteria/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/risk-acceptance-criteria/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Risk Acceptance vs Risk Avoidance in Cyber Security</title><link>https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-avoidance/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-avoidance/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Risk Acceptance vs Risk Exception in Cyber Security</title><link>https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-exception/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-exception/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Risk Acceptance vs Risk Tolerance: Who Sets the Limit</title><link>https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-tolerance/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-tolerance/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Risk Transfer vs Risk Acceptance for Security Findings</title><link>https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-transfer/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-transfer/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Who Is the Risk Owner for a Security Finding?</title><link>https://remediationvsmitigation.com/guides/risk-owner/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/risk-owner/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Risk Register vs Exception Register: How They Link</title><link>https://remediationvsmitigation.com/guides/risk-register-vs-exception-register/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/risk-register-vs-exception-register/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>How to Verify a Mitigation Works: Checks for 5 Real CVEs</title><link>https://remediationvsmitigation.com/guides/verifying-a-mitigation-works/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/verifying-a-mitigation-works/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>When Virtual Patching Is Enough, and When It Is Not</title><link>https://remediationvsmitigation.com/guides/virtual-patching-and-when-it-is-enough/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/virtual-patching-and-when-it-is-enough/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>Workaround vs Mitigation in Real Vendor Advisories</title><link>https://remediationvsmitigation.com/guides/workaround-vs-mitigation/</link><guid isPermaLink="false">https://remediationvsmitigation.com/guides/workaround-vs-mitigation/</guid><pubDate>Thu, 19 Nov 2026 12:00:00 GMT</pubDate><description>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.</description></item>
<item><title>24 Jun 2026: FedRAMP Consolidated Rules for 2026 launch</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Wed, 24 Jun 2026 12:00:00 GMT</pubDate><description>States that mitigation and remediation are not interchangeable, sets mitigate-or-remediate timeframes by impact, exposure and exploitability, says providers SHOULD remediate KEVs by the CISA date even if fully mitigated, and defines an accepted vulnerability as one not fully mitigated or remediated within 192 days of evaluation.</description></item>
<item><title>11 Jun 2026: First KEV catalog entry whose required action cites BOD 26-04</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Thu, 11 Jun 2026 12:00:00 GMT</pubDate><description>From this date new and re-labeled KEV entries tell agencies to apply mitigations and also follow BOD 26-04 and forensic triage guidance. Counted on 19 Nov 2026 from the live feed (2026.11.18, 1,786 entries): 169 entries whose requiredAction text contains &quot;BOD 26-04&quot;; the earliest dateAdded among them is 11 Jun 2026.</description></item>
<item><title>10 Jun 2026: CISA BOD 26-04: Prioritizing Security Updates Based on Risk; BOD 22-01 and BOD 19-02 revoked</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Wed, 10 Jun 2026 12:00:00 GMT</pubDate><description>Replaces fixed two-week KEV dates with a table of 3, 14 and 60 day timelines and 'fix on system upgrade', driven by exposure, KEV status, automation and impact. Keeps the KEV criteria. Defines remediation to include decommissioning.</description></item>
<item><title>25 Feb 2026: CISA Emergency Directive on Cisco SD-WAN issued (ED 26-03, updated 11 March 2026)</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Wed, 25 Feb 2026 12:00:00 GMT</pubDate><description>An example of an emergency directive that sets mitigation steps, inventory and hunt actions before patching; KEV entries for these products carry its text.</description></item>
<item><title>5 Feb 2026: CISA BOD 26-02: Mitigating Risk From End-of-Support Edge Devices</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Thu, 05 Feb 2026 12:00:00 GMT</pubDate><description>Sets decommissioning (not mitigation) as the end state for end-of-support edge devices at federal civilian agencies, with 12, 18 and 24 month steps.</description></item>
<item><title>31 Mar 2025: PCI DSS v4.x future-dated requirements become mandatory</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Mon, 31 Mar 2025 12:00:00 GMT</pubDate><description>The new requirements marked as recommended-only until this date took effect. PCI SSC confirmed v4.0.1 did not move the date.</description></item>
<item><title>31 Dec 2024: PCI DSS v4.0 retired</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Tue, 31 Dec 2024 12:00:00 GMT</pubDate><description>From this date v4.0.1 is the only active PCI DSS version.</description></item>
<item><title>11 Jun 2024: PCI DSS v4.0.1 published</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Tue, 11 Jun 2024 12:00:00 GMT</pubDate><description>A limited revision that keeps the 30-day critical-patch requirement and adds or deletes no requirements.</description></item>
<item><title>27 Jun 2022: FedRAMP POA&amp;M template gains BOD 22-01 due date and CVE columns</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Mon, 27 Jun 2022 12:00:00 GMT</pubDate><description>Tied each POA&amp;M line item to the KEV due date and CVE, so an open item can be checked against the federal date.</description></item>
<item><title>Apr 2022: NIST SP 800-40 Rev. 4 published</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Fri, 01 Apr 2022 12:00:00 GMT</pubDate><description>Names four risk responses to software vulnerabilities (accept, mitigate, transfer, avoid), counts patching as a form of mitigate, and adds emergency mitigation and unpatchable-asset plans.</description></item>
<item><title>3 Nov 2021: CISA BOD 22-01 issued; Known Exploited Vulnerabilities catalog begins</title><link>https://remediationvsmitigation.com/</link><guid isPermaLink="false">https://remediationvsmitigation.com/</guid><pubDate>Wed, 03 Nov 2021 12:00:00 GMT</pubDate><description>Gave federal agencies fixed remediation dates (two weeks, or six months for older CVEs) for exploited vulnerabilities, with removal from the network as the fallback. This is the first public rule that made 'fix by a date' the default for one list of findings.</description></item>
</channel>
</rss>
