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.
On this page
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
| NIST IR 8286 element | Exception register column | Reading |
|---|---|---|
| ID (Risk Identifier) | exception_id | Each 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 Description | finding_ref, asset | The register holds the pointer; the form holds the scenario |
| Risk Response Type | response | IR 8286 has accept, transfer, mitigate, avoid; the exception register has accepted, interim mitigation, vendor dependency |
| Risk Response Description | control_ids, plan_milestone_date | Controls link to the compensating control entries |
| Risk Owner | approver_role | Not the same: the approver signs, the owner manages; see who is the risk owner |
| Status | vulnerability_state | IR 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 Cost | none | Held on the risk acceptance form or the risk register |
| none | exception_state, decision_date, expiry_date, next_review_date, vendor_last_checkin, closed_date, closure_evidence | The 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
| Risk register | Exception register | |
|---|---|---|
| Kept by | The risk owner for each entry; ERM leadership "should ensure that accountability" (NIST IR 8286) | The register owner, who moves rows between states (exception register) |
| Reviewed | On 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 owner | Monthly, by next_review_date; a row enters "renewal due" 30 days before expiry (this site's routine) |
| A change to one entry | Re-rating, new response, new owner | New decision, renewal as a new row, or closure with evidence |
Where an entry goes
| Situation | Risk register | Exception register | POA&M |
|---|---|---|---|
| Accepted risk, no fix planned | Yes | Yes, with expiry | No: 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 fix | Yes | Yes | Yes: 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 unchanged | No | Yes (SP 800-40 Rev. 4 asks that exceptions be tracked closely) | No |
| False positive | No: closed with evidence | Only if a row was opened | No |
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:
| Status | FedRAMP 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 mitigated | reduced "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.
| Date (2026) | Event | Risk register R-0207 | Exception register EX-0031 |
|---|---|---|---|
| 4 Sep | Interim step applied: TransferFiles deselected in all roles | Opened. Response: mitigate. Owner: Head of IT Service Desk. Status: partially mitigated | No row: no rule has been departed from |
| 8 Sep | 26.6.5 released | Plan: upgrade server and clients by 14 Sep | No row |
| 11 Sep | CISA adds the CVE to KEV, due 14 Sep | Exposure re-rated; escalated to the CISO | No row |
| 14 Sep | Server upgraded. 11 of 40 clients at a branch office cannot be reached before the due date | Status: partially mitigated. Response description: exception EX-0031 | Opened. 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 Sep | Due date has passed | Status: overdue | vulnerability_state: overdue (exception_state stays active) |
| 21 Sep | 10 of 11 clients upgraded; 1 laptop is back in the office on 24 Sep | Unchanged | next_review_date 24 Sep |
| 24 Sep | Last client upgraded; rescan shows no detection | Closed. Status: remediated | closed_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
- NIST CSRC glossary, risk register, read 19 Nov 2026
- NIST IR 8286, Tables 2 and 3, read 19 Nov 2026
- NIST IR 8286B, Sections 2.4.3 and 2.4.4, read 19 Nov 2026
- NIST IR 8286C, risk register guidance, read 19 Nov 2026
- NIST SP 800-37 Rev. 2, Appendix D roles and Task R-4, read 19 Nov 2026
- NIST SP 800-53 Rev. 5 catalog (OSCAL), controls PM-9 and RA-7, read 19 Nov 2026
- FedRAMP Consolidated Rules for 2026, definitions of vulnerability terms, read 19 Nov 2026
- NVD record for CVE-2026-84869, with the CISA KEV date and due date it carries, read 19 Nov 2026
- ConnectWise security bulletin, ScreenConnect 26.6.5, 8 Sep 2026 (CVE-2026-84869, TransferFiles mitigation), read 19 Nov 2026
- ConnectWise trust center advisories, interim Guest File Transfer advisory of 3 Sep 2026, read 19 Nov 2026
- CISA KEV feed, catalog version 2026.11.18: CVE-2026-84869 added 11 Sep 2026, due 14 Sep 2026, read 19 Nov 2026
Last reviewed