{
 "name": "Remediation vs Mitigation: Compensating Controls Register",
 "edition": "2026-11-19",
 "license": "CC BY 4.0",
 "license_url": "https://creativecommons.org/licenses/by/4.0/",
 "cite": "Remediation vs Mitigation, Compensating Controls Register, edition 19 Nov 2026, https://remediationvsmitigation.com/compensating-controls/",
 "pci_dss_appendix_b": {
  "status": "not read",
  "reason": "PCI DSS v4.0.1 PDF (Appendix B compensating controls, Appendix C worksheet) is behind a click-through license agreement on docs-prv.pcisecuritystandards.org; it was not accepted or fetched on 2026-11-19. Public PCI SSC FAQs 1046, 1572 and 1597 and the v4.0.1 announcement were read instead.",
  "read": "2026-11-19",
  "faq_facts": [
   {
    "claim": "Who decides.",
    "quote": "QSAs are responsible to determine whether a compensating control is sufficient to meet the intent of a requirement during their review of all other controls in place to satisfy PCI DSS requirements.",
    "source": "https://www.pcisecuritystandards.org/faqs/1046",
    "read": "2026-11-19",
    "kind": "primary",
    "location": "FAQ 1046"
   },
   {
    "claim": "Definition of addressed.",
    "quote": "Addressed - the entity determines 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).",
    "source": "https://www.pcisecuritystandards.org/faqs/1597",
    "read": "2026-11-19",
    "kind": "primary",
    "location": "FAQ 1597"
   }
  ]
 },
 "unread": [
  "PCI DSS v4.0.1 PDF incl. Appendix B and C and customized approach (click-through license, not accepted)",
  "ISO/IEC 27005 public pages (iso.org HTTP 403)",
  "FDA medical device cybersecurity guidance (fda.gov URLs tried returned not found)",
  "Microsoft Security Update Guide current definitions (script-built page, no text)",
  "Akamai, OWASP Network Segmentation and Multifactor Authentication cheat sheets (listed in the OWASP index, not opened)"
 ],
 "rows": [
  {
   "id": "network-segmentation",
   "name": "Network segmentation or isolation",
   "control_kind": "mitigation",
   "what_it_changes": "Limits which systems and users can reach the vulnerable component, which shrinks the attack surface.",
   "what_it_does_not_fix": "The vulnerable code stays installed. Anything that can still reach the component, including a compromised neighbor inside the segment, can still exploit it.",
   "how_to_verify": [
    "From a host that should be blocked, try to open a connection to the component's address and port and record that it fails. This shows reachability is cut; it does not test the flaw.",
    "Review the firewall or segmentation rule set and the date of last change.",
    "Re-run the check after every network change that touches the segment."
   ],
   "evidence_to_keep": [
    "Rule export or screenshot with date",
    "Architecture or network diagram showing the boundary",
    "Connectivity check result (reachability only)",
    "Change ticket and approver",
    "Review date"
   ],
   "standard_ids": [
    "NIST SP 800-53 SC-7, SC-7(21)",
    "NIST SP 800-40r4 section 3.5.4",
    "PCI DSS Appendix B compensating control criteria"
   ],
   "sources": [
    {
     "claim": "800-53 text on isolating components.",
     "quote": "Isolating system components with boundary protection mechanisms provides the capability for increased protection of individual system components and to more effectively control information flows between those components.",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/SC-7.21",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "SC-7.21"
    },
    {
     "claim": "CISA lists isolation techniques for assets that cannot be updated.",
     "quote": "Depending on your environment, appropriate isolation techniques may include decommissioning, removal of the vulnerable software product, network segmentation, isolation, software-defined perimeters, and proxies.",
     "source": "https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Implementation guidance FAQ"
    },
    {
     "claim": "SP 800-40r4 names segmentation as a mitigation.",
     "quote": "using firewalls and network segmentation to isolate vulnerable assets, thus reducing the attack surface",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.1"
    },
    {
     "claim": "800-53A lists configuration records as examination material for boundary protection.",
     "quote": "system configuration settings and associated documentation",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/SC-7.21",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "SC-7 assessment method"
    }
   ],
   "notes": "SP 800-40r4 section 3.5.4 cites SP 800-207 micro-segmentation and software-defined perimeters for unpatchable assets.",
   "verification_basis": [
    {
     "claim": "SP 800-40r4 says to verify that a deployed control works.",
     "quote": "For deploying additional security controls, ensure they are functioning as intended.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3c"
    },
    {
     "claim": "SP 800-40r4 says to keep monitoring that the control stays in place.",
     "quote": "Make sure that the risk response continues to be in place: no one uninstalls the patch, deactivates the additional security controls, lets the cybersecurity insurance lapse, or restarts the decommissioned asset.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3d"
    }
   ],
   "changes": "Who can reach it"
  },
  {
   "id": "waf-rule",
   "name": "WAF rule or virtual patch",
   "control_kind": "mitigation",
   "what_it_changes": "Blocks or filters requests that match a known exploitation pattern before they reach the vulnerable application, without changing its code.",
   "what_it_does_not_fix": "The flaw stays in the code. Traffic the WAF does not inspect (other paths, internal callers, other protocols) and attack variants the rule does not recognize are not covered.",
   "how_to_verify": [
    "Use the vendor's or OWASP's test guidance to confirm the rule's block or log action.",
    "Test alternate encodings and other endpoints, as OWASP advises, before claiming coverage.",
    "Confirm the rule is in block mode, not log-only, and is attached to every route that reaches the component."
   ],
   "evidence_to_keep": [
    "Rule ID, version and mode (block or log)",
    "Test record with date and tester",
    "List of routes and hosts covered",
    "Change ticket and approver",
    "Date the rule is to be removed after the code or vendor fix"
   ],
   "standard_ids": [
    "OWASP Virtual Patching Cheat Sheet",
    "NIST SP 800-53 SC-7, SI-10",
    "PCI DSS Appendix B compensating control criteria"
   ],
   "sources": [
    {
     "claim": "OWASP definition of virtual patching.",
     "quote": "A security policy enforcement layer that detects and blocks matching exploitation attempts against a known vulnerability without changing the vulnerable code.",
     "source": "https://cheatsheetseries.owasp.org/cheatsheets/Virtual_Patching_Cheat_Sheet.html",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Definition: Virtual Patching"
    },
    {
     "claim": "OWASP on the limit of a virtual patch.",
     "quote": "A virtual patch reduces exposure only for traffic the enforcement layer inspects and attack variants its rules recognize.",
     "source": "https://cheatsheetseries.owasp.org/cheatsheets/Virtual_Patching_Cheat_Sheet.html",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Definition: Virtual Patching"
    },
    {
     "claim": "FedRAMP 2026 names filtering in front of the resource.",
     "quote": "The simplest way to prevent exploitation of internet-reachable vulnerabilities is to intercept, inspect, filter, sanitize, reject, or otherwise deflect triggering payloads before they are processed by the vulnerable resource",
     "source": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "VER-EVA-EIR notes"
    },
    {
     "claim": "Vendor documentation: a managed rule may be off by default, so check it is on.",
     "quote": "Some rules in the Cloudflare Managed Ruleset are disabled by default, intending to strike a balance between providing the right protection and reducing the number of false positives.",
     "source": "https://developers.cloudflare.com/waf/managed-rules/reference/cloudflare-managed-ruleset/",
     "read": "2026-11-19",
     "kind": "vendor",
     "location": "Cloudflare Managed Ruleset"
    },
    {
     "claim": "Vendor description of a managed ruleset for no-patch cases.",
     "quote": "It covers known attack techniques and zero-day vulnerabilities (newly discovered flaws with no available patch).",
     "source": "https://developers.cloudflare.com/waf/managed-rules/",
     "read": "2026-11-19",
     "kind": "vendor",
     "location": "Available managed rulesets"
    }
   ],
   "notes": "OWASP prefers allow-list (positive security) virtual patches and warns about exploit-specific rules.",
   "verification_basis": [
    {
     "claim": "SP 800-40r4 says to verify that a deployed control works.",
     "quote": "For deploying additional security controls, ensure they are functioning as intended.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3c"
    },
    {
     "claim": "SP 800-40r4 says to keep monitoring that the control stays in place.",
     "quote": "Make sure that the risk response continues to be in place: no one uninstalls the patch, deactivates the additional security controls, lets the cybersecurity insurance lapse, or restarts the decommissioned asset.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3d"
    }
   ],
   "changes": "Traffic that reaches it"
  },
  {
   "id": "ips-signature",
   "name": "IPS signature or filter",
   "control_kind": "mitigation",
   "what_it_changes": "Inspects network traffic and blocks traffic that matches a signature for the exploit of a specific vulnerability.",
   "what_it_does_not_fix": "Only traffic that passes through the sensor is covered. Signatures can be bypassed by variants, and an unknown flaw has no signature.",
   "how_to_verify": [
    "Confirm the signature or filter is enabled in prevent mode, not detect-only, on the sensor in the path.",
    "Confirm the sensor sees the traffic (inline placement, decryption where needed).",
    "Check the signature update date against the advisory date."
   ],
   "evidence_to_keep": [
    "Filter ID and action",
    "Sensor placement diagram",
    "Policy export with date",
    "Last signature update date",
    "Change ticket"
   ],
   "standard_ids": [
    "NIST SP 800-53 SI-4, SC-7",
    "PCI DSS Appendix B compensating control criteria"
   ],
   "sources": [
    {
     "claim": "OWASP lists an IPS appliance as a virtual patching tool.",
     "quote": "Intermediary devices such as a WAF or IPS appliance",
     "source": "https://cheatsheetseries.owasp.org/cheatsheets/Virtual_Patching_Cheat_Sheet.html",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Virtual Patching Tools"
    },
    {
     "claim": "Vendor documentation: detect-only mode is a setting, so verify the mode.",
     "quote": "Optional detect-only mode sets all protections to only detect to allow you to evaluate your profile",
     "source": "https://www.checkpoint.com/quantum/intrusion-prevention-system-ips/",
     "read": "2026-11-19",
     "kind": "vendor",
     "location": "Check Point IPS page"
    },
    {
     "claim": "Vendor claim.",
     "quote": "TippingPoint protects against vulnerabilities before vendor patches are available.",
     "source": "https://www.trendmicro.com/en_us/business/products/network/intrusion-prevention.html",
     "read": "2026-11-19",
     "kind": "vendor",
     "location": "Trend Micro TippingPoint page"
    },
    {
     "claim": "800-53 SI-4 discussion lists intrusion prevention systems.",
     "quote": "System monitoring capabilities are achieved through a variety of tools and techniques, including intrusion detection and prevention systems, malicious code protection software, scanning tools, audit record monitoring software, and network monitoring software.",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/SI-4",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "SI-4 discussion"
    }
   ],
   "notes": null,
   "verification_basis": [
    {
     "claim": "SP 800-40r4 says to verify that a deployed control works.",
     "quote": "For deploying additional security controls, ensure they are functioning as intended.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3c"
    },
    {
     "claim": "SP 800-40r4 says to keep monitoring that the control stays in place.",
     "quote": "Make sure that the risk response continues to be in place: no one uninstalls the patch, deactivates the additional security controls, lets the cybersecurity insurance lapse, or restarts the decommissioned asset.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3d"
    }
   ],
   "changes": "Traffic that reaches it"
  },
  {
   "id": "disable-feature-or-service",
   "name": "Disable the vulnerable feature, service or port",
   "control_kind": "mitigation",
   "what_it_changes": "Removes the code path or listener the exploit needs.",
   "what_it_does_not_fix": "The vulnerable software is still installed. Re-enabling the feature, an upgrade that resets the setting, or another path to the same code undoes the control.",
   "how_to_verify": [
    "On the host, run the service-status command and a port listing, and record that the service is stopped and the port no longer listens.",
    "Confirm the setting survives a reboot and an upgrade.",
    "Check the business owner agrees the feature is not needed."
   ],
   "evidence_to_keep": [
    "Before and after configuration export",
    "Service-status check result",
    "Business owner sign-off that the feature is unused",
    "Change ticket",
    "Review date"
   ],
   "standard_ids": [
    "NIST SP 800-53 CM-7",
    "NIST SP 800-40r4",
    "PCI DSS FAQ 1597 ('disabling a vulnerable service')"
   ],
   "sources": [
    {
     "claim": "SP 800-40r4 lists disabling a feature under Mitigate.",
     "quote": "Mitigate: Reduce the risk by eliminating the vulnerabilities (e.g., patching the vulnerable software, disabling a vulnerable feature, or upgrading to a newer software version without the vulnerabilities)",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.1"
    },
    {
     "claim": "800-53 CM-7 statement.",
     "quote": "Prohibit or restrict the use of the following functions, ports, protocols, software, and/or services",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/CM-7",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "CM-7 b"
    },
    {
     "claim": "A KEV required action that names disabling a service.",
     "quote": "Apply mitigations per vendor instructions or disable SLP service or port 427/UDP on all systems running on untrusted networks, including those directly connected to the Internet.",
     "source": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "requiredAction field, CVE-2023-29552"
    }
   ],
   "notes": null,
   "verification_basis": [
    {
     "claim": "SP 800-40r4 says to verify that a deployed control works.",
     "quote": "For deploying additional security controls, ensure they are functioning as intended.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3c"
    },
    {
     "claim": "SP 800-40r4 says to keep monitoring that the control stays in place.",
     "quote": "Make sure that the risk response continues to be in place: no one uninstalls the patch, deactivates the additional security controls, lets the cybersecurity insurance lapse, or restarts the decommissioned asset.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3d"
    }
   ],
   "changes": "The code path or setting"
  },
  {
   "id": "configuration-change",
   "name": "Configuration change or hardening setting",
   "control_kind": "mitigation",
   "what_it_changes": "Changes a setting so the vulnerable behavior is not reachable or not exploitable under default use.",
   "what_it_does_not_fix": "The underlying flaw stays. Microsoft defines a workaround as a change that 'does not correct the underlying vulnerability'.",
   "how_to_verify": [
    "Read the setting back from the system and compare it to the approved value.",
    "Run the vendor's check for the setting if one exists.",
    "Alert on drift from the approved value."
   ],
   "evidence_to_keep": [
    "Approved configuration baseline entry",
    "Read-back output with date",
    "Drift alert rule",
    "Approved deviation record if the baseline is changed"
   ],
   "standard_ids": [
    "NIST SP 800-53 CM-6",
    "Microsoft Security Bulletins 'Mitigations' and 'Workarounds' wording"
   ],
   "sources": [
    {
     "claim": "Microsoft's definition of a workaround (from security bulletin MS10-046, archived on Microsoft Learn).",
     "quote": "Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update.",
     "source": "https://learn.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-046",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "MS10-046, Workarounds section"
    },
    {
     "claim": "Microsoft's definition of a mitigation, quoted from the middle of the sentence 'Mitigation refers to a setting, common configuration, or general ...' (same bulletin).",
     "quote": "existing in a default state, that could reduce the severity of exploitation of a vulnerability.",
     "source": "https://learn.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-046",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "MS10-046, Mitigating Factors section"
    },
    {
     "claim": "800-53 CM-6 on approving deviations.",
     "quote": "Identify, document, and approve any deviations from established configuration settings",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/CM-6",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "CM-6 c"
    }
   ],
   "notes": "Microsoft's 2010 bulletin text is a legacy page. The current Security Update Guide (msrc.microsoft.com/update-guide) is a script-built page that could not be read on 2026-11-19, so its present wording is unconfirmed.",
   "verification_basis": [
    {
     "claim": "SP 800-40r4 says to verify that a deployed control works.",
     "quote": "For deploying additional security controls, ensure they are functioning as intended.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3c"
    },
    {
     "claim": "SP 800-40r4 says to keep monitoring that the control stays in place.",
     "quote": "Make sure that the risk response continues to be in place: no one uninstalls the patch, deactivates the additional security controls, lets the cybersecurity insurance lapse, or restarts the decommissioned asset.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3d"
    }
   ],
   "changes": "The code path or setting"
  },
  {
   "id": "access-restriction",
   "name": "Access restriction or least privilege on the vulnerable component",
   "control_kind": "mitigation",
   "what_it_changes": "Narrows who and what can call the component: allow-lists of source addresses, removing public listeners, separating admin interfaces.",
   "what_it_does_not_fix": "Authorized users and allowed sources can still reach the flaw. A stolen credential or a compromised allowed host bypasses it.",
   "how_to_verify": [
    "List who can reach the component and compare to the approved list.",
    "Confirm management interfaces are not reachable from untrusted networks.",
    "Review the access list on a schedule."
   ],
   "evidence_to_keep": [
    "Access list export with date",
    "Approved-user list and approver",
    "Review record"
   ],
   "standard_ids": [
    "NIST SP 800-53 AC-6, SC-7(5)"
   ],
   "sources": [
    {
     "claim": "800-53 SC-7(5)",
     "quote": "Deny network communications traffic by default and allow network communications traffic by exception",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/SC-7.5",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "SC-7(5)"
    },
    {
     "claim": "800-53 AC-6",
     "quote": "Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/AC-6",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "AC-6"
    },
    {
     "claim": "A KEV required action that restricts management interface exposure.",
     "quote": "Additionally, the management interfaces for affected devices should not be exposed to untrusted networks, including the internet.",
     "source": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "requiredAction field, CVE-2024-9474"
    }
   ],
   "notes": null,
   "verification_basis": [
    {
     "claim": "SP 800-40r4 says to verify that a deployed control works.",
     "quote": "For deploying additional security controls, ensure they are functioning as intended.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3c"
    },
    {
     "claim": "SP 800-40r4 says to keep monitoring that the control stays in place.",
     "quote": "Make sure that the risk response continues to be in place: no one uninstalls the patch, deactivates the additional security controls, lets the cybersecurity insurance lapse, or restarts the decommissioned asset.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3d"
    }
   ],
   "changes": "Who can reach it"
  },
  {
   "id": "mfa-in-front",
   "name": "Multi-factor authentication in front of the component",
   "control_kind": "mitigation",
   "what_it_changes": "Adds a second factor to the access path (for example privileged accounts or a remote access gateway), so a stolen password alone does not give access.",
   "what_it_does_not_fix": "Does not fix a flaw that is exploitable before or without authentication, and does not help once a session is hijacked.",
   "how_to_verify": [
    "Confirm, with a test account your team owns, that a login with the first factor only is refused.",
    "Check there is no bypass path or exempted group.",
    "Review enrollment coverage for the accounts in scope."
   ],
   "evidence_to_keep": [
    "Policy export showing MFA required",
    "Test result with date",
    "Exemption list with approver",
    "Enrollment coverage report",
    "Advisory text showing where the flaw sits relative to the login"
   ],
   "standard_ids": [
    "NIST SP 800-53 IA-2(1)"
   ],
   "sources": [
    {
     "claim": "800-53 IA-2(1)",
     "quote": "Implement multi-factor authentication for access to privileged accounts.",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/IA-2.1",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "IA-2(1)"
    },
    {
     "claim": "A KEV entry whose description says the flaw bypasses SAML-enforced MFA.",
     "quote": "Successful exploitation may also bypass SAML-enforced multi-factor authentication (MFA).",
     "source": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "CVE-2026-19868, shortDescription, catalog 2026.11.18"
    },
    {
     "claim": "A KEV entry whose description says the flaw may allow bypass of MFA in some configurations.",
     "quote": "In some configurations, this may also allow bypass of multi-factor authentication.",
     "source": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "CVE-2026-48558, shortDescription, catalog 2026.11.18"
    },
    {
     "claim": "The vendor's own notice for CVE-2026-48558 points to updating.",
     "quote": "Not all servers can be exploited.",
     "source": "https://simple-help.com/security/simplehelp-security-update-2026-05",
     "read": "2026-11-19",
     "kind": "vendor",
     "location": "SimpleHelp security notice 2026-05"
    }
   ],
   "notes": "Two KEV entries (CVE-2026-19868, CVE-2026-48558) describe MFA bypass, so the control only counts where the flaw is not in the component that enforces the factor. No KEV required action read on 2026-11-19 names MFA as the response. The SonicWall advisory page returned no text.",
   "verification_basis": [
    {
     "claim": "SP 800-40r4 says to verify that a deployed control works.",
     "quote": "For deploying additional security controls, ensure they are functioning as intended.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3c"
    },
    {
     "claim": "SP 800-40r4 says to keep monitoring that the control stays in place.",
     "quote": "Make sure that the risk response continues to be in place: no one uninstalls the patch, deactivates the additional security controls, lets the cybersecurity insurance lapse, or restarts the decommissioned asset.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3d"
    }
   ],
   "changes": "Who can reach it"
  },
  {
   "id": "edr-rule",
   "name": "EDR or host protection rule",
   "control_kind": "mitigation",
   "what_it_changes": "Detects or blocks the post-exploitation behavior or the exploit process on the host.",
   "what_it_does_not_fix": "The vulnerable software stays. Coverage depends on the agent being installed and healthy on every affected host.",
   "how_to_verify": [
    "Confirm the agent is present and reporting on every affected host.",
    "Confirm the rule is in block mode and fires on a benign test of the behavior it targets.",
    "Review hosts with a stale agent."
   ],
   "evidence_to_keep": [
    "Agent coverage report with date",
    "Rule ID and mode",
    "Test record",
    "Exception list"
   ],
   "standard_ids": [
    "NIST SP 800-53 SI-3, SI-4"
   ],
   "sources": [
    {
     "claim": "800-53 SI-3 discussion.",
     "quote": "A variety of technologies and methods exist to limit or eliminate the effects of malicious code.",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/SI-3",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "SI-3 discussion"
    },
    {
     "claim": "800-53 SI-4 d",
     "quote": "Analyze detected events and anomalies;",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/SI-4",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "SI-4 d"
    }
   ],
   "notes": null,
   "verification_basis": [
    {
     "claim": "SP 800-40r4 says to verify that a deployed control works.",
     "quote": "For deploying additional security controls, ensure they are functioning as intended.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3c"
    },
    {
     "claim": "SP 800-40r4 says to keep monitoring that the control stays in place.",
     "quote": "Make sure that the risk response continues to be in place: no one uninstalls the patch, deactivates the additional security controls, lets the cybersecurity insurance lapse, or restarts the decommissioned asset.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3d"
    }
   ],
   "changes": "What can run on the host"
  },
  {
   "id": "application-allow-listing",
   "name": "Application allow-listing",
   "control_kind": "mitigation",
   "what_it_changes": "Only approved programs can run on the host, so an exploit that drops or launches an unapproved program is blocked.",
   "what_it_does_not_fix": "Does not stop exploitation of an approved program or in-memory abuse of it. The list must be kept current or it fails open or breaks work.",
   "how_to_verify": [
    "Confirm the policy is enforced, not audit-only.",
    "Attempt to run an unapproved test binary on a pilot host and confirm it is blocked.",
    "Review the allow list and its owner on a schedule."
   ],
   "evidence_to_keep": [
    "Policy export with mode",
    "Pilot test record",
    "Allow-list review record"
   ],
   "standard_ids": [
    "NIST SP 800-53 CM-7(5)"
   ],
   "sources": [
    {
     "claim": "800-53 CM-7(5)",
     "quote": "Employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system;",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/CM-7.5",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "CM-7(5) b"
    }
   ],
   "notes": null,
   "verification_basis": [
    {
     "claim": "SP 800-40r4 says to verify that a deployed control works.",
     "quote": "For deploying additional security controls, ensure they are functioning as intended.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3c"
    },
    {
     "claim": "SP 800-40r4 says to keep monitoring that the control stays in place.",
     "quote": "Make sure that the risk response continues to be in place: no one uninstalls the patch, deactivates the additional security controls, lets the cybersecurity insurance lapse, or restarts the decommissioned asset.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3d"
    }
   ],
   "changes": "What can run on the host"
  },
  {
   "id": "increased-monitoring",
   "name": "Increased monitoring and alerting",
   "control_kind": "detective control (reduces dwell time, does not prevent)",
   "what_it_changes": "Raises the chance an exploit attempt or compromise is seen, and cuts the time to respond.",
   "what_it_does_not_fix": "Prevents nothing by itself. It is a weak stand-alone mitigation for a vulnerability being exploited in the wild.",
   "how_to_verify": [
    "Confirm the detection fires on a benign test of the event it targets.",
    "Confirm someone owns the alert and a response runbook exists.",
    "Check alert volume is reviewable."
   ],
   "evidence_to_keep": [
    "Detection rule ID and logic",
    "Test alert with date",
    "Named owner and runbook link",
    "Alert review log"
   ],
   "standard_ids": [
    "NIST SP 800-53 SI-4"
   ],
   "sources": [
    {
     "claim": "800-53 SI-4 e",
     "quote": "Adjust the level of system monitoring activity when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation;",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/SI-4",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "SI-4 e"
    },
    {
     "claim": "BOD 26-04 pairs the fastest actions with a check for compromise.",
     "quote": "The text \"& forensic triage\" means that the agency must complete remediation or mitigation action within the timeline (three days) and carry out a forensic triage of the asset to assess whether the system is compromised.",
     "source": "https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Appendix A, notes to Table 1"
    }
   ],
   "notes": null,
   "verification_basis": [
    {
     "claim": "SP 800-40r4 says to verify that a deployed control works.",
     "quote": "For deploying additional security controls, ensure they are functioning as intended.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3c"
    },
    {
     "claim": "SP 800-40r4 says to keep monitoring that the control stays in place.",
     "quote": "Make sure that the risk response continues to be in place: no one uninstalls the patch, deactivates the additional security controls, lets the cybersecurity insurance lapse, or restarts the decommissioned asset.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3d"
    }
   ],
   "changes": "How fast an attack is seen"
  },
  {
   "id": "remove-internet-exposure",
   "name": "Remove internet exposure",
   "control_kind": "mitigation",
   "what_it_changes": "Takes the component off public networks (pull the listener, put it behind VPN or a private link). BOD 26-04 treats this as changing the exposure rating, which moves the required timeline.",
   "what_it_does_not_fix": "Does not fix the flaw. Internal attackers and anything that still reaches it remain. It can be undone by a later network change.",
   "how_to_verify": [
    "From a network outside the perimeter, try to open a connection to the component's public address and port and record that it fails or times out. This shows reachability only.",
    "Check DNS and load balancer records for stale paths.",
    "Re-check after each network change."
   ],
   "evidence_to_keep": [
    "External connectivity check result with date",
    "Before and after exposure inventory entry",
    "Change ticket"
   ],
   "standard_ids": [
    "CISA BOD 26-04",
    "CISA ICS advisories"
   ],
   "sources": [
    {
     "claim": "BOD 26-04 names removing the system from the internet as a valid mitigation.",
     "quote": "one valid mitigation is to remove the system from the internet; that action changes the value of \"Publicly Exposed\" from Yes to No and will shift the required timeline for further action",
     "source": "https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Appendix A, notes to Table 1"
    },
    {
     "claim": "CISA ICS advisory recommended practice.",
     "quote": "Minimize network exposure for all control system devices and/or systems, ensuring they are not accessible from the internet",
     "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-321-11",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Recommended Practices"
    }
   ],
   "notes": null,
   "verification_basis": [
    {
     "claim": "SP 800-40r4 says to verify that a deployed control works.",
     "quote": "For deploying additional security controls, ensure they are functioning as intended.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3c"
    },
    {
     "claim": "SP 800-40r4 says to keep monitoring that the control stays in place.",
     "quote": "Make sure that the risk response continues to be in place: no one uninstalls the patch, deactivates the additional security controls, lets the cybersecurity insurance lapse, or restarts the decommissioned asset.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 2.2, step 3d"
    }
   ],
   "changes": "Who can reach it"
  }
 ]
}