NIST AI RMF vs ISO 42001: which one should a small company document against?
Written by PolicyDrafters. Published , updated .
Document against whichever framework your customers name. US customers usually ask for NIST AI RMF alignment, which is voluntary and not certifiable; certification-driven procurement asks for ISO/IEC 42001:2023, which is audited against clauses 4 to 10 and Annex A. If nobody has asked, start with the documents both share: an AI policy, a system inventory and a risk procedure.
What is the NIST AI RMF?
The NIST AI Risk Management Framework 1.0 is a voluntary framework, published by the US National Institute of Standards and Technology on 26 January 2023, that organises the management of AI risk into four functions: Govern, Map, Measure and Manage [1]. Govern is the cross-cutting function: policies, roles, accountability and culture. Map sets the context for a system, who it affects and what could go wrong. Measure tests and tracks the risks that Map identified. Manage decides what to do about them and records the decision.
Each function is divided into categories and subcategories that read as outcomes rather than instructions, and the framework does not say which of them a given organisation must meet. A companion Playbook suggests actions, references and documentation for each subcategory, and NIST publishes profiles for particular uses, including NIST AI 600-1, the generative AI profile issued on 26 July 2024 [2].
Two things follow from the framework being voluntary. Nobody certifies against it; an organisation says it is aligned, and a customer either takes its word or asks to see the evidence. And it carries no fixed clause structure, so two organisations that both claim alignment can hold very different document sets. That flexibility is what US buyers like about it, and it is also what makes it hard to point at a single list of required documents.
What is ISO/IEC 42001?
ISO/IEC 42001:2023 is an international standard, published in December 2023, that specifies the requirements for an AI management system: the policies, roles, processes and records through which an organisation establishes, operates, monitors and improves its development or use of AI [3]. It uses the same harmonised structure as ISO/IEC 27001 and ISO 9001, so clauses 4 to 10 cover context, leadership, planning, support, operation, performance evaluation and improvement, in that order.
Annex A lists the reference controls, grouped under nine objectives (A.2 to A.10) that run from AI policies and internal organisation through resources, impact assessment, the system life cycle, data, information for interested parties, use of AI systems and third-party relationships. Annex B gives implementation guidance for each control, and clause 6.1.3 asks the organisation to produce a statement of applicability saying which controls it has adopted and why the others do not apply.
The standard is written to be audited. Every "shall" in clauses 4 to 10 is a requirement an accredited certification body can test, and each one expects documented information behind it. That is the trade: a fixed structure that takes more work to set up, in exchange for a certificate at the end.
Who asks for which framework?
In practice the question is settled by whoever is sending you the questionnaire. US enterprise customers and US public bodies tend to reference NIST, partly because the framework comes from a US federal agency, and partly because NIST frameworks are familiar from the security questionnaire that arrived first. The usual form of the request is "describe how your AI risk management aligns to the NIST AI RMF", and it is answered with a mapping document rather than a certificate.
Procurement that is driven by certification asks for ISO/IEC 42001 in the same breath as ISO/IEC 27001, because the buyer's vendor process is built around certificates and a management system standard fits the slot. European buyers, larger buyers with formal supplier assurance programmes and any buyer that already holds 42001 itself are the ones most likely to ask. Regulators, so far, name neither as mandatory.
The EU AI Act lets conformity with its requirements be shown through harmonised standards, and under Article 40(1) a standard gives that presumption only once its reference is published in the Official Journal [4]. The first European standard written for the Act, EN 18286:2026 on the quality management system that Article 17 asks of providers of high-risk systems, was published by CEN and CENELEC in July 2026 [5]. The Act is therefore a reason to watch both texts rather than a reason to hold a 42001 certificate today.
Which one can you be certified against?
NIST AI RMF alignment is a claim you make and support. ISO/IEC 42001 certification is a claim a third party makes about you after a two-stage audit: a review of the documented management system, then a test of whether the system runs as documented, followed by surveillance audits in the following years and a recertification audit at the end of the cycle.
The standard therefore carries a visible cost that the framework does not, and a visible result that the framework cannot give. A small company that documents against 42001 without seeking certification still gains the structure; it forgoes the certificate, and should say so plainly rather than imply otherwise.
What documents does each one imply?
Neither text hands you a list of documents by name, but each implies one. For NIST, the Govern function expects an AI policy that assigns accountability, a record of roles, and a process for reviewing risks; Map expects an inventory of AI systems with the context and intended use of each; Measure expects a testing and monitoring record; Manage expects a procedure for responding to risks and incidents and for deciding whether a system continues. A mapping table that places each of your documents under the relevant subcategory is the artefact customers actually ask to see.
For ISO/IEC 42001, the documents are closer to prescribed. Clause 5.2 asks for an AI policy, clauses 6.1.2 and 6.1.3 for a risk assessment and risk treatment process with its results and a statement of applicability against the Annex A controls, clauses 6.1.4 and 8.4 for an AI system impact assessment, clause 6.2 for objectives, clause 7.5 for controlled documented information, clause 9 for monitoring, internal audit and management review records, and clause 10 for nonconformity and corrective action records. An organisation seeking certification should also expect to show an internal audit programme and at least one completed management review before the certification body arrives.
The overlap is large. An AI policy, a system inventory, a risk assessment procedure, a human oversight procedure, an incident procedure and a technical documentation template serve both, which is why our AI governance suite is drafted against the two together with the EU AI Act and carries a mapping table showing which clause, function and article each document answers. The documents that serve only one are the ISO-specific ones: the statement of applicability, the internal audit programme and the management review record.
What does it take to keep each one current?
The framework changes slowly and informally. NIST updates the Playbook and adds profiles without reissuing the core, though its resource page states that AI RMF 1.0 is being revised as part of the White House AI Action Plan [2]. A document set aligned to it therefore needs a review when a relevant profile or the revised framework appears, and otherwise an annual check.
The standard changes rarely and formally, and its running cost sits elsewhere: in the certification cycle, the internal audits, the management reviews and the records those produce. A small company documenting against 42001 should expect the management system to need an owner with time set aside each quarter, where the NIST-aligned set needs an owner with time set aside each year. Under the maintenance plan, $29 to $99 a month, we track whichever you were drafted against and reissue the documents with the changes marked when the text moves.
How do they map to each other and to the EU AI Act?
NIST lists crosswalks submitted by the AI RMF user community in its AI Resource Center, and the one for ISO/IEC 42001 was contributed by Microsoft rather than prepared by NIST [6]. Read side by side, the mapping runs the way you would expect: Govern to clauses 5 and 7 and to Annex A.2 and A.3; Map to clause 4, clause 8.4 and Annex A.5 and A.6; Measure to clause 9 and Annex A.6 and A.7; Manage to clauses 6.1, 8 and 10.
The EU AI Act, for its part, asks providers of high-risk systems for a risk management system under Article 9, data governance under Article 10, technical documentation under Article 11 and Annex IV, record-keeping under Article 12, human oversight under Article 14 and a quality management system under Article 17, and gives deployers their own obligations in Article 26 [4].
Article 17's quality management system reads much like clauses 4 to 10 of 42001, so a company documented against the standard has most of Article 17 in hand. A document set built on the shared core answers most of all three, and the mapping table shows where the gaps are.
| Aspect | NIST AI RMF 1.0 | ISO/IEC 42001:2023 |
|---|---|---|
| What it is | A voluntary risk management framework from a US agency | An international management system standard |
| Published | January 2023, with a Playbook and later profiles | December 2023 |
| Structure | Four functions: Govern, Map, Measure, Manage, with categories and subcategories | Clauses 4 to 10 plus Annex A controls under nine objectives |
| Who asks for it | US enterprise customers and public bodies | Certification-driven procurement, European buyers, buyers that hold it themselves |
| Certifiable | No; alignment is self-declared and evidenced | Yes; accredited certification bodies audit against it |
| Documents implied | AI policy, system inventory, risk and incident procedures, mapping table | The same, plus statement of applicability, impact assessment, internal audit and management review records |
| Cost to keep current | Annual review; updates when a profile, the Playbook or the 1.0 core is revised | Quarterly management system work; surveillance and recertification audits |
| Relation to the EU AI Act | Crosswalked; no presumption of conformity | Closest to Article 17, for which EN 18286:2026 is the standard written |
- What it is
- NIST AI RMF 1.0A voluntary risk management framework from a US agency
- ISO/IEC 42001:2023An international management system standard
- Published
- NIST AI RMF 1.0January 2023, with a Playbook and later profiles
- ISO/IEC 42001:2023December 2023
- Structure
- NIST AI RMF 1.0Four functions: Govern, Map, Measure, Manage, with categories and subcategories
- ISO/IEC 42001:2023Clauses 4 to 10 plus Annex A controls under nine objectives
- Who asks for it
- NIST AI RMF 1.0US enterprise customers and public bodies
- ISO/IEC 42001:2023Certification-driven procurement, European buyers, buyers that hold it themselves
- Certifiable
- NIST AI RMF 1.0No; alignment is self-declared and evidenced
- ISO/IEC 42001:2023Yes; accredited certification bodies audit against it
- Documents implied
- NIST AI RMF 1.0AI policy, system inventory, risk and incident procedures, mapping table
- ISO/IEC 42001:2023The same, plus statement of applicability, impact assessment, internal audit and management review records
- Cost to keep current
- NIST AI RMF 1.0Annual review; updates when a profile, the Playbook or the 1.0 core is revised
- ISO/IEC 42001:2023Quarterly management system work; surveillance and recertification audits
- Relation to the EU AI Act
- NIST AI RMF 1.0Crosswalked; no presumption of conformity
- ISO/IEC 42001:2023Closest to Article 17, for which EN 18286:2026 is the standard written
So which one should you document against?
A small company should document against whichever of the NIST AI RMF and ISO/IEC 42001 its customers name. If they ask for the NIST AI RMF, write the AI policy, the system inventory, the risk procedure and the incident procedure, and put a mapping table at the front that places each one under Govern, Map, Measure and Manage.
If they ask for ISO/IEC 42001, use the structure of clauses 4 to 10, add the statement of applicability against Annex A, and decide early whether certification is the goal, because that decision sets the budget for internal audit and management review. If nobody has asked, start with the documents both share, name both frameworks in the mapping table, and let the first questionnaire decide which column you expand. Neither choice locks you in, because the shared core carries over when a later customer names the other one.
The one route to avoid is holding two document sets. A company that keeps a NIST-aligned policy for US customers and a separate 42001 policy for European ones has two revision histories, two owners and, within a year, two different rules. One policy with a mapping table serves both readers.
Where should a small company start?
For a SaaS or technology company with a few AI features and its first AI questionnaire, the sequence that works is the inventory first, because every other document refers to it; then the policy, because it assigns the owner; then the risk assessment and human oversight procedures, because those are what the questionnaire actually probes; then the incident procedure. The ISO-specific records come last and only if certification is in view. The security side of the same questionnaire is answered by the information security policy set, and the two sets are drafted to share one document ID convention and one revision block.
We draft the AI set as the AI governance suite, quoted at $3,000 to $5,000, reviewed by our legal team before delivery, with the mapping table included so one set of documents can be read against a NIST question, an ISO audit or an Article 26 questionnaire. The classification of each system, provider or deployer, high-risk or not, is yours to make; the suite records the answer and the reasons for it.
Questions
- Can a company be certified against the NIST AI RMF?
- No company can be certified against the NIST AI RMF, which is voluntary and has no certification scheme. A company states that it is aligned and shows the mapping and the documents behind the statement. ISO/IEC 42001:2023 is the one with an accredited certification audit.
- Do we need both the NIST AI RMF and ISO 42001 if we sell to the US and the EU?
- Usually one document set with a mapping table serves both the NIST AI RMF and ISO/IEC 42001. The policy, system inventory, risk assessment procedure, human oversight procedure and incident procedure are common to both frameworks. Only the ISO-specific records, such as the statement of applicability and the internal audit programme, are added when certification is the goal.
- Does the NIST AI RMF or ISO 42001 satisfy the EU AI Act?
- Neither the NIST AI RMF nor ISO/IEC 42001 satisfies the EU AI Act on its own. The Act sets its own obligations for providers and deployers of high-risk systems, and under Article 40 a presumption of conformity comes only from harmonised standards whose references are published in the Official Journal. The first European standard written for the Act, EN 18286:2026 on the Article 17 quality management system, was published by CEN and CENELEC in July 2026. Documents drafted against the shared core of the two frameworks answer most of what Articles 9 to 17 and 26 ask for, with the gaps marked.
- How long does the AI governance suite take?
- The AI governance suite takes twenty working days from a complete intake to the first draft. It is drafted against the EU AI Act, the NIST AI RMF 1.0 and ISO/IEC 42001:2023 together, reviewed by our legal team, and carries a mapping table showing which clause, function and article each document answers.
Sources
- NIST AI 100-1, AI RMF 1.0doi.org
- NIST AI RMF resource pagenist.gov
- ISO/IEC 42001:2023iso.org
- Regulation (EU) 2024/1689 (EU AI Act)eur-lex.europa.eu
- CEN and CENELEC, EN 18286:2026cencenelec.eu
- NIST AI Resource Center, AI RMF crosswalksairc.nist.gov
The documents this guide is about
Applies to
AI governance suite
An AI governance documentation suite is the set of policies, procedures and record templates that sets out how an organisation approves, risk-assesses, oversees and monitors the AI systems it builds or uses, and keeps the evidence of each step in the form the EU AI Act, the NIST AI RMF and ISO/IEC 42001 describe.
$3,000 to $5,000
20 working days
Information security policy set
An information security policy set is the group of written policies and procedures that states how a company protects its systems and data: who may access what, how staff may use company devices, how incidents and outages are handled, which vendors may hold the data, and who owns each control.
$1,200 to $2,500
12 working days