# Remediation and mitigation glossary

Canonical: https://remediationvsmitigation.com/glossary/

Thirty-one terms for remediating, mitigating, accepting and excepting security findings, each defined in the issuer's own words with a sourced example or note. Definitions come from NIST, FedRAMP, CISA, PCI SSC, OWASP and Microsoft, all read on 19 Nov 2026, and the entries run A to Z.

## Accepted vulnerability

FedRAMP defines it as "A vulnerability that the provider does not intend to fully mitigate or remediate, OR that has not or will not be fully mitigated or remediated within the maximum overdue period in FedRAMP Vulnerability Detection and Response rules" ([definitions](https://www.fedramp.gov/2026/definitions/)).

Example: the definition refers to a "maximum overdue period"; the figure is set in rule VER-TFR-MAV of the Vulnerability Evaluation and Reporting rules: 192 days from evaluation ([FedRAMP](https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/)). A flaw evaluated on 15 Oct 2026 and still unfixed becomes accepted on 25 Apr 2027. See [maximum durations](https://remediationvsmitigation.com/risk-acceptance-form/maximum-durations/).

## Authorization termination date

The date on which an authorization expires. NIST SP 800-37 Rev. 2 says it "is established by the authorizing official and indicates when the authorization expires".

Example: It is the model for field 14 of the [Risk Acceptance Form](https://remediationvsmitigation.com/risk-acceptance-form/). Source: [SP 800-37 Rev. 2, Task R-4](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf).

## Authorizing official

NIST: "A senior Federal official or executive with the authority to authorize (i.e., assume responsibility for) the operation of an information system" ([glossary](https://csrc.nist.gov/glossary/term/authorizing_official)).

Also: Acceptance of risk "cannot be delegated to other officials within the organization" ([SP 800-37 Rev. 2, Task R-4](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf)). See [who may sign](https://remediationvsmitigation.com/risk-acceptance-form/who-may-sign/).

## Compensating control

NIST: "The security and privacy controls employed in lieu of the controls in the baselines described in NIST Special Publication 800-53B that provide equivalent or comparable protection for a system or organization" ([glossary](https://csrc.nist.gov/glossary/term/compensating_controls)).

Example: PCI SSC treats a compensating control as one way to address a vulnerability that is not resolved, for example "with a compensating control or by disabling a vulnerable service" ([FAQ 1597](https://www.pcisecuritystandards.org/faqs/1597)).

## Decommission

Retiring a system or device so the vulnerable component no longer exists in the environment. CISA BOD 26-04 counts it as a way to remediate: elimination "through patching, decommissioning the system, or another action".

Example: BOD 26-02 requires agencies to "Decommission all identified EOS edge devices from agency networks" ([BOD 26-02](https://www.cisa.gov/news-events/directives/bod-26-02-mitigating-risk-end-support-edge-devices)).

## Exception (to a maintenance plan)

An asset that cannot follow its normal patch plan. NIST SP 800-40 Rev. 4 says organizations "should closely track and monitor all exceptions to maintenance plans".

Also: The same section says "Assets with similar long-term exceptions might need to be moved to a separate maintenance group with its own maintenance plan" ([Section 3.5.5](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf)). See [acceptance versus exception](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-exception/).

## False positive vulnerability

FedRAMP: "A detected vulnerability that is not actually present in an exploitable state in the information resource" ([definitions](https://www.fedramp.gov/2026/definitions/)).

Also: the definition covers vulnerable code that exists on a machine but "not loaded, running, or otherwise in an operating state required for exploitation", and excludes anything remediated or fully mitigated. See [false positive handling](https://remediationvsmitigation.com/guides/false-positive-handling/).

## Fully mitigated vulnerability

FedRAMP: "A vulnerability where the likelihood of exploitation or Potential Agency Impact N-rating has been reduced from the original evaluation until either are negligible, but the vulnerability is still detected" ([definitions](https://www.fedramp.gov/2026/definitions/)).

Also: FedRAMP adds that a fully mitigated vulnerability still exists until it is remediated ([VDR-CSO-RES](https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/)), and still expects KEVs to be remediated by the CISA date.

## Internet-reachable vulnerability

FedRAMP: "A vulnerability in a machine-based information resource that might be exploited or otherwise triggered by a payload originating from a source on the public internet" ([definitions](https://www.fedramp.gov/2026/definitions/)).

Also: A resource with "no direct route to/from the internet" still counts if it receives payloads or acts on internet activity. This is field 4 of the [form](https://remediationvsmitigation.com/risk-acceptance-form/).

## Known exploited vulnerability (KEV)

FedRAMP, citing CISA: "any vulnerability identified in CISA's Known Exploited Vulnerabilities catalog" ([definitions](https://www.fedramp.gov/2026/definitions/)).

Example: Catalog version 2026.11.18 held 1786 entries, read from the [CISA feed](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json) on 19 Nov 2026. See the [KEV rows of the Decision Table](https://remediationvsmitigation.com/decision-table/kev-patch-available-exposed/).

## Likely exploitable vulnerability

FedRAMP: a vulnerability that is not fully mitigated and is reachable by a likely threat actor who "would likely gain unauthorized access, cause harm, disrupt operations, or otherwise have an undesired adverse impact" ([definitions](https://www.fedramp.gov/2026/definitions/)).

Also: The note sets a floor: "any vulnerability that an automated unauthenticated system can exploit over the internet is a likely exploitable vulnerability".

## Mitigation

NIST SP 800-216: "The temporary reduction or lessening of the impact of a vulnerability or the likelihood of its exploitation" ([glossary](https://csrc.nist.gov/glossary/term/mitigation)).

Also: FedRAMP separates it from remediation: "Mitigation is the process of reducing the risk and impact of a vulnerability" ([VDR-CSO-RES](https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/)).

## Ongoing authorization

NIST SP 800-37 Rev. 2, Task R-4: an organization may eliminate the authorization termination date "if the system is operating under an ongoing authorization", where continuous monitoring gives the authorizing official "the needed information to conduct ongoing risk determination and risk acceptance" ([SP 800-37 Rev. 2](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf)).

## Overdue vulnerability

FedRAMP: "A vulnerability that the provider intends to fully mitigate or remediate but has not or will not do so within the time frames recommended or required by FedRAMP" ([definitions](https://www.fedramp.gov/2026/definitions/)).

Also: It differs from an accepted vulnerability by intent: the provider still plans to fix it. The two get separate statuses in the [exception register](https://remediationvsmitigation.com/exception-register/).

## Partially mitigated vulnerability

FedRAMP: a vulnerability whose likelihood or impact level "has been reduced from the original evaluation but the risk of exploitation still exists" ([definitions](https://www.fedramp.gov/2026/definitions/)).

Also: Where full mitigation or remediation is not possible, providers "SHOULD instead partially mitigate vulnerabilities promptly, progressively, and persistently" ([VDR-CSO-RES](https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/)).

## Plan of action and milestones (POA&M)

NIST: "A document that identifies tasks that need to be accomplished. It details resources required to accomplish the elements of the plan, milestones for meeting the tasks, and the scheduled completion dates for the milestones" ([glossary](https://csrc.nist.gov/glossary/term/plan_of_action_and_milestones)).

Example: FedRAMP tells agencies to create a POA&M "only when there are actions the agency needs to take, track, fund, manage, or accept" ([agency POA&M page](https://www.fedramp.gov/2026/agencies/use/ongoing/poams/)).

## Potential Agency Impact (PAIN)

FedRAMP, which lists PAIN as the short form of Potential Agency Impact N-rating: "The estimated cumulative effect of unauthorized access, disruption, harm, or other adverse impacts to all agencies using the cloud service" ([definitions](https://www.fedramp.gov/2026/definitions/)).

Example: it drives the timeframes in VDR-TFR-PVR. A Class D provider has 12 hours for a PAIN-5 flaw that is likely exploitable and internet-reachable, and 192 days for a PAIN-2 flaw that is not ([FedRAMP](https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/)).

## Qualified Security Assessor (QSA)

In PCI DSS compliance, the assessor who judges compensating controls. PCI SSC: "QSAs are responsible to determine whether a compensating control is sufficient to meet the intent of a requirement" ([FAQ 1046](https://www.pcisecuritystandards.org/faqs/1046)).

Example: when a critical security patch was not installed within 30 days of release, PCI SSC says an assessor can find the requirement "In Place" only with assurance of four things: a repeatable documented process, an exceptional circumstance, the cause addressed and recurrence prevented. Otherwise the assessor can consider "Not in Place" ([FAQ 1572](https://www.pcisecuritystandards.org/faqs/1572), June 2025).

## Remediated vulnerability

FedRAMP: "A vulnerability that has been neutralized or eliminated and is no longer detected" ([definitions](https://www.fedramp.gov/2026/definitions/)).

Example: The phrase "no longer detected" makes a rescan the closing evidence; the register column for it is described on the [exception register page](https://remediationvsmitigation.com/exception-register/).

## Remediation

NIST SP 800-216: "The neutralization or elimination of a vulnerability or the likelihood of its exploitation"; CNSSI 4009-2022 also lists "The act of mitigating a vulnerability or a threat" ([glossary](https://csrc.nist.gov/glossary/term/remediation)).

Also: CISA BOD 26-04 uses the narrower meaning: "the vulnerability is eliminated through patching, decommissioning the system, or another action" ([BOD 26-04](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk)).

## Residual risk

The risk that remains after a risk response. NIST SP 800-37 Rev. 2: "regardless of the risk response, there remains a degree of residual risk".

Also: Organizations "determine acceptable degrees of residual risk based on organizational risk tolerance" ([SP 800-37 Rev. 2, Task R-3](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf)). SP 800-39, Task 3-3, adds "and the specific risk tolerances of particular decision makers" ([SP 800-39](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-39.pdf)). It is field 11 of the [form](https://remediationvsmitigation.com/risk-acceptance-form/).

## Risk acceptance

NIST SP 800-39: "Risk acceptance is the appropriate risk response when the identified risk is within the organizational risk tolerance" ([Task 3-1](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-39.pdf)).

Also: SP 800-40 Rev. 4 adds that "By default, an organization accepts the risk posed by using its software" ([Section 2.1](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf)).

## Risk avoidance

NIST SP 800-40 Rev. 4: "Ensure that the risk does not occur by eliminating the attack surface, such as by uninstalling the vulnerable software, decommissioning assets with the vulnerabilities, or disabling computing capabilities in assets that can function without them" ([Section 2.1](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf)).

Also: SP 800-39 sets the trigger: avoidance "may be the appropriate risk response when the identified risk exceeds the organizational risk tolerance".

## Risk mitigation

NIST SP 800-30 Rev. 1: "Prioritizing, evaluating, and implementing the appropriate risk-reducing controls/countermeasures recommended from the risk management process. A subset of Risk Response" ([glossary](https://csrc.nist.gov/glossary/term/risk_mitigation)).

Also: SP 800-40 Rev. 4 includes patching in its mitigate response, which is why the word is not used the same way across publications.

## Risk response

NIST: "Accepting, avoiding, mitigating, sharing, or transferring risk to organizational operations, organizational assets, individuals, other organizations, or the Nation" ([glossary](https://csrc.nist.gov/glossary/term/risk_response)).

Also: SP 800-40 Rev. 4 names four for software vulnerabilities (accept, mitigate, transfer, avoid) and does not list sharing separately ([Section 2.1](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf)).

## Risk tolerance

NIST: "The level of risk or the degree of uncertainty that is acceptable to an organization" ([glossary](https://csrc.nist.gov/glossary/term/risk_tolerance)).

Also: SP 800-39 notes "There is no correct level of organizational risk tolerance" ([SP 800-39](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-39.pdf)). See [risk acceptance criteria](https://remediationvsmitigation.com/guides/risk-acceptance-criteria/).

## Risk transfer

NIST SP 800-39: risk transfer "shifts the entire risk responsibility or liability from one organization to another organization", for example by insurance.

Also: The same text warns that "risk transfer reduces neither the likelihood of harmful events occurring nor the consequences" ([Task 3-1](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-39.pdf)).

## Vendor dependency

In the legacy FedRAMP playbook, a finding whose fix waits on a vendor patch that does not yet exist. The playbook is marked reference only after 24 Jun 2026.

Also: It required that providers "check in with the vendor at least once a month" and said high-risk vendor dependencies must be mitigated to a Moderate level within 30 days ([playbook](https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/)).

## Virtual patch

OWASP: "A security policy enforcement layer that detects and blocks matching exploitation attempts against a known vulnerability without changing the vulnerable code" ([cheat sheet](https://cheatsheetseries.owasp.org/cheatsheets/Virtual_Patching_Cheat_Sheet.html)).

Example: Fastly offers a virtual patch for CVE-2026-75650 in Adobe Commerce, and Sansec says to install Adobe's hotfix anyway, so the fix is still owed ([Fastly](https://www.fastly.com/blog/what-is-style-smuggler-cve-2026-75650)). OWASP says a virtual patch leaves the underlying vulnerability in place.

## Waiver

A release from a required action. CISA states that it "does not issue waivers or exceptions for actions required in cyber directives" ([BOD 26-04 guidance](https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk)).

Example: A missed KEV date therefore cannot be waived; see the KEV row of the [Decision Table](https://remediationvsmitigation.com/decision-table/).

## Workaround

Microsoft's 2010 bulletin MS10-046 defines it as "a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update" ([bulletin](https://learn.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-046)).

Also: the same bulletin uses "mitigation" for a setting or common configuration "existing in a default state" that could reduce severity. See [workaround versus mitigation](https://remediationvsmitigation.com/guides/workaround-vs-mitigation/).

Longer explanations of terms used above: [risk tolerance and risk acceptance](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-tolerance/), [residual risk](https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/), [inherent versus residual risk](https://remediationvsmitigation.com/guides/inherent-vs-residual-risk/), [risk owner](https://remediationvsmitigation.com/guides/risk-owner/), [plan of action and milestones](https://remediationvsmitigation.com/guides/poam-plan-of-action-and-milestones/) and [false positive](https://remediationvsmitigation.com/guides/false-positive-handling/).

## Sources

- FedRAMP Consolidated Rules for 2026, definitions: https://www.fedramp.gov/2026/definitions/ (read 19 Nov 2026)
- FedRAMP 2026, Vulnerability Detection and Response: https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/ (read 19 Nov 2026)
- FedRAMP 2026, Vulnerability Evaluation and Reporting: https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/ (read 19 Nov 2026)
- FedRAMP 2026, Managing POA&Ms: https://www.fedramp.gov/2026/agencies/use/ongoing/poams/ (read 19 Nov 2026)
- FedRAMP legacy POA&M playbook: https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/ (read 19 Nov 2026)
- 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 CSRC glossary, risk mitigation: https://csrc.nist.gov/glossary/term/risk_mitigation (read 19 Nov 2026)
- NIST CSRC glossary, risk response: https://csrc.nist.gov/glossary/term/risk_response (read 19 Nov 2026)
- NIST CSRC glossary, risk tolerance: https://csrc.nist.gov/glossary/term/risk_tolerance (read 19 Nov 2026)
- NIST CSRC glossary, compensating controls: https://csrc.nist.gov/glossary/term/compensating_controls (read 19 Nov 2026)
- NIST CSRC glossary, plan of action and milestones: https://csrc.nist.gov/glossary/term/plan_of_action_and_milestones (read 19 Nov 2026)
- NIST CSRC glossary, authorizing official: https://csrc.nist.gov/glossary/term/authorizing_official (read 19 Nov 2026)
- NIST SP 800-37 Rev. 2: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf (read 19 Nov 2026)
- NIST SP 800-39: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-39.pdf (read 19 Nov 2026)
- NIST SP 800-40 Rev. 4: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf (read 19 Nov 2026)
- CISA BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 19 Nov 2026)
- CISA BOD 26-04 implementation guidance: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk (read 19 Nov 2026)
- CISA BOD 26-02: https://www.cisa.gov/news-events/directives/bod-26-02-mitigating-risk-end-support-edge-devices (read 19 Nov 2026)
- PCI SSC FAQ 1046: https://www.pcisecuritystandards.org/faqs/1046 (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)
- Microsoft, Security Bulletin MS10-046 (2010): https://learn.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-046 (read 19 Nov 2026)
- CISA KEV catalog JSON feed, version 2026.11.18: https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 19 Nov 2026)
- PCI SSC FAQ 1572: https://www.pcisecuritystandards.org/faqs/1572 (read 19 Nov 2026)

Last reviewed 19 Nov 2026

## Related

- [Risk Acceptance Form: Free Template With 15 Fields](https://remediationvsmitigation.com/risk-acceptance-form/index.md)
- [Exception Register: 15 Columns, States and Blank CSV](https://remediationvsmitigation.com/exception-register/index.md)
- [Risk Acceptance vs Risk Exception in Cyber Security](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-exception/index.md)
- [Risk Acceptance vs Risk Tolerance: Who Sets the Limit](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-tolerance/index.md)
- [Residual Risk After Mitigation: Define, Estimate, Record](https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/index.md)
- [Inherent vs Residual Risk on a Security Decision Record](https://remediationvsmitigation.com/guides/inherent-vs-residual-risk/index.md)
- [Who Is the Risk Owner for a Security Finding?](https://remediationvsmitigation.com/guides/risk-owner/index.md)
- [POA&M Example: A Filled Plan of Action and Milestones Entry](https://remediationvsmitigation.com/guides/poam-plan-of-action-and-milestones/index.md)
- [Vulnerability False Positive: Close It With Evidence](https://remediationvsmitigation.com/guides/false-positive-handling/index.md)
