Risk exception expiry and renewal
An exception that reaches its end date has not removed the risk. NIST SP 800-37 Rev. 2 lets the authorizing official set a termination date, and at review the official either acknowledges continued acceptance or requires further response. NIST sets no renewal limit. Read 19 Nov 2026.
On this page
What the date means in NIST SP 800-37
SP 800-37 Rev. 2 says "The authorization termination date is established by the authorizing official and indicates when the authorization expires." It also says the date "can be adjusted at any time by the authorizing official to reflect an increased level of concern regarding the security and privacy posture of the system." Organizations "may eliminate the authorization termination date if the system is operating under an ongoing authorization", where a time-driven review frequency replaces it. At that review: "If the risk remains acceptable, the authorizing official acknowledges the acceptance in accordance with organizational processes. If not, the authorizing official indicates that the risk is no longer acceptable and requires further risk response or a full denial of the authorization."
The text leaves the formality to the organization: it "determines the level of formality for the process of communicating and acknowledging continued risk acceptance." A renewal is therefore a fresh acknowledgment of the same fields, not a change of a date in a spreadsheet. The fields are on the risk acceptance form, and who may sign is on who may sign a risk acceptance.
Triggers that end an exception early
- Event-driven review. SP 800-37 Rev. 2 describes a review the authorizing official may require "in addition to the time-driven frequency review".
- Change monitoring. SP 800-39 lists as one purpose of monitoring to "identify risk-impacting changes to organizational information systems and the environments in which the systems operate".
- Changed facts. CISA's BOD 26-04 says "The timelines for each asset are dynamic as facts change", so an exception written for an internal asset lapses in substance if the asset becomes exposed or the CVE is added to the KEV catalog.
- Open maintenance exceptions. SP 800-40 Rev. 4 (Section 3.5.5) asks that exceptions to maintenance plans be "reviewed regularly to determine if the maintenance plan can be implemented now."
A worked case: CVE-2026-41709 on ESX hosts
The organization is invented; the CVE, the advisory and the KEV dates are real. Broadcom published advisory VMSA-2026-0006 on 29 Jul 2026 with fixed ESX builds, and NVD recorded CVE-2026-41709 on 30 Jul as Low (CVSS 3.1 base 2.7): an administrator on the host can perform some operations that leave no log entry. Broadcom lists no workaround. On 24 Aug 2026 an operations team with 40 ESX 8.0 hosts below build ESXi80U3j-25429389 signs a 90-day acceptance. The reasons: the rating is Low, the flaw needs ESX administrator rights, and the hosts are patched in the November cluster window. The controls: administrator rights limited to named accounts, management interface reachable only from a jump host, and host syslog forwarded to a collector. One reopen trigger is written on the record: the CVE appears on the KEV catalog. Day 90 is 22 Nov 2026.
| Date | Day of term | What happens |
|---|---|---|
| 24 Aug 2026 | 0 | Approver signs; expiry set to 22 Nov 2026 |
| 23 Sep 2026 | 30 | First review: facts unchanged, controls retested, exception continues |
| 23 Oct 2026 | 60 | Second review: facts unchanged, exception continues |
| 28 Oct 2026 | 65 | CISA adds the CVE to KEV with a due date of 11 Nov 2026. Its SSVC entry in NVD lists exploitation as active. The reopen trigger fires and the approver holds an event review the same day |
| 28 Oct 2026 | 65 | Decision: close the exception, patch all 40 hosts to ESXi80U3j-25429389 or later by 11 Nov, and review the administrator-account list and host logs against vCenter task history |
| 11 Nov 2026 | 79 | KEV due date. Closure evidence: build number per host from esxcli system version get. Exception closed |
| 22 Nov 2026 | 90 | Original expiry. Nothing is left to lapse |
The scheduled reviews were never going to catch this. The 23 Oct review came five days before the listing, and the end date of 22 Nov fell 11 days after the KEV due date. An exception that waited for its expiry would have kept hosts unpatched through a listing for known exploitation. Only the written trigger and an event review moved the decision to 28 Oct. A federal civilian agency would have had no choice at all: CISA states that it "does not issue waivers or exceptions for actions required in cyber directives".
What the approver is given at renewal
- List what changed since the last signature. Owner: the exception owner. Record: KEV status, vendor fix status, exposure, whether the scanner finding is still open. In the case above this list, dated 28 Oct, is what ended the exception.
- Retest every control named in the exception. Owner: the control owner. Record: a test result with date and tester. SP 800-40 Rev. 4 asks that additional controls be confirmed "functioning as intended" and that the response "continues to be in place". This is where renewals usually fail: the control was never rechecked.
- Confirm the risk owner. NIST IR 8286C suggests reviewing monthly that the risk owner is still the appropriate designee, so confirm the owner before the choice, not after.
- Choose renew, close or escalate (table below). Owner: the risk owner proposes, the approver decides. Record: the choice with its reason in one sentence.
- Obtain a new acknowledgment from the approver, with a new date and a new end date. Owner: the approver named in the original record, or that role's successor. Record: a signature and date on a new version of the record, linked to the old one. Editing the old end date leaves no evidence that anyone decided.
| Outcome | What the sources require | Evidence |
|---|---|---|
| Renew | A fresh acknowledgment by the signer (SP 800-37 Rev. 2) | New signature and date, current residual risk |
| Close | Verify the response: patch installed, controls "functioning as intended", or asset decommissioned (SP 800-40 Rev. 4) | Rescan result, change ticket or decommission record |
| Escalate | Risk elevation to a more senior stakeholder (IR 8286B) | Named new owner and decision date |
How the register marks a row as renewal due, lapsed or closed, and the monthly review that opens a renewal 30 days before the end date, are on the exception register.
When renewal is the wrong answer
Renewal is wrong when the facts that justified the exception are gone. Close instead if the vendor fix exists, escalate if the CVE is now on the KEV catalog, and stop if a control failed its retest. A KEV listing also shortens the clock: BOD 26-04 starts its timeline on the earlier of the catalog addition and the agency's own identification of the flaw.
Repetition is a signal too. NIST IR 8286B gives an escalation example for risk left without treatment: "a risk that has remained through more than two fiscal periods without adequate treatment might be flagged for additional scrutiny." Neither IR 8286B nor IR 8286C sets an exception lifetime.
For FedRAMP providers the 2026 rules do set a ceiling of a kind. "Providers MUST categorize any vulnerability that is not or will not be fully mitigated or remediated within 192 days of evaluation as an accepted vulnerability" (VER-TFR-MAV), and an accepted vulnerability is one 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" (FedRAMP definitions). It is a reporting category, not a permission; the dates are on maximum durations. The legacy playbook said approved operational requirements "are still considered open risks" that must be "periodically reassessed", and its deviation form listed Pending, Approved, Rejected and Withdrawn as statuses.
Where the exception covers unsupported software, see accepting risk on end-of-life software.
Sources
- NIST SP 800-37 Rev. 2, Task R-4 and Appendix F, read 19 Nov 2026
- NIST SP 800-39, risk monitoring, read 19 Nov 2026
- NIST SP 800-40 Rev. 4, Sections 2.2 and 3.5.5, read 19 Nov 2026
- NIST IR 8286B, Section 2.4.3 (escalation and elevation), read 19 Nov 2026
- NIST IR 8286C (periodic review of the risk owner), read 19 Nov 2026
- FedRAMP legacy playbook, POA&M, read 19 Nov 2026
- FedRAMP legacy Vulnerability Deviation Request Form, status list, read 19 Nov 2026
- FedRAMP 2026 definitions, Accepted Vulnerability, read 19 Nov 2026
- FedRAMP 2026, VER-TFR-MAV, read 19 Nov 2026
- CISA BOD 26-04, Appendix A, read 19 Nov 2026
- Broadcom advisory VMSA-2026-0006 (CVE-2026-41709), read 19 Nov 2026
- NVD record, CVE-2026-41709, read 19 Nov 2026
- CISA KEV feed, catalogVersion 2026.11.18, CVE-2026-41709, read 19 Nov 2026
- CISA BOD 26-04 implementation guidance, FAQ on waivers, read 19 Nov 2026
Last reviewed