Risk register vs exception register

A risk register records risks and the responses chosen; an exception register records approved departures from a rule, plan or setting, each with an end date. NIST IR 8286 lists 12 risk register elements; the exception register has 15 columns. Two fields join them: finding_ref and vulnerability_state.

  1. Remediate
  2. Mitigate now, fix later
  3. Accept with a dated exceptionThis page is about it

Two records, two questions

NIST's glossary gives two definitions of a risk register. One, from OMB Circular A-11, is "A repository of risk information including the data understood about risks over time." The other, from NISTIR 8170, is "A central record of current risks, and related information, for a given scope or organization." It adds that current risks are both accepted risks and risks with a planned mitigation path. So a risk register already holds accepted risks. It has no lifecycle for each departure from a rule, which is the job of the exception register.

The 12 elements against the 15 columns

Elements from NIST IR 8286, Table 2. All 12 appear: priority, category, likelihood, impact, exposure and response cost are in the row marked none, and the other six are paired with columns. The pairing is a reading of the two. Read 19 Nov 2026.
NIST IR 8286 elementException register columnReading
ID (Risk Identifier)exception_idEach register carries its own ID: the risk register holds the risk ID (R-0207 in the case below), the exception register holds exception_id (EX-0031). The exception row names the risk ID in finding_ref, and the risk row names the exception ID in its response description
Risk Descriptionfinding_ref, assetThe register holds the pointer; the form holds the scenario
Risk Response TyperesponseIR 8286 has accept, transfer, mitigate, avoid; the exception register has accepted, interim mitigation, vendor dependency
Risk Response Descriptioncontrol_ids, plan_milestone_dateControls link to the compensating control entries
Risk Ownerapprover_roleNot the same: the approver signs, the owner manages; see who is the risk owner
Statusvulnerability_stateIR 8286 leaves terms to the organization; the register fixes six FedRAMP values for the finding
Priority, Risk Category, Current Assessment (likelihood, impact, exposure), Risk Response CostnoneHeld on the risk acceptance form or the risk register
noneexception_state, decision_date, expiry_date, next_review_date, vendor_last_checkin, closed_date, closure_evidenceThe state of the exception itself, its dates and the closing proof are what the exception register adds

The exception register has 15 columns. Eight are paired in the table (exception_id, finding_ref, asset, response, control_ids, plan_milestone_date, approver_role and vulnerability_state). Seven are its own: exception_state, decision_date, expiry_date, next_review_date, vendor_last_checkin, closed_date and closure_evidence.

Two fields join the registers. First, finding_ref holds the risk register's ID (R-0207) beside the CVE ID, so an auditor can move from a departure to the risk it covers; the risk register's response description holds the exception_id (EX-0031) for the way back. Second, vulnerability_state takes the same six values as the risk register's Status, so the two rows cannot disagree about the finding. The approver and the risk owner are not a join: approver_role records who signed, and the risk owner field records who manages the risk, so the signature and the accountability can differ without confusing the record.

Who keeps each register, and how often

Maintenance and review of the two registers. The risk register column rests on NIST IR 8286 and IR 8286C; the exception register column is this site's routine. Read 19 Nov 2026.
Risk registerException register
Kept byThe risk owner for each entry; ERM leadership "should ensure that accountability" (NIST IR 8286)The register owner, who moves rows between states (exception register)
ReviewedOn the enterprise's reporting cycle: IR 8286C says that where risk is reported quarterly, register processes "need to cycle at least quarterly", and gives monthly as an example interval for confirming the ownerMonthly, by next_review_date; a row enters "renewal due" 30 days before expiry (this site's routine)
A change to one entryRe-rating, new response, new ownerNew decision, renewal as a new row, or closure with evidence

Where an entry goes

Placement by this site from the cited NIST texts. Read 19 Nov 2026.
SituationRisk registerException registerPOA&M
Accepted risk, no fix plannedYesYes, with expiryNo: SP 800-37 Rev. 2 says entries "are not necessary when deficiencies are accepted by the authorizing official as residual risk"
Mitigation waiting for a fixYesYesYes: SP 800-53 RA-7 generates a plan entry when a mitigation "cannot be completed immediately"; see the POA&M guide
Exception to a patching schedule, risk response unchangedNoYes (SP 800-40 Rev. 4 asks that exceptions be tracked closely)No
False positiveNo: closed with evidenceOnly if a row was openedNo

Statuses

NIST IR 8286C suggests a status that could be "a simple indicator (e.g., open, closed, pending, waived, transferred)" or a more detailed explanation. IR 8286B says the terms are "at the discretion of the organization, but the options available should be specified in the risk management policy and/or procedures to enable consistent review". The exception register takes the stricter route for vulnerability_state and uses six values from FedRAMP's 2026 definitions. The risk register row in the case below uses the same six values, so both registers describe one finding in one vocabulary. exception_state is separate (active, renewal due, lapsed, escalated, closed) and has no risk register counterpart:

FedRAMP Consolidated Rules for 2026, definitions, read 19 Nov 2026.
StatusFedRAMP definition (abridged)
accepted"A vulnerability that the provider does not intend to fully mitigate or remediate", or that has not been or will not be within the maximum overdue period
overdue"intends to fully mitigate or remediate but has not or will not do so within the time frames recommended or required by FedRAMP"
partially mitigated"likelihood or Potential Agency Impact N-rating has been reduced from the original evaluation but the risk of exploitation still exists and the vulnerability is still detected"
fully mitigatedreduced "until either are negligible, but the vulnerability is still detected"
remediated"neutralized or eliminated and is no longer detected"
false positive"not actually present in an exploitable state in the information resource"

Worked case: one ScreenConnect finding in both registers

The sample organization is invented; the CVE, vendor and CISA dates are real (NVD, the ConnectWise bulletin and advisory page, and the CISA KEV feed, read 19 Nov 2026). It runs ScreenConnect for its help desk, with 40 technician clients. CVE-2026-84869 (file transfer flaw, CVSS 9.9) was fixed in version 26.6.5, released 8 Sep 2026. CISA added it to KEV on 11 Sep with a due date of 14 Sep. ConnectWise's interim step, published 3 Sep, was to deselect the TransferFiles permission in every role.

Sample records using the exception register columns and FedRAMP's six status values. Vendor and CISA dates are real (ConnectWise bulletin, NVD and KEV feed 2026.11.18); the organization is invented.
Date (2026)EventRisk register R-0207Exception register EX-0031
4 SepInterim step applied: TransferFiles deselected in all rolesOpened. Response: mitigate. Owner: Head of IT Service Desk. Status: partially mitigatedNo row: no rule has been departed from
8 Sep26.6.5 releasedPlan: upgrade server and clients by 14 SepNo row
11 SepCISA adds the CVE to KEV, due 14 SepExposure re-rated; escalated to the CISONo row
14 SepServer upgraded. 11 of 40 clients at a branch office cannot be reached before the due dateStatus: partially mitigated. Response description: exception EX-0031Opened. finding_ref: CVE-2026-84869, R-0207; response: interim mitigation; exception_state: active; vulnerability_state: partially mitigated; approver_role: CISO; decision_date 14 Sep; expiry_date 25 Sep; control_ids: the TransferFiles role change; plan_milestone_date 21 Sep
15 SepDue date has passedStatus: overduevulnerability_state: overdue (exception_state stays active)
21 Sep10 of 11 clients upgraded; 1 laptop is back in the office on 24 SepUnchangednext_review_date 24 Sep
24 SepLast client upgraded; rescan shows no detectionClosed. Status: remediatedclosed_date 24 Sep; closure_evidence: rescan reference; exception_state: closed; vulnerability_state: remediated

Both rows share the finding, the dates and the final status, but they answer different questions. The risk register shows that the risk was owned and re-rated; the exception register shows that the 14 Sep rule was departed from for 10 days under a signature and that the departure ended with evidence. The word overdue in the 15 Sep rows is this site's convention: FedRAMP defines overdue against FedRAMP's own time frames, and here it is applied to the missed KEV due date of 14 Sep.

Sources

Last reviewed