Skip to content
Compliance Automation Tools

Home / Guides / A risk register needs ten fields, a repeatable scale and a link to controls

Guide, read 13 Nov 2026

A risk register needs ten fields, a repeatable scale and a link to controls

Framework Coverage MatrixAll guides

The fields a register needs

A risk register is a table where each row is one risk scenario and every cell has an answer. A register with empty cells is a to-do list. NIST IR 8286 (October 2020) gives the clearest field list in a public source. Its Table 2 describes these elements: ID, priority, risk description, risk category, current assessment of likelihood, current assessment of impact, exposure rating, risk response type, risk response cost, risk response description, risk owner and status.

NIST's page shows IR 8286 as withdrawn on 18 Dec 2025 and superseded by IR 8286 Rev. 1. The 2020 field list is still the one I could read in full on 12 Nov 2026, so treat the Rev. 1 text as the one to check before you copy anything.

Two details from Table 2 are worth keeping. The risk description is written in cause and effect form, "if X occurs, then Y happens". And the risk category can reuse SP 800-53 control families such as Access Control (AC) or Audit and Accountability (AU), which makes a later link to controls simple.

FieldWhat goes in itExample
IDSequential number, never reusedR-031
DescriptionIf X occurs, then Y happensIf a departed engineer's token stays active, customer data can be read after exit
CategoryOne family from your control setAccess
LikelihoodValue from the scale, with a reason3 of 5, because 4 leaver tickets closed late last quarter
ImpactValue from the scale, with a reason4 of 5, customer data in scope
ExposureLikelihood combined with impact12 of 25
ResponseAccept, transfer, mitigate or avoidMitigate
OwnerOne named personHead of IT Operations
Linked controlsIDs from the house setACC-02, ACC-07
Status and next reviewOpen, treating, accepted; a dateTreating; review 15 Jan 2027

Scoring scales that two people can repeat

Pick the scale for repeatability, not precision. NIST SP 800-30 Rev. 1 (September 2012) describes three kinds of assessment: qualitative, semi-quantitative and quantitative. Qualitative uses levels such as very low, low, moderate, high and very high. The guide says unless each value is clearly defined, different experts can produce significantly different results. It adds that annotating a value with its reasons ("high because of the following") increases repeatability.

Semi-quantitative scales use bins. SP 800-30 gives 0 to 15, 16 to 35, 36 to 70, 71 to 85 and 86 to 100 as an example, and notes that a score of 95 reads as very high. It also says the difference between a 70 and a 71 is relatively insignificant.

For a scaleup, a 5 by 5 grid with written definitions is enough. Define each level with a number: for impact, 1 means under 1 hour of degraded service for one customer; 5 means customer data exposed or more than 24 hours of outage for many. Write the definitions on one page and keep them next to the register. Do not add decimals.

Risk appetite and treatment options

Risk appetite tells you which rows need action. IR 8286 quotes OMB Circular A-123, which defines appetite as the broad-based amount of risk an organization is willing to accept in pursuit of its mission. It separates this from risk tolerance, which is set closer to the program or objective. Its example appetite statement is "Email service shall be available during the large majority of a 24 hour period."

Write yours as a threshold on the scale: "We accept exposure up to 6. Above 6 needs a treatment plan. Above 15 goes to the executive team." A threshold turns a debate into a lookup.

IR 8286 Table 3 lists four response types for negative risks. Accept means staying within tolerance with monitoring only. Transfer means sharing the consequences, for example through insurance, and the document warns that consequences like lost customer trust cannot be transferred. Mitigate means applying controls to reduce the threat, vulnerability or impact. Avoid means ensuring the risk does not occur, which can be right when no cost-effective reduction exists. Record the choice, the cost and the date. Inherent and residual risk are the scores before and after treatment, so keep both.

Set two cadences. The first is a scheduled review of the whole register, quarterly for most scaleups. The second is event driven: a new product, a new vendor, an incident or a scope change. NIST SP 800-53 Rev. 5 control PM-9 requires an organization to review and update its risk management strategy at an organization-defined frequency or as required to address organizational changes. It leaves the frequency to you, so write yours down.

If you handle electronic protected health information, the floor is in law. 45 CFR 164.308(a)(1)(ii)(A) is labeled Required and reads: conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information. The next item, 164.308(a)(1)(ii)(B), is also Required: implement security measures sufficient to reduce those risks to a reasonable and appropriate level. The regulation does not set a number of months. The HIPAA page covers the framework.

Whatever the cadence, date every review and keep the previous version. A register with one undated version looks abandoned.

Linking the register to controls

A register row without a control link is an opinion. Each row should name the controls that treat it, and each control should name the risks it addresses. That two-way link answers an assessor's question: why do you test this control, and what happens if it fails.

Use the link to drive action. If a control test fails, raise the likelihood on every linked risk and flag the rows for owner review. If a risk is accepted, record the approver and the date, then follow the exception steps in policy exceptions. If a risk has no linked control, either add one to the house set or record the acceptance.

The NIST control catalog shows the same pattern. SP 800-53 Rev. 5 controls carry assessment objectives and evidence examples, and its risk-related controls tie back to the organization's strategy. In a platform, the link is usually a field on both sides; in a spreadsheet it is a column of control IDs. Either works if someone checks it every quarter.

Where this shows up in the index

16 of 16 tools have a record of a risk register in the product among the facts read on 12 Nov 2026. The risk and vendor modules criterion scores it.

Sources

  1. csrc.nist.gov/pubs/ir/8286/final, read 12 Nov 2026
  2. nvlpubs.nist.gov/nistpubs/ir/2020/NIST.IR.8286.pdf, read 12 Nov 2026
  3. csrc.nist.gov/pubs/sp/800/30/r1/final, read 12 Nov 2026
  4. nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-30r1.pdf, read 12 Nov 2026
  5. raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json, read 12 Nov 2026
  6. ecfr.gov/api/renderer/v1/content/enhanced/current/title-45?subtitle=A&subchapter=C&part=164&subpart=C&section=164.308, read 12 Nov 2026

Last reviewed 13 Nov 2026.