← Back to Technical Guides
Duczer East Guides: NIST AI RMF explained, with the Generative AI Profile
AI & Data Engineering

NIST AI RMF explained, with the Generative AI Profile

A practical guide to the NIST AI Risk Management Framework for regulated firms.
Guide AI & Data Engineering 10 min read October 29, 2026 Duczer East Insights
Part of the Insights topic: Agentic AI Governance & Model Risk →

The NIST AI Risk Management Framework (AI RMF) is a voluntary framework from the US National Institute of Standards and Technology for managing the risks of AI systems across their life cycle. It organizes the work into four functions: Govern, Map, Measure and Manage. Its Generative AI Profile, NIST AI 600-1, applies those functions to large language models and other generative systems. This guide explains both and shows how a bank, insurer or health system turns them into evidence a reviewer can test. It is part of our Agentic AI Governance & Model Risk series.

What the NIST AI Risk Management Framework is

NIST published the framework in January 2023. It is voluntary, it applies to any sector, and it does not tell you which controls to buy. It describes outcomes an organization should reach and leaves the method to you. NIST has said the framework is being revised, so check the NIST site for the current text before you cite section numbers in a policy.

The framework has two parts. Part 1 explains how to frame AI risk and what makes an AI system trustworthy. Part 2 is the Core: the four functions, broken into categories and subcategories. NIST also publishes a companion Playbook with suggested actions and references for each outcome. NIST says organizations can borrow as many or as few of those suggestions as apply.

There is no NIST AI RMF certification. NIST does not certify organizations against it, and no auditor can issue one. What the framework gives a regulated firm is a common structure. Model risk, security, privacy and compliance teams can map their existing controls to the same outcomes and find the gaps between them.

It does not replace sector rules. A bank still answers to its supervisors and to SR 26-2. A health system still answers to HIPAA. The framework sits underneath as the way to organize the AI evidence those reviews ask for.

The seven characteristics of trustworthy AI

Part 1 defines what the framework is trying to protect. NIST lists seven characteristics of a trustworthy AI system:

NIST treats valid and reliable as the base: a system that does not work as intended cannot be trustworthy in any other way. Accountable and transparent spans the other six, because each of them depends on someone being able to see and answer for what the system did.

In practice, each characteristic becomes a test question. Is the model accurate on our data? Can it be made to leak customer records? Can we explain a decline to the customer? Who answers for it when it is wrong? A governance program that cannot answer those questions with evidence has not applied the framework, whatever its policy says.

The four functions: Govern, Map, Measure and Manage

The Core is where the work happens. Govern runs across the other three. Map, Measure and Manage repeat for each AI system through its life.

FunctionWhat it asksCategoriesEvidence it produces in a regulated firm
GovernWho owns AI risk, and what are the rules?6AI policy, risk tolerance, roles and accountability, training records, third-party AI terms
MapWhat is this system, who does it affect, and what could go wrong?5AI inventory entry, intended use, affected parties, data sources, known limitations
MeasureHow risky is it, and how do we know?4Test plans and results, metrics, bias and robustness testing, monitoring reports
ManageWhat do we do about the risks we found?4Risk acceptance or treatment decisions, runtime controls, incident response, decommissioning records

Each category breaks into numbered subcategories, such as GOVERN 1.1 or MEASURE 2.7. Those numbers are useful as keys. If every control, test and policy in your program carries the subcategory it supports, an auditor can trace any outcome to its evidence in one step.

The functions are not a one-time sequence. A model that passes Measure at launch goes back through Map when its data, its users or its vendor changes. Most findings come from systems that were measured once and never mapped again.

Profiles: how you apply the framework to your firm

The framework is generic on purpose. Profiles make it specific. NIST describes three kinds.

A use-case profile applies the functions to one setting, such as credit underwriting or claims triage, with that setting's risk tolerance and resources.

A temporal profile compares two states. The current profile describes how you manage AI risk today. The target profile describes the outcomes you need. The gap between them is your plan, ranked by what matters most to you.

A cross-sectoral profile covers risks shared across many settings, such as large language models or cloud services. The Generative AI Profile is the main example.

For most regulated firms, the useful starting point is a current and target profile for each risk tier in the AI inventory. High-risk systems, such as anything that affects credit, coverage, claims or clinical decisions, get the full target profile. Low-risk internal tools get a lighter one.

The Generative AI Profile (NIST AI 600-1)

NIST published the Generative AI Profile in July 2024 as a cross-sectoral profile for generative AI. It names 12 risks that generative AI creates or makes worse, then lists suggested actions for each, organized by the same functions and subcategories as the Core. Each action has an ID that ties it back to the framework. GV-1.1-001 is the first suggested action under GOVERN 1.1.

Risk (NIST name)What it looks like in a bank, insurer or health system
CBRN Information or CapabilitiesMainly a model-provider concern. Most enterprise deployments record it and rely on the provider's controls.
ConfabulationAn assistant states a wrong fee, policy limit or dosage with full confidence.
Dangerous, Violent, or Hateful ContentA customer-facing chat produces abusive or threatening text.
Data PrivacyCustomer data or patient records surface in a response, a log or a fine-tuned model.
Environmental ImpactsCompute and energy use of training and inference. Usually reported, rarely the top risk.
Harmful Bias or HomogenizationUnderwriting or credit summaries that treat groups differently, or many teams relying on one model's judgment.
Human-AI ConfigurationStaff approve an agent's recommendation without real review, or trust it beyond what it was tested for.
Information IntegrityFalse or misleading generated content reaches customers, regulators or the public.
Information SecurityPrompt injection in an email or document makes an assistant leak data or call a tool it should not.
Intellectual PropertyGenerated text or code reproduces licensed material.
Obscene, Degrading, and/or Abusive ContentMostly a concern for open, customer-facing tools and image generation.
Value Chain and Component IntegrationA third-party model, plugin or tool server changes behavior without notice.

The profile also sets out four primary considerations that cut across the risks: governance, content provenance, pre-deployment testing and incident disclosure. For a regulated firm, pre-deployment testing and incident disclosure are where most of the new work sits. Testing a generative system means testing for confabulation, leakage and injection, not only accuracy. Incident disclosure means knowing, before launch, what counts as an AI incident and who has to be told.

Not every risk applies to every deployment. Record each one in the system's profile as applicable or not, with a reason. A reviewer will accept "not applicable, internal summarization tool with no customer output" far more readily than silence.

Applying the framework to AI agents

The framework was written before AI agents were common, but its functions fit them well. An agent is a generative system that also acts: it calls APIs, queries databases and uses tools, often through the Model Context Protocol (MCP). That raises the weight of three risks from the profile: Information Security, Human-AI Configuration, and Value Chain and Component Integration.

Map changes the most. An agent's inventory entry has to list what it can do, not just what it is: every tool, API and data source it can reach, and the authority it acts under. If that list does not exist, Measure has nothing to test against.

Measure has to include behavior, not only output. Tests should cover whether the agent can be steered by injected instructions, whether it stays within its tools, and whether it stops when a check fails.

Manage is where agents need controls that run, not documents. Four controls carry most of the weight:

Above the gateway, an agent control plane manages the agents themselves: inventory, identity, lifecycle, evaluation and suspension. Several platforms offer one. On Choreo Labs (formerly WSO2), it is Choreo Agent Manager.

How it fits with SR 26-2, ISO/IEC 42001 and the EU AI Act

The AI RMF rarely stands alone. Regulated firms map it to the requirements they are actually examined on.

For banks, SR 26-2 is the interagency model risk guidance that replaced SR 11-7. It sets the supervisory expectations for model inventory, development, validation and governance. The AI RMF does not change those expectations. It gives a structure for the AI-specific evidence, especially for generative and agentic systems, that a model risk program now has to produce. Our page on AI governance for banks and SR 26-2 covers that mapping.

ISO/IEC 42001 is a management system standard for AI. Unlike the AI RMF, an organization can be certified against it, and that certification comes from an accredited certification body. Firms that want certification often use the AI RMF to design their risk work and ISO/IEC 42001 to run it as a managed, auditable system. NIST's resource center lists crosswalks between the AI RMF and other standards, including one for ISO/IEC 42001 submitted by a third party.

The EU AI Act matters for firms with EU customers, staff or operations. It is law, not a voluntary framework, and its obligations depend on how a system is classified. The AI RMF helps produce the risk evidence the Act asks for, but mapping to the Act is a separate exercise.

Adopting the framework: six steps

  1. Name an owner and set risk tolerance. One accountable executive, a written AI policy, and risk tiers that say which systems need the most scrutiny. This is Govern.
  2. Build the AI inventory. Every model, generative tool and agent in use, including vendor features switched on inside existing software. Record owner, purpose, data, users, tier and, for agents, the tools they can reach. This is Map.
  3. Write the current profile. For each high-risk system, record which subcategories you meet today and the evidence for each.
  4. Set the target profile. Decide which outcomes each tier must reach, including the Generative AI Profile actions that apply. The gap becomes the plan.
  5. Test before launch and on change. Accuracy, bias, robustness, leakage and injection testing, scaled to the tier, with results stored where an auditor can find them. This is Measure.
  6. Put controls in the runtime and plan for incidents. Identity, enforcement, logs and a stop control for agents. A defined AI incident process with named people. This is Manage.

What auditors and examiners check

Reviewers rarely ask whether you "follow NIST." They ask for evidence that the outcomes are met. Expect requests like these:

If you can produce each of these without asking the developers, the program is ready for review.

When to bring in a partner

The framework is easy to read and hard to evidence. Most firms already have pieces of it spread across model risk, security and privacy teams. The work is joining them into one inventory, one set of profiles and controls that run in production. Duczer East provides AI governance consulting for banks, insurers and health systems, from the inventory and gap analysis to the runtime controls that close it.

Related: SR 11-7 and SR 26-2 explained · prompt injection controls

Frequently asked questions

Is the NIST AI RMF mandatory?

No. The NIST AI Risk Management Framework is voluntary. It becomes binding only when a contract, a customer or a regulator's guidance points to it, so many regulated firms adopt it to organize evidence they owe for other reasons.

Can an organization be certified in NIST AI RMF?

No. NIST does not certify organizations against the AI RMF, and there is no official certification. Firms that need a certificate usually look at ISO/IEC 42001, which is certified by accredited bodies.

What are the four functions of the NIST AI RMF?

The four functions are Govern, Map, Measure and Manage. Govern sets policy and accountability and runs across the others. Map establishes each system's context and risks, Measure tests and monitors them, and Manage decides and applies the response.

What is NIST AI 600-1?

NIST AI 600-1 is the Generative AI Profile of the AI RMF, published in July 2024. It names 12 risks that generative AI creates or makes worse, such as confabulation and information security, and lists suggested actions for each, organized by the framework's functions.

What is the difference between NIST AI RMF and ISO 42001?

The NIST AI RMF is a voluntary risk framework, while ISO/IEC 42001 is a management system standard you can be certified against. Many firms use the AI RMF to design their AI risk work and ISO/IEC 42001 to run it as an auditable system.

Does the NIST AI RMF apply to AI agents?

Yes. Its functions apply to any AI system, and the Generative AI Profile covers the risks agents raise most, such as prompt injection and third-party components. Agents also need runtime controls, such as their own identity, enforced access and decision logs, to meet the Manage outcomes.

Would you like to discuss AI governance for your organization?

Duczer East provides AI governance consulting for banks, insurers and health systems, from the inventory and gap analysis to the runtime controls that close it.

Prefer email? info@duceast.com
Duczer East — Where Data Engineering Meets Agentic AI

The Practitioner's Briefing

Senior-level insights on agentic AI, data engineering, and enterprise integration — delivered to your inbox.