Residual risk after mitigation
Residual risk is the portion of risk left after security measures are applied, and a mitigation never takes it to zero. The worked case rates CVE-2024-10441 (CVSS base score 9.8, added to CISA's KEV catalog on 18 Nov 2026) High before any control and Moderate after two, on one scale, with the next reduction dated.
On this page
Three wordings, one difference
| Source | Wording of "residual risk" | Condition built in |
|---|---|---|
| CNSSI 4009 (in NIST SP 800-30 Rev. 1) | "Portion of risk remaining after security measures have been applied." | Measures applied |
| NIST SP 800-161 Rev. 1 | "Portion of risk remaining after controls/countermeasures have been applied." | Controls applied |
| NIST IR 8286 | "Risk that remains after risk responses have been documented and performed." | Documented and performed |
The third wording is the stricter one for a mitigation record. A control that is planned but not installed, or installed but not written down, is not yet a response, so the residual figure stays at the earlier level until it is. NIST SP 800-37 adds that "regardless of the risk response, there remains a degree of residual risk" and that organizations "determine acceptable degrees of residual risk based on organizational risk tolerance". The inherent-risk side of the pair is on the inherent vs residual risk page.
Estimate it the way the first estimate was made
NIST IR 8286, Section 3.5.2: "The residual risk can be calculated using the same methods for calculating current risk". A record that rates the finding on one scale before a control and on another after cannot show a reduction. The same section tells the risk owner what to do with the result: "If the residual risk is beyond the acceptable level of risk, then the risk owner should evaluate whether the risk can be brought to an acceptable level (for example, by applying additional security controls)."
A worked case: CVE-2024-10441 on a NAS
The finding is real. Synology advisory Synology-SA-24:20, published 5 Nov 2024, rates CVE-2024-10441 Critical with a CVSS 3 base score of 9.8 (vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and says remote attackers can execute arbitrary code. The advisory lists the mitigation as "None" and the fixed release for DSM 7.2.2 as 7.2.2-72806-1. CISA added the CVE to the KEV catalog on 18 Nov 2026, 743 days after the advisory, with a due date of 21 Nov 2026 and the forensic triage flag set to Yes. The asset below, its owners and every date after 19 Nov are the example's own: one DiskStation running DSM 7.2.2 earlier than 7.2.2-72806-1, holding finance team shares, reachable from the internet through a port forward.
The scale is also the example's. Both estimates use it, as IR 8286 requires.
| Likelihood of exploitation | Impact Low | Impact Moderate | Impact High |
|---|---|---|---|
| Low | Low | Low | Moderate |
| Medium | Low | Moderate | High |
| High | Moderate | High | High |
| Date | Step and evidence | Likelihood | Impact | Rating |
|---|---|---|---|---|
| 19 Nov 2026 | Baseline. Reachable from the internet, no login needed, on the KEV catalog; full control of the device would follow. Evidence: port-forward list, KEV entry. | High | High | High |
| 19 Nov 2026 | First control: the port forward is removed, so only the office network reaches the NAS. Evidence: port-forward list after the change. | Medium | High | High |
| 20 Nov 2026 | Second control: a firewall rule limits the NAS to two administrator workstations. Evidence: rule list, a refused connection from a non-administrator workstation in the log. | Low | High | Moderate |
| 21 Nov 2026 | KEV due date. Forensic triage of the NAS completed with no sign of compromise. Evidence: triage note. | Low | High | Moderate |
| 28 Nov 2026 | Next reduction: upgrade to 7.2.2-72806-1 or later. Evidence: version shown after the change. | |||
| 30 Nov 2026 | Rescan reads the finding as no longer detected; entry closed. | Closed |
Three things in the table need attention. The first control lowered the likelihood but left the rating at High, so a record that logs only the rating would show no progress, while a record that logs likelihood and impact separately shows it. The Moderate figure on 20 Nov is inside the 30-day tolerance and the upgrade is dated 8 days later, so the acceptance period is short and ends with a fix. The figure also describes the future only: the KEV entry flags forensic triage, which BOD 26-04 describes as completing "remediation or mitigation action within the timeline (three days)" and carrying out a triage "to assess whether the system is compromised". A control cannot lower the risk of an intrusion that already happened, which is why the 21 Nov row records the triage result.
How FedRAMP records each step down
FedRAMP's 2026 definitions call a vulnerability partially mitigated when "the risk of exploitation still exists and the vulnerability is still detected", and fully mitigated when likelihood or impact has been reduced "until either are negligible, but the vulnerability is still detected". Rule VER-RPT-VDT asks providers for the "Time and Potential Agency Impact N-rating of each completed and evaluated reduction" and the "Estimated time and target Potential Agency Impact N-rating of next reduction". The ladder above carries the same fields: each rung has a date, a level and a next target. The wording that matters for a record is in the FedRAMP definitions.
A control that only helps response leaves the rating unchanged
NIST SP 800-82 Rev. 3 separates two kinds of compensating control for OT. Limiting exposure, restricting vulnerable services and virtual patching reduce the chance of exploitation. "Other compensating controls that do not decrease the residual risk but increase the ability to respond may be desirable (e.g., provide a timely response in case of an incident, devise a plan to ensure that the OT can identify exploitation of the flaw)." Adding the NAS to a monitoring rule would sit in the second group: it belongs on the record, but the rating in the ladder would not change. See increased monitoring in the register.
Who estimates and who signs
The security analyst proposes the likelihood and impact, the system owner confirms the facts they rest on (exposure, version, data held), and the risk owner decides whether the residual level is acceptable, per IR 8286. Under NIST SP 800-37 Task R-4, acceptance by the authorizing official "cannot be delegated". Other organizations name their own signer; see who is the risk owner and who may sign.
The record carries four things: the before and after levels on one scale with the control that moved each, the tolerance statement they are compared with, the date measured with the next reduction and its date, and the evidence for each control. The field for them is in the Risk Acceptance Form. The case where the control is already in front of the flaw is in control already in place.
Sources
- NIST CSRC glossary, residual risk, read 19 Nov 2026
- NIST IR 8286, Section 3.5.2, read 19 Nov 2026
- NIST SP 800-37 Rev. 2, Task R-3 discussion and Task R-4, read 19 Nov 2026
- NIST SP 800-82 Rev. 3, Section 6.2.11 (SI-2 OT discussion), read 19 Nov 2026
- FedRAMP 2026, VER-RPT-VDT, read 19 Nov 2026
- FedRAMP 2026 definitions, partially and fully mitigated vulnerability, read 19 Nov 2026
- Synology advisory Synology-SA-24:20, read 19 Nov 2026
- CISA KEV catalog JSON feed, catalogVersion 2026.11.18, entry CVE-2024-10441, read 19 Nov 2026
- CISA BOD 26-04, Appendix A, read 19 Nov 2026
Last reviewed