# Inherent vs residual risk

Canonical: https://remediationvsmitigation.com/guides/inherent-vs-residual-risk/

Inherent risk is the risk before any management action; residual risk is the exposure left after action. NIST IR 8286 quotes COSO and OMB for both, then records "current risk" instead. The words "inherent risk" appear 0 times in SP 800-37 Rev. 2, SP 800-39 and SP 800-40 Rev. 4 (read 19 Nov 2026).

## Definitions as published

Quotations as printed in NIST IR 8286, Section 3.2, read 19 Nov 2026.

| Term | Wording | Source |
|---|---|---|
| Inherent risk | "The risk to an entity in the absence of any direct or focused actions by management to alter its severity." | COSO ERM, via NIST IR 8286 and the NIST glossary |
| Inherent risk | "conditions in the absence of risk management actions" | OMB Circular A-123, via NIST IR 8286 |
| Residual risk | "the exposure remaining from an inherent risk after action has been taken to manage it, using the same assessment standards as the inherent assessment" | OMB Circular A-123, via NIST IR 8286 |
| Target residual risk | "the amount of risk that an entity prefers to assume in the pursuit of its strategy and business objectives" | COSO ERM, via NIST IR 8286 |
| Actual residual risk | "the risk remaining after management has taken action to alter its severity. Actual residual risk should be equal to or less than the target residual risk." | COSO ERM, via NIST IR 8286 |

NIST IR 8286 states that for federal agencies, OMB Circular A-123 requires the enterprise risk register to "consider both inherent and residual risk". Its own register uses a third state: "this publication typically refers to current risk (rather than inherent risk) that represents a baseline risk posture." Current risk is measured before the response in question and may already include existing controls, which is why it is the practical starting figure for a vulnerability on a running system.

## Which texts use which word

Counts on 19 Nov 2026. Method: text extracted from each NIST PDF with pypdf 7.1.1, hyphenated line breaks joined, whitespace collapsed, case-insensitive count of the exact phrase (the figure for IR 8286 includes its glossary and footnotes). SP 800-53 was counted in the NIST OSCAL JSON of Rev. 5.2.0, control prose only. FedRAMP and BOD figures are from the page text of the VER and VDR rules, the definitions page and the directive page.

| Document | "inherent risk" | "residual risk" |
|---|---|---|
| NIST SP 800-37 Rev. 2 | 0 | 6 |
| NIST SP 800-39 | 0 | 6 |
| NIST SP 800-30 Rev. 1 | 0 | 1 |
| NIST SP 800-40 Rev. 4 | 0 | 0 |
| NIST SP 800-82 Rev. 3 | 0 | 6 |
| NIST SP 800-53 Rev. 5.2.0 control text | 1 (discussion of MA-5(2), maintenance personnel) | 2 (discussion of SI-19, de-identification) |
| NIST IR 8286 | 6 | 25 |
| FedRAMP 2026 rules and definitions | 0 | 0 |
| CISA BOD 26-04 | 0 | 0 |

The federal publications that govern authorization use only the second word, and SP 800-53 uses both only inside guidance text. The BOD 26-04 clocks and FedRAMP's partial and full mitigation definitions use neither; they describe the asset as it is now. BOD 26-04 says "The timelines for each asset are dynamic as facts change". A decision record built on those rules therefore stores the current facts and the target, not a reconstruction of an unmanaged past.

## Worked example: one record with three states

The environment is invented; the CVE, the advisory and the dates are real. A team runs a Synology DiskStation Manager NAS with a port forward from the internet. CVE-2024-10441 (CVSS 3.1 base score 9.8, network, no privileges) is in Synology advisory SA-24:20, published 5 Nov 2024 with fixed releases and, in the vendor's words, "Mitigation None". CISA added it to the KEV catalog on 18 Nov 2026 with a due date of 21 Nov 2026 and forensic triage marked Yes, which is why the window is 3 days. The scale is an illustrative 1 to 5 for likelihood and for impact; exposure is their product, as IR 8286 defines exposure as the combination of likelihood and impact.

Record layout follows the IR 8286 register elements (current assessment, response, residual, target residual). Scale, values and owners are illustrative; 21 Nov 2026 is a Saturday.

| State | Date | Likelihood | Impact | Exposure | What changed | Set by |
|---|---|---|---|---|---|---|
| Current risk | 18 Nov 2026 | 5 | 4 | 20 | Port forward open; the entry was added to the KEV list that day | Vulnerability analyst proposes; head of IT operations, the risk owner, confirms |
| Target residual risk | 18 Nov 2026 |  |  | 8 or lower | Appetite for an internal file server; a KEV entry may not stay above it past the due date | Head of IT operations (risk owner) |
| Residual risk, first response | 19 Nov 2026 | 2 | 4 | 8 | Port forward removed; NAS reachable only from the office network. No vendor mitigation exists, so this is the owner's own control | NAS administrator measures; risk owner accepts |
| Residual risk, after fix (planned) | 21 Nov 2026 | 1 | 4 | 4 | DSM upgraded in the Saturday maintenance window to a fixed release listed in the advisory (for DSM 7.2.2: 7.2.2-72806-1 or above) | NAS administrator upgrades; a second administrator verifies the build number and signs |

The 19 Nov row is the one a single-number record cannot show. Exposure fell from 20 to 8 and met the target of 8, yet the KEV date of 21 Nov 2026 still asks for the vendor's action, so the record also keeps the response and its date: hold the interim control for two days, then remediate on 21 Nov, the due date itself. If the window slipped past 21 Nov, the gap would need a signed, dated exception that names the interim control and the new fix date; the due date would still be missed. The actual-below-target test is the tolerance test in [risk acceptance versus risk tolerance](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-tolerance/), and how the second number is estimated is in [residual risk after mitigation](https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/).

## Where each state appears on the record

The response is accept, transfer, mitigate or avoid (IR 8286 Table 3), with its date and the risk owner, defined in IR 8286 as "the designated party responsible and accountable for ensuring that the risk is maintained in accordance with enterprise requirements". After it, IR 8286 says "the results of a post-response assessment could be reflected in the register as the Residual Risk", and an organization "might even document a desired risk state based on risk appetite/tolerance, the Target Residual Risk". The pre-response fields sit on the [risk acceptance form](https://remediationvsmitigation.com/risk-acceptance-form/).

The register and the [exception register](https://remediationvsmitigation.com/exception-register/) hold the same finding at different grain; how they link is on [risk register versus exception register](https://remediationvsmitigation.com/guides/risk-register-vs-exception-register/).

## When the inherent framing is the wrong tool

- A vulnerability on a running asset has no unmanaged state to measure. The firewall, login and monitoring already exist, so current risk is the honest starting number. Inherent risk fits a design decision, such as whether to build a service at all.
- A KEV due date or a FedRAMP timeframe turns on facts now (internet exposure, exploitation status, impact rating), not on a before-and-after pair. Record the facts and the clock, then the residual.
- A residual figure counts only for a control that has been checked. Until then the record holds the current figure and a planned residual, labeled as planned.

## Sources

- NIST CSRC glossary, inherent risk: https://csrc.nist.gov/glossary/term/inherent_risk (read 19 Nov 2026)
- NIST CSRC glossary, residual risk: https://csrc.nist.gov/glossary/term/residual_risk (read 19 Nov 2026)
- NIST IR 8286, Sections 2 and 3.2 and glossary: https://nvlpubs.nist.gov/nistpubs/ir/2020/NIST.IR.8286.pdf (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-30 Rev. 1: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-30r1.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)
- NIST SP 800-82 Rev. 3: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-82r3.pdf (read 19 Nov 2026)
- NIST SP 800-53 Rev. 5.2.0 catalog (OSCAL JSON): https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json (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)
- FedRAMP 2026 definitions: https://www.fedramp.gov/2026/definitions/ (read 19 Nov 2026)
- Synology advisory Synology-SA-24:20: https://www.synology.com/en-us/security/advisory/Synology_SA_24_20 (read 19 Nov 2026)
- CISA KEV JSON feed, catalogVersion 2026.11.18: https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 19 Nov 2026)

Last reviewed 19 Nov 2026

## Related

- [Residual Risk After Mitigation: Define, Estimate, Record](https://remediationvsmitigation.com/guides/residual-risk-after-mitigation/index.md)
- [Risk Acceptance Form: Free Template With 15 Fields](https://remediationvsmitigation.com/risk-acceptance-form/index.md)
- [Remediation and Mitigation Glossary: 31 Terms, Sourced](https://remediationvsmitigation.com/glossary/index.md)
- [Risk Register vs Exception Register: How They Link](https://remediationvsmitigation.com/guides/risk-register-vs-exception-register/index.md)
- [Risk Acceptance vs Risk Tolerance: Who Sets the Limit](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-tolerance/index.md)
