NIST AI Risk Management Framework 1.0
A voluntary US framework structured around four functions - GOVERN, MAP, MEASURE, MANAGE - that any organisation can use to identify and reduce risks of AI systems. Categories and sub-categories give concrete outcomes.
Read NIST AI RMF as a step-by-step path
GOVERN - culture & policy
GOVERN sets the conditions: policy, legal alignment, documentation and trustworthy-AI characteristics integrated into how the organisation works.
- 1Map your legal and regulatory landscape into policy.
- 2Integrate the trustworthy-AI characteristics (valid, safe, secure, accountable, explainable, privacy-enhanced, fair).
- 3Document risk-management processes and outcomes.
ISO Clauses 4–5 + Annex A.2 give the certifiable version.
EU Art.16/17 turn the same intent into binding duties.
GOVERN - accountability
Accountability lines: who decides, who escalates, who signs.
- 1Document roles, responsibilities and lines of communication.
- 2Make senior leadership formally accountable for AI risk outcomes.
- 3Define decision rights for go/no-go and override.
Cl.5.1, 5.3, 9.3 + Annex A.3.
Art.26 - deployers must name responsible humans and oversee use.
GOVERN - workforce
People, skills, and the awareness that AI risk is everyone's job.
- 1Drive AI risk awareness across the organisation.
- 2Train people on the AI tasks they actually perform.
Cl.7.2 + 7.3.
Art.4 - AI literacy is now a legal duty for providers and deployers of any AI system.
GOVERN - culture of risk
GOVERN - engagement
GOVERN - third-party
Most teams integrate AI rather than build it. GOVERN 6 ensures vendor and supply-chain risk is treated as AI risk.
- 1Inventory third-party AI, models and data.
- 2Set due-diligence and contract requirements for AI suppliers.
Annex A.10.
Art.25 (value-chain responsibility) + Art.53/55 (GPAI providers).
MAP - context
MAP is where you frame the system: purpose, users, deployers, context - so risk analysis is grounded.
- 1Establish context - purpose, users, deployment environment.
- 2Identify categories and capabilities of the AI system.
Cl.4.1–4.2.
Classification under Annex III + Art.6 depends on this context.
MAP - categorization
Data is in MAP because you have to know what you're training on before you can quantify risk in MEASURE.
- 1Catalogue training and operational data, sources, limits.
Annex A.7.
Art.10 - strict data-governance duties for high-risk AI.
MAP - capabilities
MAP - third-party
Confirm the people, partners and tooling needed exist before you commit.
- 1List people, third parties, tools and infrastructure required.
Cl.7.1 + Annex A.4.
Art.17 quality-management resources.
MAP - impacts
Identify potential benefits, costs, and impacts on people and the environment.
- 1Map likelihood and magnitude of harms.
- 2Map impacts to affected individuals and groups.
Cl.6.1.2 + 6.1.4 + Annex A.5.
Art.9 + Art.27 (FRIA).
MEASURE - selection
Pick metrics appropriate to the risks you mapped. You cannot manage what you do not measure.
- 1Select metrics, methods, and acceptance thresholds.
Cl.6.2 + 9.1.
Art.15 - declared accuracy/robustness levels.
MEASURE - evaluation
Quantitative and qualitative evaluation: validity, reliability, safety, security, explainability, privacy, fairness.
- 1Test accuracy, robustness, reliability and security.
- 2Test explainability and interpretability.
- 3Test privacy and fairness.
Annex A.6.2.4 + Cl.9.1.
Art.15 + Annex IV documentation of tests.
MEASURE - tracking
Continuous monitoring of identified and emergent risks in production.
- 1Track risks and feedback signals in operation.
Cl.9.1 + Annex A.6.2.8.
Art.72 - post-market monitoring.
MANAGE - prioritization
Decide what to do about the risks: accept, mitigate, transfer, avoid.
- 1Prioritise risks against context.
- 2Plan and execute treatment.
- 3Confirm human oversight points.
Cl.6.1.3 + 8.3 + Annex A.9.
Art.9 risk management + Art.14 oversight.
MANAGE - strategies
Manage risks of third-party AI and execute residual-risk treatments.
- 1Treat residual risks and third-party AI risks operationally.
Cl.8.3 + Annex A.10.
Art.25 value-chain duties.
MANAGE - monitoring
Post-deployment: monitor, detect, respond and improve.
- 1Monitor in production.
- 2Run incident response.
- 3Report and learn.
Cl.10.2 + Annex A.6.2.8.
Art.72 + Art.73 (serious-incident reporting).