Research briefs · AI governance · Updated 2026-11-08

What belongs in an AI risk register?

A practical way to turn the NIST AI Risk Management Framework into owned, reviewable enterprise work.

Thesis

An AI risk register is most useful when it records context, evidence, owners, and residual risk rather than reducing governance to a model score.

Market context

Editorial analysis: A practical way to turn the NIST AI Risk Management Framework into owned, reviewable enterprise work. A useful decision framework considers ownership, exceptions, evidence, and change control alongside the technology itself.

Editorial analysis: standards and frameworks can provide shared terminology, but a citation to a standard does not establish how a particular product or organization implements it.

NIST AI RMF 1.0 has four functions—Govern, Map, Measure, and Manage—and NIST is revising the framework.

Evidence

  • NIST organizes AI risk management around Govern, Map, Measure, and Manage. Its framework treats governance as a cross-cutting function and asks organizations to establish accountability, document intended use, measure identified risks, and prioritize responses. That structure supports a living register linked to decisions, not a one-time compliance checklist.
  • NIST's Generative AI Profile adds risks specific to generative systems, including confabulation, information integrity, privacy, and information security. A practical register should therefore distinguish the base model, application, data flows, users, safeguards, evaluation evidence, incident signals, and accepted residual risk.
  • Editorial analysis: implementation controls should be mapped to the system, users, data, and consequences in scope; the cited sources do not establish that any particular deployment has passed those controls.
  • Editorial analysis: reviewers may find it useful to preserve dated implementation evidence and distinguish policy, configuration, and exception records.

Competing viewpoints

Editorial analysis: a standardization-first approach may improve consistency and supplier comparability, but should not be treated as proof that an implementation is effective.

Editorial analysis: a context-first approach can better reflect local risk, but may reduce consistency and require more governance. Neither position is established by the cited sources as universally preferable.

Implications

  • Assign a named owner and review trigger to every material risk.
  • Link each mitigation to test evidence, deployment context, and an escalation path.
  • Reassess entries when models, prompts, data sources, or user populations change.
  • Budget for evidence collection, exception handling, and periodic retesting; these are continuing operating costs, not one-time implementation tasks.
  • Use procurement and architecture review to expose dependencies early, because a technically valid control can still fail when ownership or supplier obligations are ambiguous.

Actionable takeaways

  • Write a one-page scope statement naming the covered systems, data, users, environments, and explicit exclusions. Give the scope an owner and review date.
  • Convert each cited principle into a testable requirement with an evidence source, pass condition, collection cadence, and escalation route.
  • Run one representative end-to-end test, including an adverse or exception case, and retain the configuration, inputs, outputs, and decision record.
  • Add relevant requirements to supplier evaluation and contracts. Ask for product-specific evidence and change notification rather than provider-wide assurances.
  • Review the control after material releases, architecture changes, incidents, and supplier changes; close expired exceptions or renew them with fresh evidence.

Limitations and risks

The NIST framework is voluntary and outcome-oriented; it does not prescribe a universal scoring method or determine which legal obligations apply in a jurisdiction. The primary sources define mechanisms, practices, or reference models; they do not measure this organization's implementation or guarantee an outcome. This is not a product comparison, legal opinion, penetration test, or audit conclusion. Applicability changes with architecture, versions, contracts, jurisdiction, threats, and data sensitivity. Validate assumptions against current source editions and product documentation, test representative failures, and obtain specialist advice for regulated or high-consequence decisions.

Sources and citations

  1. Artificial Intelligence Risk Management Framework (AI RMF 1.0) — NIST, accessed 2026-09-06
  2. Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile — NIST, accessed 2026-09-06