# Risk acceptance vs risk exception

Canonical: https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-exception/

A risk acceptance records who agreed to live with a risk. A risk exception records that an asset may depart from a rule, plan or setting. Two hosts missing the 2 Nov 2026 deadline for CVE-2026-80521 show it: one needs an exception only, the other an exception with an acceptance behind it.

## What the primary sources call each one

NIST SP 800-39 defines acceptance as a response to a risk: it "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)). In US federal systems the signer is fixed: "The explicit acceptance of risk is the responsibility of the authorizing official and cannot be delegated" ([SP 800-37 Rev. 2, Task R-4](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf)).

An exception is a departure from something else. SP 800-40 Rev. 4 uses the word for maintenance plans: "Organizations should closely track and monitor all exceptions to maintenance plans," and "having some exceptions is inevitable" ([Section 3.5.5](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf)). SP 800-53 Rev. 5 uses "deviations": CM-6 c requires organizations to "Identify, document, and approve any deviations from established configuration settings" ([CM-6](https://github.com/usnistgov/oscal-content/blob/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json)). Neither text says who approves, or whether residual risk must be accepted.

Uses of the two words in the primary sources; all read 19 Nov 2026. The 800-53 clauses are from the OSCAL catalog of Rev. 5 ([source](https://github.com/usnistgov/oscal-content/blob/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json)).

| Term | What it governs | Who decides in the text | Source |
|---|---|---|---|
| Risk acceptance | A residual risk that stays | The authorizing official for US federal systems; the policy elsewhere | SP 800-39 Task 3-1; SP 800-37 Rev. 2 Task R-4 |
| Exception to a maintenance plan | An asset that cannot follow its patch plan | Not stated; track and review regularly | SP 800-40 Rev. 4, Section 3.5.5 |
| Deviation from a configuration setting | A setting that differs from the baseline | "approve" is required; the role is not named | SP 800-53 Rev. 5, CM-6 c |
| Permit by exception | A deny-all rule with a list of allowed programs or traffic | Not a risk decision; a control | SP 800-53 Rev. 5, CM-7(5) and SC-7(5) |
| Waiver or exception to a federal directive | Not available | Nobody: CISA "does not issue waivers or exceptions" | [BOD 26-04 guidance](https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk) |

SP 800-40 Rev. 4 also pushes against exceptions as a habit. "Instead of denoting certain assets or types of assets as 'exceptions,' there should be maintenance groups for them," and assets with similar long-term exceptions "might need to be moved to a separate maintenance group with its own maintenance plan." A medical device or legacy controller that is renewed every quarter as an exception is telling the team to build a plan for that class.

## Which record does a late patch need

Decision table for choosing the record. The sources name no approver for exceptions, so the policy must; the first row assumes it does.

| Is the asset departing from a rule or plan? | Does a risk remain that someone must own? | Record needed |
|---|---|---|
| Yes | No: the control or the fix closes the gap inside the exception period | Exception only, approved by whoever owns the plan |
| Yes | Yes: the gap is open during the exception | Exception, plus a signed acceptance with its own expiry |
| No | Yes: a risk is kept and no rule is bent | Acceptance only |
| No | No | Neither; fix it in the normal cycle |

The two records have different owners and lifetimes. An exception ends when the plan can be followed or the period lapses. An acceptance ends at its own date or when a reopen trigger fires. One exception can rest on an acceptance, and the [exception register](https://remediationvsmitigation.com/exception-register/) links the two rows; the [risk register versus exception register guide](https://remediationvsmitigation.com/guides/risk-register-vs-exception-register/) covers the layout.

## Two hosts, one late patch

CVE-2026-80521 is a use-after-free in the Linux kernel's AF_UNIX garbage collector. An attacker must already run code on the host as an unprivileged user and win a narrow race. The 6.1 stable fix shipped in Linux 6.1.189 on 3 Oct 2026 ([changelog](https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.189)), and the CVE was not in the CISA catalog in version 2026.11.18 ([NVD record](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-80521), [KEV feed](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json)). The maintenance plan below is invented: kernel fixes within 30 days of release, so the due date is 2 Nov 2026.

Host B needs an exception only; Host A needs an exception with an acceptance behind it. The CVE facts and fix date are real; the hosts, the plan, the people and the approvals are invented.

|  | Host B, backup appliance | Host A, shared build server |
|---|---|---|
| Who can run code locally | Three administrators; no unprivileged users | About 40 developers with shell accounts |
| Why the plan is missed | Reboot needs a window; the next is 14 Nov 2026 | Release freeze until 15 Dec 2026 |
| Late by | 12 days | 43 days |
| Risk that remains | None beyond what the three administrators already hold | An unprivileged user could reach the flaw while the patch is waiting |
| Record | Exception to the maintenance plan, approved by the plan owner on 30 Oct 2026 | Exception requested 28 Oct 2026; acceptance signed by the security head on 29 Oct 2026, expiry 15 Dec 2026 |
| Controls named | None needed | Developer logins limited to a jump host; unusual process creation by the build user alerted; both checked 29 Oct 2026 |
| Reopen when | Window moves again | The CVE reaches the catalog; either control fails |
| Closed | 14 Nov 2026, after the kernel version check | Planned 15 Dec 2026 |

Writing "exception" on Host A's record would have left the signer's name off it. A reviewer reading it would learn which rule was bent but not who accepted the exposure of 40 accounts for 43 days. Writing "acceptance" on Host B's would have sent a signer a decision with no risk in it. The word on the record tells a reader which question was answered. How the end of each period is handled is in [risk exception expiry](https://remediationvsmitigation.com/guides/exception-expiry-and-renewal/), and the tests behind Host A's signature are in [risk acceptance criteria](https://remediationvsmitigation.com/guides/risk-acceptance-criteria/).

## Sources

- NIST SP 800-39, Task 3-1: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-39.pdf (read 19 Nov 2026)
- NIST SP 800-37 Rev. 2, Task R-4: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf (read 19 Nov 2026)
- NIST SP 800-40 Rev. 4, Sections 3.4 and 3.5.5: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf (read 19 Nov 2026)
- NIST SP 800-53 Rev. 5 catalog (OSCAL), CM-6, CM-7(5), SC-7(5): https://github.com/usnistgov/oscal-content/blob/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json (read 19 Nov 2026)
- CISA BOD 26-04 implementation guidance, waiver question: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk (read 19 Nov 2026)
- NVD record, CVE-2026-80521: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-80521 (read 19 Nov 2026)
- kernel.org, ChangeLog-6.1.189: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.189 (read 19 Nov 2026)
- CISA Known Exploited Vulnerabilities feed, version 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

- [Exception Register: 15 Columns, States and Blank CSV](https://remediationvsmitigation.com/exception-register/index.md)
- [Risk Acceptance Form: Free Template With 15 Fields](https://remediationvsmitigation.com/risk-acceptance-form/index.md)
- [Risk Acceptance Criteria: 7 Tests From NIST and CISA](https://remediationvsmitigation.com/guides/risk-acceptance-criteria/index.md)
- [Risk Register vs Exception Register: How They Link](https://remediationvsmitigation.com/guides/risk-register-vs-exception-register/index.md)
- [Risk Exception Expiry: What Happens and How to Renew](https://remediationvsmitigation.com/guides/exception-expiry-and-renewal/index.md)
- [Application Allow-Listing as a Compensating Control](https://remediationvsmitigation.com/compensating-controls/application-allow-listing/index.md)
