Risk acceptance vs risk tolerance
Risk tolerance is the level of risk an organization will bear, written once for many decisions. Risk acceptance keeps one named finding because it falls inside that level. NIST SP 800-39 calls acceptance "the appropriate risk response when the identified risk is within the organizational risk tolerance" (read 19 Nov 2026).
On this page
What NIST says tolerance is
The NIST glossary lists several definitions of risk tolerance, each taken from a different publication. Acceptance is defined by its response text in SP 800-39, quoted in the next section.
| Source | Wording of "risk tolerance" | What it adds |
|---|---|---|
| NIST SP 800-53 Rev. 5 (from SP 800-39) | "The level of risk or the degree of uncertainty that is acceptable to an organization." | Covers uncertainty as well as level |
| NIST SP 800-137 | "The level of risk an entity is willing to assume in order to achieve a potential desired result." | Tied to a goal |
| NIST IR 8286 (adapted from ISO Guide 73) | "The organization's or stakeholder's readiness to bear the remaining risk after responding to or considering the risk in order to achieve its objectives." | Measured on the risk that remains after a response |
| NIST SP 800-221 (from OMB Circular A-123) | "The acceptable level of variance in performance relative to the achievement of objectives." | Defined as variance in performance |
| NIST SP 800-221 (from ISO Guide 73) | "The readiness of an organization or stakeholders to bear the remaining risk after responding to or considering the risk to achieve its objectives (while recognizing that such tolerance can be influenced by legal or regulatory requirements)" | Law and regulation can narrow it |
Tolerance is set above the finding, acceptance at it
SP 800-39 puts tolerance in the organization-wide tier: "Risk tolerance is the level of risk or degree of uncertainty that is acceptable to organizations and is a key element of the organizational risk frame." It adds that "There is no correct level of organizational risk tolerance", and that the degree is "generally indicative of organizational culture", "potentially different for different types of losses/compromises" and shaped by the individual views of senior executives.
SP 800-53 PM-9 says the risk management strategy "includes an expression of the security and privacy risk tolerance for the organization". RA-7 requires that findings from assessments, monitoring and audits be responded to "in accordance with organizational risk tolerance". So the person asked to accept one finding starts from a document someone else wrote. If it is silent on vulnerabilities, the risk acceptance criteria have nothing to be tested against.
Acceptance is the response at the finding. SP 800-39: "Risk acceptance is the appropriate risk response when the identified risk is within the organizational risk tolerance. Organizations can accept risk deemed to be low, moderate, or high depending on particular situations or conditions." NIST IR 8286, Table 3, adds the working consequence: for Accept, "No additional risk response action is needed except for monitoring." The same table pairs Transfer with risks "that fall outside of tolerance levels"; see risk transfer versus risk acceptance.
The quantity compared with tolerance is residual risk. SP 800-39 Task 3-3 has organizations "determine acceptable degrees of residual risk based on organizational risk tolerance and the specific risk tolerances of particular decision makers". How to state the remaining level is covered in residual risk after mitigation.
Sorting a statement into the right word
Appetite is the third word. NIST IR 8286 quotes OMB Circular A-123: appetite "is the broad-based amount of risk an organization is willing to accept in pursuit of its mission/vision", set by the most senior leadership, while tolerance is "generally established at the program, objective, or component level". For a vulnerability record, tolerance is the one that matters, because it can be written for a class of systems or findings.
| Statement | What it is | Why | Where it lives |
|---|---|---|---|
| Leadership will take more risk to enter a new market | Appetite | Broad amount of risk in pursuit of the mission | Strategy, board papers |
| A day of intranet downtime is bearable, a day of payment downtime is not | Tolerance | Differs by type of loss (SP 800-39) | Risk management strategy (PM-9) |
| No internet-facing system may carry a known exploited vulnerability past its CISA due date | Tolerance, written as a limit on findings | Sets what RA-7 responses are compared with | Vulnerability policy |
| Accept anything below CVSS 8.0 | A proxy for tolerance, not tolerance | Severity is one input; exploitation can change while the rating stays put (see the case below) | Often found in scanner settings |
| Host reporting-01 keeps finding F-4417 until 17 Feb 2027, signed by the director | Acceptance | One finding, one signer, one expiry | Risk acceptance form and exception register |
| Patching on host X may run 10 days past the monthly cycle | Exception to a rule | A departure from a plan, not a statement about risk level | Exception register; see acceptance versus exception |
Worked case: a local-access kernel flaw that left tolerance on day 149
The sample organization below is invented. The CVE facts are real, from the NVD and Red Hat records and the CISA catalog read 19 Nov 2026. Its tolerance statement for internal Linux servers:
SAMPLE tolerance statement TS-4 (invented organization)
The infrastructure director may accept a finding on an internal Linux server for up to 180 days when all four hold:
- CVSS base score below 8.0.
- Not on the CISA KEV catalog.
- The attacker needs local access (CVSS attack vector Local).
- A mitigation the vendor documents is in place and has been checked.
If any condition stops holding, the acceptance ends that day and the finding is treated as unaccepted.
CVE-2026-46300 ("Fragnesia") is a Linux kernel flaw in socket buffer coalescing: a local low-privilege user can alter cached copies of read-only files and reach root. NVD gives it a CVSS 3.1 base of 7.8 (AV:L/AC:L/PR:L). Red Hat released the fixed RHEL 9 kernel, kernel-5.14.0-687.10.1.el9_8 (RHSA-2026:19568), on 20 May 2026, and names blocking the esp4 and esp6 IPsec modules as a mitigation where IPsec is not in use.
- 1 Jun 2026: all four conditions hold (7.8 is below 8.0; not in the catalog; local access; the esp4 and esp6 modules are blocked and a module listing confirms it, on a server that does not use IPsec). The reason, invented, is that the database vendor has not yet certified the fixed kernel for this host. The director signs an acceptance for 180 days, expiring 28 Nov 2026. Field 7 of the risk acceptance form cites TS-4 and field 11 records residual risk as Low.
- 28 Oct 2026, day 149 of 180: CISA adds the CVE to the KEV catalog, with a due date of 31 Oct 2026, 3 days later. Condition 2 fails. By the statement's own words the acceptance ended on 28 Oct, not on 28 Nov.
- 28 to 30 Oct 2026: the finding goes to the decision table as unaccepted. The database vendor's certification is escalated, the fixed kernel is installed and the host rebooted on 30 Oct, a day before the due date. The record keeps the 1 Jun acceptance as closed on 28 Oct, with the reason.
A tolerance written only as "CVSS below 8.0" would have left the acceptance in force for 31 more days, until 28 Nov 2026, because the base score stayed 7.8 throughout. The statement also shows the limit of its own wording: NVD has carried CISA's SSVC mark of exploitation "active" for this CVE since 14 May 2026, 18 days before the acceptance, and condition 2 looks only at the catalog. A statement that added "no active exploitation in CISA's SSVC data" would have refused the acceptance on 1 Jun. Which signals the statement names decides when an acceptance ends.
Sources
- NIST CSRC glossary, risk tolerance, read 19 Nov 2026
- NIST SP 800-39, Section 2.3.3 and Task 3-1 (risk responses), read 19 Nov 2026
- NIST SP 800-53 Rev. 5 catalog (OSCAL), controls PM-9 and RA-7, read 19 Nov 2026
- NIST IR 8286, Tables 2 and 3, read 19 Nov 2026
- NIST SP 800-37 Rev. 2, Appendix D roles and Task R-4, read 19 Nov 2026
- NVD record for CVE-2026-46300, with CISA's KEV date, due date and SSVC data, read 19 Nov 2026
- Red Hat CVE page for CVE-2026-46300, errata and mitigation, read 19 Nov 2026
- CISA KEV catalog JSON feed, catalogVersion 2026.11.18, entry CVE-2026-46300, read 19 Nov 2026
Last reviewed