Originally published at https://charz.ai/blog/nist-ai-600-1-vs-nist-ai-rmf by Char-Z AI.
One Framework, One Profile
The NIST AI Risk Management Framework (AI RMF 1.0) is a voluntary framework for managing AI risk across any AI system, organized around four functions: Govern, Map, Measure, and Manage. The Generative AI Profile — published as NIST AI 600-1 — is not a separate framework. It is a companion document that applies the AI RMF specifically to generative AI, and it exists because generative AI produces distinctive risks that a general method does not surface on its own (NIST, 2023; NIST, 2024).
Think of the AI RMF as the method and the profile as a lens over it. You do not run two programmes; you run one programme with the generative AI lens attached to the systems that need it.
What Generative AI Adds
- Confabulation — fluency is not accuracy; a plausible output is not a correct one.
- Harmful or toxic content — output quality is not a control the general method tests for.
- Disclosure of private training data — the risk lives in the data, not the deployment.
- Information integrity — synthetic media changes what “evidence” means downstream.
- Prompt injection and adversarial input — the input surface is natural language, and it is untrusted.
- Provenance and sourcing — models, datasets, and weights have their own supply chain.
These are not hypothetical. They are the reason a team can pass a conventional AI risk review and still ship a chatbot that invents a policy, leaks a customer name, or repeats an attacker's instructions.
The 12 Action Categories
The profile organizes its guidance into 12 action categories across the AI RMF's four functions (NIST, 2024):
- Govern — define and communicate use cases and context; document context sufficiently to reason about output confidence; conduct red-teaming and tabletop exercises; apply zero-trust architecture; invest in robust statistical analysis of outputs.
- Map — assess and disclose risks and potential harms; establish a risk-management process; source and share AI assets responsibly and transparently.
- Measure — verify assessments, evaluations, benchmarks, and claims; implement effective mitigation for content identified as private, sensitive, or harmful.
- Manage — identify and implement mitigations for cybersecurity vulnerabilities; establish AI technology incident response and recovery plans.
Each action maps back to AI RMF subcategories, so the profile does not create a parallel structure. It extends the one you already have.
AI RMF vs AI 600-1 at a Glance
- Published — AI RMF 1.0: 2023. Generative AI Profile (AI 600–1): 2024.
- Scope — AI RMF 1.0: all AI systems. Generative AI Profile: generative AI systems.
- Structure — AI RMF 1.0: four functions with subcategories. Generative AI Profile: 12 action categories mapped to those functions.
- Nature — AI RMF 1.0: voluntary framework. Generative AI Profile: companion profile — also voluntary.
- Use — AI RMF 1.0: the method. Generative AI Profile: a lens applied over the method.
- Produces — AI RMF 1.0: risk-management practice. Generative AI Profile: generative-AI-specific controls and mitigations.
How to Apply Both
Scope first. Not every action applies at full depth to every generative AI system. Start with the systems that carry the most risk — broad user access, autonomy, sensitive data, or public output.
Map the actions onto controls you already have. A significant share of the twelve overlap with security and privacy work you already perform — access control, monitoring, incident response, data minimization. Use the profile to find the gaps rather than to start from zero.
Attach the actions to specific systems. Each generative AI system should have named controls for the actions that apply to it, with an owner and a review point. A profile applied generically produces a document; a profile applied per system produces a register.
Treat detection as a control, not an outcome. For any output that reaches a user, decide what is filtered, refused, labelled, or reviewed. Content that is identified as private, sensitive, or harmful needs a mitigation that actually runs.
Extend the incident plan. Prompt injection, data leakage, and harmful output are incident types. If your incident response plan was written for conventional software failures, add them.
The profile also pairs naturally with the transparency expectations that apply to AI systems in the EU, where disclosure of AI interaction and marking of synthetic output are separate, binding duties (European Commission, 2024). The profile supplies the methodology for managing the risk those duties address; it does not discharge the duties themselves.
Frequently Asked Questions
Is NIST AI 600-1 mandatory?
No. It is a voluntary companion profile to the AI RMF. It becomes practically relevant when you deploy generative AI in customer-facing, safety-adjacent, or regulated contexts.
Do I need the profile if I already use the AI RMF?
If you operate generative AI, yes — the base framework does not surface confabulation, harmful content, or prompt injection as first-class risks. The profile is how the method reaches those systems.
How many action categories does the profile define?
Twelve, distributed across the AI RMF's four functions: Govern, Map, Measure, and Manage. Each maps to the AI RMF subcategories it extends.
Does applying the profile make a generative AI system safe?
No framework or profile certifies a system as safe or lawful. The profile reduces identified risks through specific controls and gives you a defensible method for deciding which controls to apply.
Sources
NIST. (2024). *Generative Artificial Intelligence Profile (NIST AI 600-1)*. National Institute of Standards and Technology. https://doi.org/10.6028/NIST.AI.600-1
NIST. (2023). *Artificial Intelligence Risk Management Framework (AI RMF 1.0)*. National Institute of Standards and Technology. https://doi.org/10.6028/NIST.AI.100-1
European Commission. (2024). Regulation (EU) 2024/1689 of the European Parliament and of the Council. *Official Journal of the European Union*. https://eur-lex.europa.eu/eli/reg/2024/1689
Top comments (0)