What is a risk register used for?
NIST defines a risk register as a repository of risk information including the data understood about risks over time (NIST IR 8286 and SP 800-221). NISTIR 8170 adds that it covers both accepted risks and risks with a planned mitigation path. In practice, a register does four jobs:
- Prioritize: Rank risks by exposure so limited time and budget go to the risks that matter most.
- Assign accountability: Give every risk a named owner with the authority to act on it.
- Track decisions: Record whether each risk is being mitigated, accepted, avoided, shared, or transferred, and why.
- Report upward: Feed leadership and the board a consistent view of risk that changes as conditions change.
The NIST IR 8286 series, revised in December 2025, describes how system and organization-level cybersecurity risk registers roll up into an enterprise risk register. That roll-up is what lets a cloud misconfiguration risk sit in the same conversation as financial or operational risk. The register is also where framework requirements meet reality: ISO 27001, SOC 2, and the NIST Cybersecurity Framework all expect a documented risk assessment, and the register is its output.
What fields should a risk register include?
The fields below follow the cybersecurity risk register described in the NIST IR 8286 series. The last two rows are common practitioner additions that connect the register to control testing.
| Field | What it captures |
|---|---|
| ID | A unique, stable identifier such as R-014 |
| Priority | Relative rank among all risks in the register |
| Risk description | The scenario: what could happen, how, and the consequence |
| Risk category | A grouping used for roll-up, such as security, privacy, or supply chain |
| Likelihood | How probable the scenario is, on a defined scale |
| Impact | How severe the consequence would be, on a defined scale |
| Exposure rating | The combined result of likelihood and impact |
| Risk response type | Accept, avoid, mitigate, share, or transfer |
| Risk response cost | Estimated cost of carrying out the response |
| Risk response description | The specific actions or controls that make up the response |
| Risk owner | The accountable role and named designee |
| Status | Open, closed, pending, waived, transferred, or a more detailed note |
| Related controls | Control IDs that mitigate the risk (practitioner addition) |
| Next review date | When the entry must be re-evaluated (practitioner addition) |
NIST IR 8286 Rev. 1 publishes a Risk Register Schema and a Risk Detail Record Schema in JSON and Excel as supplemental materials. Starting from that schema keeps your register compatible with how federal agencies and many enterprises already structure risk data.
What is an example of a risk register entry?
A good entry reads like a scenario with a cause, an event, and a consequence, and it points to specific controls. Vague entries such as "cyber attack" cannot be owned or measured.
| ID | Risk description | L / I | Response | Owner |
|---|---|---|---|---|
| R-014 | A storage bucket holding customer exports is created without encryption or with public access, exposing customer data and triggering breach notification. | Low / High | Mitigate: CI policy check plus AWS Config rule (SC-28, SC-7) | VP Engineering |
| R-022 | A payroll vendor suffers a breach that exposes employee personal data. | Medium / Medium | Share: contractual security terms, annual SOC 2 review, cyber insurance | Head of People |
| R-031 | A former employee retains SaaS access after termination and exports internal data. | Medium / High | Mitigate: SSO-only access with automated deprovisioning (AC-2) | IT Director |
| R-040 | A legacy reporting tool cannot support MFA, allowing password-only access. | Low / Medium | Accept until Q2 retirement, with network isolation as a compensating control | CTO |
How do you build and maintain a risk register?
- Define scales first. Agree on what low, medium, and high likelihood and impact mean, ideally with concrete thresholds. NIST SP 800-30 provides example assessment scales you can adapt.
- Identify risks. Work from threat sources, threat events, and vulnerabilities, plus inputs like incidents, audit findings, and vendor assessments.
- Analyze and rate. Score likelihood and impact, considering the controls already in place.
- Choose a response and owner. Pick one of the five responses from NIST SP 800-39 and name an owner who can fund and execute it. Acceptance should be signed off by someone with the authority to accept.
- Review on a cadence. Revisit entries when conditions change and review the full register regularly, reporting top risks to leadership.
Risk assessments for AI systems follow the same pattern with different threat sources. See the AI risk assessment guide for that variant.
How do GRC engineers automate a risk register?
The weakness of a spreadsheet register is that it goes stale between reviews. GRC engineers fix that by storing each risk as structured data in Git, validating it against a schema in CI, and linking it to the controls that mitigate it:
id: R-014
title: Unencrypted or public customer export bucket
description: >
A storage bucket holding customer exports is created without
encryption or with public access, exposing customer data and
triggering breach notification obligations.
category: information-security
likelihood: low
impact: high
exposure: medium
response:
type: mitigate
description: CI policy check and AWS Config rules enforce encryption and block public access
cost_estimate_usd: 4000
related_controls: [SC-28, SC-7, CC6.1]
owner:
role: VP Engineering
designee: jordan.lee
status: open
next_review: 2026-12-31With risks as data, a scheduled job can read continuous monitoring results and raise the likelihood of R-014 when an SC-28 check fails, open a ticket for the owner, and flag entries past their review date. Pull requests become the audit trail for every rating change and acceptance decision. The same YAML can be exported to the NIST IR 8286 schema for enterprise reporting.
Frequently asked questions
What is a risk register?
A risk register is a central record of identified risks and the information needed to manage them, including a description, likelihood, impact, owner, chosen response, and status. NIST defines it as a repository of risk information including the data understood about risks over time. It is the working tool of any risk management program.
What fields should a risk register have?
NIST IR 8286 describes a cybersecurity risk register with an identifier, priority, risk description, risk category, likelihood, impact, exposure rating, risk response type, response cost, response description, risk owner, and status. Many teams add related controls and a next review date so the register connects to control testing.
What are the risk response options?
NIST SP 800-39 lists five risk responses: accept, avoid, mitigate, share, or transfer. Mitigation means implementing controls to reduce likelihood or impact. Transfer and sharing move some consequences to another party, such as an insurer or a vendor under contract, and acceptance is a documented decision by someone with authority to live with the risk.
Who owns the risk register?
The risk or GRC function usually maintains the register, but each individual risk should have a named owner with the authority and budget to act on it. NIST IR 8286C recommends recording both the owner role and the specific designee, and periodically confirming the designee is still correct.
How often should a risk register be updated?
Update entries whenever something material changes, such as a new system, a failed control, an incident, or a vendor change. Review the full register on a set cadence, commonly quarterly, and report the top risks to leadership. A register touched only once a year for an audit will not reflect current risk.
Is there a standard risk register template?
NIST IR 8286 Rev. 1, published in December 2025, includes a Risk Register Schema and a Risk Detail Record Schema as supplemental materials in both JSON and Excel formats. Those are a sound, vendor-neutral starting point that you can extend with fields your organization needs.