NIST AI Risk Management Framework for Enterprise AI
TL;DR — The NIST AI RMF 1.0 is a voluntary framework with four core functions: GOVERN (policies and accountability), MAP (identify and contextualize AI risks), MEASURE (assess and monitor risks), and MANAGE (prioritize and respond). 72 subcategories across these functions provide a comprehensive AI risk management structure. The Generative AI Profile (July 2024) extends it with LLM-specific risks. Implementation takes 3-6 months (small) to 12-24 months (enterprise). Organizations with existing ISO 27001 or NIST CSF programs can implement faster by overlaying AI RMF on existing governance. MAP and MEASURE align with EU AI Act Article 9 requirements. The framework is voluntary but increasingly required in US federal procurement and enterprise vendor qualification. Implement it as a continuous process, not a one-time checklist.
What the NIST AI RMF Is
The NIST AI Risk Management Framework (AI RMF 1.0), released January 2023, is a voluntary framework for managing risks associated with AI systems. It complements the AI risk assessment process by providing a structured, repeatable approach. It was developed through a consensus-driven process with private and public sectors, directed by the National Artificial Intelligence Initiative Act of 2020.
Key properties:
- Voluntary — not a regulation, but increasingly required in procurement
- Sector-agnostic — applies to all industries
- Use-case agnostic — works for any AI application
- Lifecycle-spanning — covers design, development, deployment, operation, and decommissioning
- Rights-preserving — considers impacts on individuals, groups, and society
- Living document — NIST reviews regularly, with formal input expected by 2028
The Four Core Functions
The AI RMF Core consists of four functions that operate as a continuous cycle:
The following diagram shows how the four functions relate as a continuous cycle, with GOVERN overarching all stages:
Policies & Accountability"] --> MAP GOVERN --> MEASURE GOVERN --> MANAGE MAP["MAP
Identify & Contextualize"] --> MEASURE["MEASURE
Assess & Monitor"] MEASURE --> MANAGE["MANAGE
Prioritize & Respond"] MANAGE --> MAP
GOVERN: Policies, Processes, and Accountability
GOVERN establishes the organizational framework for AI risk management. It applies to all stages and all AI systems.
| Category | Description |
|---|---|
| GOVERN 1 | Policies, processes, procedures, and practices across the organization |
| GOVERN 2 | Accountability structures for AI risk management |
| GOVERN 3 | Workforce diversity, equity, inclusion, and access |
| GOVERN 4 | Organizational culture of risk management |
| GOVERN 5 | External stakeholders and partnerships |
| GOVERN 6 | Lifecycle inventory and transparency |
Key actions:
- Appoint an AI risk management lead or committee
- Define organizational AI risk tolerance
- Create an AI governance policy referencing NIST AI RMF
- Establish a cross-functional AI governance committee (legal, security, data science, business)
- Document meeting cadence and RACI ownership for each function
class AIGovernanceCommittee:
def __init__(self):
self.members = {
"legal": "General Counsel",
"security": "CISO",
"data_science": "Head of ML",
"business": "VP Product",
"compliance": "Compliance Officer"
}
self.meeting_cadence = "monthly"
self.raci = {
"GOVERN": "Compliance Officer (A), CISO (R), All members (C)",
"MAP": "Head of ML (A), Data Science Team (R), Committee (C)",
"MEASURE": "Head of ML (A), ML Ops Team (R), Security (C)",
"MANAGE": "CISO (A), Security Team (R), Committee (C)"
}
def approve_ai_system(self, system: AISystem) -> bool:
"""Gate: AI system must be approved before production deployment."""
risk_assessment = self.assess_risk(system)
if risk_assessment.residual_risk > self.risk_tolerance:
return False
return True
MAP: Identify and Contextualize AI Risks
MAP identifies where AI risks emerge across the lifecycle and documents the context for each AI system.
| Category | Description |
|---|---|
| MAP 1 | Context is established and understood |
| MAP 2 | Categorization of the AI system is completed |
| MAP 3 | AI system capabilities and intended use are understood |
| MAP 4 | Risks and benefits are mapped for all components |
| MAP 5 | Impacts to individuals, groups, communities, and society are characterized |
Key actions:
- Create a comprehensive inventory of all AI systems
- For each system, document: intended purpose, deployment context, data inputs, decision outputs, affected stakeholders, known limitations
- Categorize each system by risk level
- Map potential impacts on individuals and society
ai_system_inventory:
- system_id: "AI-001"
name: "Customer Support LLM"
purpose: "Automated customer query response"
deployment_context: "Customer-facing chatbot"
data_inputs: ["customer queries", "knowledge base documents"]
decision_outputs: ["response text", "escalation decision"]
affected_stakeholders: ["customers", "support agents"]
known_limitations: ["may hallucinate", "limited to knowledge base scope"]
risk_level: "medium"
lifecycle_stage: "deployment"
map_function_complete: true
MEASURE: Assess, Quantify, and Monitor
MEASURE evaluates AI systems against trustworthiness characteristics and monitors them over time.
| Category | Description |
|---|---|
| MEASURE 1 | Appropriate methods for measuring AI risks are identified and applied |
| MEASURE 2 | Appropriate methods for measuring AI trustworthiness are identified and applied |
| MEASURE 3 | Mechanisms for tracking measured risks over time are identified and applied |
| MEASURE 4 | Feedback about AI system performance is gathered and assessed |
Seven trustworthiness characteristics:
| Characteristic | Description | Measurement Example |
|---|---|---|
| Validity & Reliability | System produces accurate, consistent results | Accuracy, precision, recall, F1 |
| Safety | System does not cause harm | Failure rate, incident count |
| Security | System resists adversarial attacks | Robustness testing, penetration test results |
| Accountability | Clear ownership of system outcomes | Audit trail completeness |
| Transparency & Explainability | System decisions are understandable | Explanation coverage, user comprehension |
| Privacy | System protects personal data | PII exposure rate, data minimization score |
| Fairness | System does not discriminate | Demographic parity, equalized odds |
class AITrustworthinessMeasurer:
def measure_system(self, system: AISystem) -> TrustMetrics:
return TrustMetrics(
validity=self.measure_validity(system),
safety=self.measure_safety(system),
security=self.measure_security(system),
accountability=self.measure_accountability(system),
transparency=self.measure_transparency(system),
privacy=self.measure_privacy(system),
fairness=self.measure_fairness(system)
)
def measure_fairness(self, system: AISystem) -> FairnessMetric:
# Test for demographic parity in outputs
results = system.test_demographic_parity()
return FairnessMetric(
demographic_parity=results.parity_score,
disparate_impact=results.impact_ratio,
equalized_odds=results.odds_difference
)
MANAGE: Prioritize and Respond
MANAGE allocates risk resources to mapped and measured risks on a regular basis.
| Category | Description |
|---|---|
| MANAGE 1 | AI risks are prioritized and responded to |
| MANAGE 2 | Resources are allocated to manage risks |
| MANAGE 3 | Third-party AI risks are managed |
| MANAGE 4 | AI systems are monitored for ongoing performance |
Risk treatment options:
| Treatment | When to Use | Example |
|---|---|---|
| Mitigate | Risk can be reduced with controls | Add output filtering for harmful content |
| Transfer | Risk is shifted to another party | Purchase AI liability insurance |
| Accept | Risk is within tolerance | Low-impact hallucination in non-critical context |
| Avoid | Risk is too high to proceed | Cancel deployment of biased model |
class RiskResponsePlaybook:
def respond_to_risk(self, risk: AIRisk):
if risk.severity == "critical":
self.escalate_to_committee(risk)
self.initiate_incident_response(risk)
elif risk.severity == "high":
self.mitigate(risk)
self.monitor(risk, frequency="daily")
elif risk.severity == "medium":
self.mitigate(risk)
self.monitor(risk, frequency="weekly")
elif risk.severity == "low":
if risk.within_tolerance:
self.accept(risk)
else:
self.mitigate(risk)
Generative AI Profile (NIST-AI-600-1)
Released July 2024, the Generative AI Profile extends the AI RMF with genAI-specific risks:
| GenAI Risk Category | AI RMF Function | Description |
|---|---|---|
| Hallucination | MEASURE | Model produces false but plausible outputs |
| Data poisoning | MAP/MEASURE | Training data manipulated to cause specific behaviors |
| Prompt injection | MANAGE | Adversarial inputs manipulate model behavior |
| Model inversion | MEASURE | Attackers reconstruct training data from model outputs |
| Memorization | MEASURE | Model reproduces training data verbatim |
| Deepfakes | MANAGE | Synthetic content used for deception |
| Content provenance | GOVERN | Lack of transparency about AI-generated content |
| Value chain risks | MAP | Risks from foundation model providers, data suppliers |
| Intellectual property | GOVERN | Copyright issues in training data and outputs |
| Environmental impact | MEASURE | Energy consumption of training and inference |
| Information integrity | MEASURE | Misinformation and disinformation risks |
| Information security | MANAGE | GenAI used for cyberattacks (phishing, code generation) |
If your AI platform uses LLMs, implement both the base RMF and the Generative AI Profile.
EU AI Act Alignment
The NIST AI RMF MAP and MEASURE functions align with EU AI Act requirements:
| EU AI Act Requirement | NIST AI RMF Function | Coverage |
|---|---|---|
| Article 9: Risk management system | MAP + MEASURE | High |
| Article 10: Data governance | MAP (data inputs) | Medium |
| Article 12: Record keeping | GOVERN 6 | Medium |
| Article 13: Transparency | GOVERN + MAP 3 | Medium |
| Article 14: Human oversight | MANAGE 1 | High |
| Article 15: Accuracy and robustness | MEASURE 1-2 | High |
Practical benefit: Organizations implementing NIST AI RMF can reuse MAP and MEASURE evidence for EU AI Act conformity assessments, reducing duplicative compliance effort.
Implementation Timeline
| Phase | Duration | Activities |
|---|---|---|
| Phase 1: Govern | 1-3 months | Establish committee, draft AI policy, define risk tolerance |
| Phase 2: Map | 1-3 months | Inventory AI systems, document context, categorize risks |
| Phase 3: Measure | 2-6 months | Define metrics, deploy monitoring, establish baselines |
| Phase 4: Manage | Ongoing | Risk treatment, incident response, continuous monitoring |
For organizations with existing GRC programs (ISO 27001, NIST CSF):
- Map existing controls to GOVERN and MANAGE first
- Add AI-specific evidence for MAP and MEASURE
- Treat AI RMF as an overlay, not a standalone program
- Estimated timeline: 3-6 months (small), 12-24 months (enterprise)
For organizations without existing GRC programs:
- Start with GOVERN to establish accountability structures
- Build governance infrastructure before MAP, MEASURE, MANAGE
- Estimated timeline: 6-12 months (small), 18-36 months (enterprise)
Audit-Ready Evidence
Each function requires specific evidence artifacts:
ai_rmf_evidence:
govern:
- ai_governance_policy.pdf
- committee_charter.pdf
- meeting_minutes/
- raci_matrix.pdf
- risk_tolerance_statement.pdf
map:
- ai_system_inventory.yaml
- system_context_documents/
- stakeholder_impact_assessments/
- risk_categorization_matrix.pdf
measure:
- trustworthiness_metrics_dashboard.json
- bias_test_results/
- security_test_results/
- performance_baselines/
- monitoring_config.yaml
manage:
- risk_treatment_plans/
- incident_response_playbook.pdf
- third_party_assessment_records/
- monitoring_alerts_log.json
- corrective_action_log.json
Key principle: Organizations that enforce AI governance policy at the system level produce continuous evidence rather than assembling it manually before each audit cycle.
Common Implementation Mistakes
Treating AI RMF as a One-Time Checklist
The framework is designed for continuous improvement. Organizations that complete the four functions once and consider themselves "compliant" miss the point.
Fix: Implement as a continuous cycle. Review and update regularly. Monitor AI systems continuously, not periodically.
Starting with MAP Instead of GOVERN
Jumping straight to AI system inventory without establishing governance structures first. Without accountability, the inventory becomes a static document that nobody owns.
Fix: Start with GOVERN. Appoint a committee. Define risk tolerance. Then proceed to MAP.
No Generative AI Profile
Implementing the base RMF but ignoring the Generative AI Profile. LLM-specific risks (hallucination, prompt injection, memorization) are not covered by the base framework.
Fix: If you use LLMs, implement both the base RMF and NIST-AI-600-1.
No Evidence of Operation
Having policies and risk assessments on paper but no evidence they're followed. Auditors check for operational evidence — monitoring logs, incident reports, committee meeting minutes.
Fix: Generate continuous evidence through system-level enforcement. Don't assemble evidence manually before audits.
Ignoring Third-Party AI Risks
Not assessing AI systems from vendors. MANAGE 3 specifically requires managing third-party AI risks.
Fix: Assess every third-party AI system before deployment. Include AI-specific clauses in vendor contracts. Monitor after deployment. Use a structured AI vendor risk assessment process to evaluate providers before integration.
Implementation Checklist
- [ ] Appoint an AI risk management lead or committee (GOVERN)
- [ ] Draft and approve an AI governance policy (GOVERN 1)
- [ ] Define organizational AI risk tolerance (GOVERN 1)
- [ ] Establish a cross-functional AI governance committee (GOVERN 2)
- [ ] Document RACI ownership for each function (GOVERN 2)
- [ ] Create a comprehensive AI system inventory (MAP 1)
- [ ] Document intended purpose, context, and stakeholders for each system (MAP 3)
- [ ] Categorize each system by risk level (MAP 2)
- [ ] Map potential impacts on individuals and society (MAP 5)
- [ ] Define metrics for each trustworthiness characteristic (MEASURE 1)
- [ ] Deploy continuous monitoring for AI systems (MEASURE 3)
- [ ] Establish performance baselines (MEASURE 2)
- [ ] Implement bias and fairness testing (MEASURE 2)
- [ ] Implement security and robustness testing (MEASURE 2)
- [ ] Create risk response playbooks for common scenarios (MANAGE 1)
- [ ] Define escalation paths for risks exceeding tolerance (MANAGE 1)
- [ ] Establish AI incident response procedures (MANAGE 1)
- [ ] Document risk treatment plans (mitigate, transfer, accept, avoid) (MANAGE 2)
- [ ] Assess third-party AI systems before deployment (MANAGE 3)
- [ ] Monitor third-party AI systems after deployment (MANAGE 4)
- [ ] Implement the Generative AI Profile if using LLMs (NIST-AI-600-1)
- [ ] Map evidence to EU AI Act articles for dual compliance
- [ ] Generate continuous evidence through system-level enforcement
- [ ] Review and update risk management process at least annually
- [ ] Conduct internal audits of AI RMF implementation
- [ ] Train staff on AI risk management practices
Conclusion
The NIST AI RMF provides a structured, flexible approach to AI risk management that adapts to any organization, any sector, and any AI technology. Its four functions — GOVERN, MAP, MEASURE, MANAGE — create a continuous cycle of risk identification, assessment, monitoring, and response.
For enterprise AI platforms, the framework is not optional in practice even though it's voluntary in law. US federal procurement increasingly references it. Enterprise vendor qualification processes request it. And it provides a practical bridge to EU AI Act compliance through MAP and MEASURE alignment with Article 9.
Start with GOVERN. Establish accountability before inventory. Implement the Generative AI Profile if you use LLMs. Generate continuous evidence through system-level enforcement rather than assembling it manually before audits. Treat the framework as a continuous improvement process, not a one-time checklist.
Organizations that implement the NIST AI RMF alongside ISO 27001 and ISO 42001 create a comprehensive governance stack: information security (27001), AI management (42001), and AI risk management (NIST AI RMF). This stack satisfies enterprise procurement requirements across US and EU markets.
FAQ
What is the NIST AI Risk Management Framework?
The NIST AI RMF 1.0 is a voluntary framework released in January 2023 for managing risks associated with AI systems. It consists of four core functions — GOVERN, MAP, MEASURE, and MANAGE — with 72 subcategories. It is sector-agnostic, use-case agnostic, and designed for organizations of all sizes. It is not a regulation but provides a structured approach to identifying, assessing, and managing AI risks throughout the AI lifecycle.
Is the NIST AI RMF mandatory?
No. The NIST AI RMF is voluntary. However, it is increasingly referenced in US federal procurement requirements, enterprise vendor qualification, and as a foundational framework for AI governance. The EU AI Act's risk management requirements (Article 9) align with the MAP and MEASURE functions, making NIST AI RMF implementation a practical bridge to EU AI Act compliance.
What are the four functions of the NIST AI RMF?
GOVERN establishes policies, processes, and procedures for AI risk management across the organization. MAP identifies and contextualizes AI risks by documenting intended purpose, deployment context, stakeholders, and known limitations. MEASURE assesses, quantifies, and monitors AI risks against trustworthiness characteristics (validity, reliability, safety, security, accountability, transparency, explainability, privacy, fairness). MANAGE prioritizes and responds to identified risks through mitigation, transfer, acceptance, or avoidance.
What is the NIST Generative AI Profile?
Released in July 2024 (NIST-AI-600-1), the Generative AI Profile extends the AI RMF with genAI-specific risks: hallucination, data poisoning, prompt injection, model inversion, memorization, deepfakes, and content provenance. It adds 12 genAI-specific risk categories mapped to the four core functions. If your AI platform uses LLMs, implement both the base RMF and the Generative AI Profile.
How long does NIST AI RMF implementation take?
Foundational adoption takes 3-6 months for smaller initiatives and 12-24 months at enterprise scale. Organizations with existing GRC programs (ISO 27001, NIST CSF) can implement faster by treating AI RMF as an overlay — mapping current controls to GOVERN and MANAGE first, then adding AI-specific evidence for MAP and MEASURE. The framework is designed for continuous improvement, not one-time compliance.
Want a self-hosted AI company brain that does all of this out of the box?
Book a demo →