Exception register

The register has 15 columns, a filled example row and a blank CSV header. Two fields hold status: exception_state tracks the exception itself, and vulnerability_state uses FedRAMP's six 2026 vulnerability definitions. Keeping them apart lets an expired exception and a still-detected finding both show. Read 19 Nov 2026.

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

The 15 columns, with one row filled in

One row is one signed Risk Acceptance Form or one interim mitigation waiting on a fix. The filled row is an invented organization's record of a real finding, as it stands on 19 Nov 2026: CVE-2026-65660, a SharePoint Server code-injection flaw that CISA added to KEV on 25 Sep 2026 with a due date of 28 Sep 2026 (CISA KEV feed 2026.11.18). Microsoft's fixed build for SharePoint 2019 is 16.0.10417.20198, delivered as two packages: KB5002894 (Core) and KB5002896 (Language Pack). A private company can sign this exception. A federal civilian agency cannot waive a KEV due date, because "CISA does not issue waivers or exceptions for actions required in cyber directives" (BOD 26-04 implementation guidance).

Column definitions and the form field each comes from. Example values are invented except the CVE, the KEV dates and the fixed build, which are real (read 19 Nov 2026). The row is in renewal due because its expiry, 12 Dec 2026, is 23 days after the read date.
ColumnHoldsFilled rowForm field
exception_idYour own number, unique and never reusedEX-2026-0311
finding_refCVE ID and scanner finding IDsCVE-2026-656601
assetSystem IDs, environment, exposureSP-FARM-02, SharePoint Server 2019 below build 16.0.10417.20198, prod, internal with partner VPN access3
responseaccepted, interim mitigation or vendor dependencyinterim mitigation7, 12
exception_stateactive, renewal due, lapsed, escalated or closed (defined below)renewal dueNot on the form
vulnerability_stateOne of the six FedRAMP states (defined below), as of the last scanpartially mitigatedNot on the form
approver_roleRole that signed; the name stays on the formCISO13
decision_dateDate of signature, as YYYY-MM-DD28 Sep 202613
expiry_dateDate the exception lapses unless renewed12 Dec 202614
next_review_dateNext review under the cadence in field 1030 Nov 202610
control_idsCompensating control entries usedCC-007 (anonymous viewing off), CC-012 (partner access through the VPN only)8
plan_milestone_dateDate of the next milestone26 Nov 2026 (patch in the change window)9
vendor_last_checkinDate of the last vendor contact; blank if no vendor fix is awaitedblank: the fix exists12
closed_dateDate the exception was closedblankNot on the form
closure_evidenceRescan reference, change ticket or decommission recordblankNot on the form

Blank header and empty row for a spreadsheet or database import:

exception_id,finding_ref,asset,response,exception_state,vulnerability_state,approver_role,decision_date,expiry_date,next_review_date,control_ids,plan_milestone_date,vendor_last_checkin,closed_date,closure_evidence
,,,,,,,,,,,,,,

The same header is in the downloadable CSV.

Two status fields, kept apart

A finding has a state, and so does the exception that covers it. A register with one status column loses one of them: an exception can lapse while the scanner still detects the flaw, and a flaw can be fixed while the paperwork is still open. FedRAMP's 2026 definitions describe the finding. The exception lifecycle below is this register's own; no standard defines it.

Exception lifecycle defined by this register.
exception_stateMeaningWho moves itMoves to
activeSigned and inside its expiry dateApprover signsrenewal due, escalated or closed
renewal dueExpiry is 30 days away or lessRegister owner, on the monthly reviewclosed (renewed as a new row), lapsed or escalated
lapsedExpiry date passed with no signatureRegister ownerescalated, or closed if the finding is remediated
escalatedSent to a senior owner under criteria written in advanceRegister ownerclosed, or a new row with a new decision
closedRemediated, false positive, decommissioned or renewed as a new rowRegister owner, only with closure_evidenceTerminal

A renewal is a new signature. Copy the row to a new exception_id with the new decision_date and expiry_date, then set the old row to closed with closure_evidence "renewed as EX-...". The old row stays as the audit trail and no ID is reused.

FedRAMP Consolidated Rules for 2026, definitions, read 19 Nov 2026. FedRAMP writes them for cloud providers; the register borrows the vocabulary.
vulnerability_stateFedRAMP definition (2026)Expected response
accepted"A vulnerability that 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"accepted
overdue"intends to fully mitigate or remediate but has not or will not do so within the time frames recommended or required by FedRAMP"vendor dependency, or a late patch
partially mitigated"likelihood or Potential Agency Impact N-rating has been reduced from the original evaluation but the risk of exploitation still exists"interim mitigation
fully mitigated"reduced from the original evaluation until either are negligible, but the vulnerability is still detected"interim mitigation, scanner still reports it
remediated"neutralized or eliminated and is no longer detected"Closes the row: rescan evidence
false positive"not actually present in an exploitable state in the information resource"Closes the row: evidence of why

An interim mitigation row therefore carries partially mitigated or fully mitigated, never remediated. A remediated or fully mitigated vulnerability cannot also be a false positive; FedRAMP's definition of false positive says so. When vulnerability_state reaches remediated or false positive, exception_state becomes closed. The false positive route is in vulnerability false positive handling.

The monthly review routine

  1. Sort by expiry_date. Every row expiring within 30 days moves to renewal due; the approver renews in writing or the row moves on.
  2. Sort by next_review_date and clear every row that is due. NIST SP 800-40 Rev. 4 asks that exceptions be "reviewed regularly to determine if the maintenance plan can be implemented now" (Section 3.5.5).
  3. Re-check each control_ids entry. NIST SP 800-40 Rev. 4 step 3d says to make sure no one "deactivates the additional security controls" (Section 2.2).
  4. Look up each finding_ref on the CISA KEV catalog. A KEV listing reopens the row; for a federal civilian agency the BOD 26-04 date then applies and no waiver exists.
  5. Read vendor_last_checkin. The legacy FedRAMP playbook asks for a check "at least once a month".
  6. Close rows only with closure_evidence. A row marked remediated needs a rescan that no longer detects the finding, because that is what FedRAMP's definition requires.

In the filled row, expiry on 12 Dec 2026 put EX-2026-031 into renewal due on 12 Nov 2026, 30 days earlier, whether or not any milestone was met. At the 19 Nov review step 1 lists it. If the patch lands on the 26 Nov milestone, the row closes with the rescan as closure_evidence; if not, the approver signs a renewal as a new row before 12 Dec or the row lapses. Step 4 applies from day one, because the CVE was already on KEV when the row was signed on 28 Sep.

Accepted rows stay on the register

The legacy FedRAMP playbook says "Approved ORs are still considered open risks" and that they must be "periodically reassessed". Expiry does not remove a row: it moves to closed, lapsed or escalated, never to deleted. Two other pages explain the neighbors: risk acceptance versus risk exception for why a register holds both kinds of row, and risk register versus exception register for how the two link. Expiry rules are in risk exception expiry, rows waiting on a fix in the POA&M guide, and the monthly control check in verifying a mitigation.

Sources

Last reviewed