← All news and guides
AI governance

Do You Need ISO 42001 to Sell to Enterprise Customers?

Many enterprise buyers do not require ISO 42001 yet. See when certification pays off, who certifies, how it compares with NIST AI RMF, and what to show instead.

Mono Team ·

A long boardroom table with a closed folder and a single pen at one end, empty leather chairs around it, pale daylight from tall windows.

Short answer: often not yet. Many enterprise buyers ask for AI governance evidence rather than ISO/IEC 42001 certification, and we have found no law that makes a SaaS vendor hold it. What they ask for is proof that you govern your AI: a policy, an inventory, a risk process, vendor controls and evidence. You can show that without a certificate. Certification starts to matter when a buyer or tender names it, when several large customers ask for it in the same quarter, or when you sell AI as the core of your product and want an independent audit to point to. Until then, build the controls first. A certificate is only worth having if the system behind it is real.

This guide is for founders, CTOs and security leads at B2B and SaaS companies who have seen "ISO 42001" in a questionnaire or a sales call and need to decide what to do. It covers what the standard is, who certifies it, when to get certified, how it compares with NIST AI RMF and SOC 2, and what to do if you do not certify. It is engineering guidance, not legal advice. Mono does not certify anyone. We help you get ready.

What is ISO 42001?

ISO/IEC 42001:2023, Information technology - Artificial intelligence - Management system, is an international standard for an AI management system. It was published on 18 December 2023 by ISO/IEC JTC 1/SC 42 as Edition 1. It is written for organisations that develop, provide or use AI-based products or services.

It is a management-system standard. It does not test your model or tell you how accurate it must be. It asks whether your organisation runs AI in a controlled, documented and repeatable way. The main clauses (4 to 10) cover:

  • Context and scope (clause 4): your interested parties and which AI systems are in scope.
  • Leadership (clause 5): an AI policy and named roles and authorities.
  • Planning (clause 6): AI risk assessment, risk treatment and an AI system impact assessment.
  • Support and operation (clauses 7 and 8): resources, competence, documented information, and operating the controls you chose.
  • Performance evaluation and improvement (clauses 9 and 10): monitoring, internal audit, management review and corrective action.

Annex A lists reference control objectives and controls, grouped under topics such as policies, internal organisation, resources, impact assessment, the AI system life cycle, data, information for interested parties, use of AI systems, and third-party and customer relationships. Annex B gives implementation guidance. Annexes C and D are informative. You do not have to apply every Annex A control. You decide which are necessary through your risk treatment and record the decision, with reasons, in a Statement of Applicability.

Does any law or regulator require ISO 42001?

We have found no law, rule or regulator that requires a SaaS vendor to hold ISO/IEC 42001 certification. It is a voluntary standard. In India, the DPDP Act and Rules do not mention it, and the RBI's FREE-AI report is a committee report, not a direction. As of November 2026, RBI has not issued final model risk management guidance, and the June 2026 draft is the latest text.

That can change for a sector or a tender. A buyer can write ISO 42001 into its vendor policy or an RFP at any time. So the useful question is not "is it required by law?" but "is it required by the buyers I want to win?" The next section helps you answer that.

When do enterprise buyers actually ask for ISO 42001?

It shows up in a few predictable ways. Check which one you are in before you spend money.

Where you see itWhat it usually meansWhat to do
A security questionnaire asks "Are you ISO 42001 certified?" as a yes or noWhat it usually means: A checkbox. The buyer wants to know whether you have an AI governance programme. Some forms accept an alternativeWhat to do: Answer honestly. Say what you have instead, and attach evidence. See the questionnaire guides linked below
A named line in an RFP or vendor policy: "certification required"What it usually means: A real requirement. A gap can block the dealWhat to do: Ask the buyer if a roadmap with dates, or a readiness assessment, is acceptable while you certify
A SIG or CSA AI-CAIQ that maps to ISO 42001What it usually means: The framework is a reference, not a requirement to be certifiedWhat to do: Answer the questions on their own terms. Mapping helps you reuse answers
Your own sales team says "competitors have it"What it usually means: A hunch, not a requirementWhat to do: Ask the last five lost or stalled deals what the buyer actually asked for
A regulated buyer (bank, insurer, healthcare) running a third-party AI risk reviewWhat it usually means: Often asks for governance evidence. Whether it asks for the certificate varies by buyerWhat to do: Ask the buyer's security team what evidence they accept

If you want the detail on how buyers write these questions, see how to answer the AI section of a security questionnaire, and what the SIG AI domain and the CSA AI-CAIQ ask. Both the SIG and the CSA AI Controls Matrix map to ISO/IEC 42001, and both are ways for a buyer to ask about AI governance without requiring certification.

Who can certify me against ISO 42001?

Two empty chairs facing each other across a plain meeting-room table, a closed folder and a pen between them, soft overcast light from a tall window.

ISO does not certify companies. Independent certification bodies do. ISO/IEC 42006:2025, published on 7 July 2025, sets the requirements for bodies that audit and certify an AI management system, building on ISO/IEC 17021-1. In India, NABCB (part of QCI) accredits certification bodies for AI management systems under its criteria document NABCB 220 (April 2026), which requires ISO/IEC 17021-1 and ISO/IEC 42006:2025.

Only certification bodies accredited for ISO/IEC 42001, for example by NABCB, ANAB or UKAS, issue accredited certificates. Consultants provide readiness. Mono is not a certification body. We help you build and evidence the controls so an audit goes smoothly. We do not issue, promise or guarantee a certificate. Before you buy, ask any certification body for the scope of its accreditation, and check that scope on the accreditation body's own register.

What does certification involve?

The detail depends on the certification body, so confirm it with them. In outline, certification means you have a working AI management system that covers the clauses above, and an independent audit finds it conforms. These are the parts that take real effort:

  • Scope. Which AI systems, teams, locations and products are in the AI management system. A narrow, honest scope beats a wide, vague one.
  • AI policy and roles. A written policy, signed off by leadership, and named owners.
  • AI inventory and risk assessment. Every AI system you build, buy or use, with its risks, rated and treated.
  • AI system impact assessment. For each in-scope system, who could be affected and how, and what you do about it.
  • Statement of Applicability. The controls you apply from Annex A, the ones you exclude and why.
  • Operating evidence. Records that the controls ran: approvals, reviews, logs, training, incident handling.
  • Internal audit and management review. You audit yourself, and leadership reviews the results, before the external auditor arrives.

One point to plan for: auditors look for records that the system has been operating, not only that policies exist. If you write the policies the week before the audit, you will struggle to show operation. This is a good reason to start the controls early, even if you decide to certify later. Our ISO 42001 readiness service covers this groundwork.

When should you get ISO 42001 certified?

Use these tests. Two or more "yes" answers is a good sign it is time to plan certification.

  • A named buyer or tender requires it and the deal is large enough to justify the effort.
  • Several buyers ask for it in the same sales period, not just one.
  • AI is the core of what you sell. An independent audit supports your claims about how you build and run it.
  • You already run ISO/IEC 27001 or a similar management system. 42001 uses the same kind of structure, so you reuse an audit rhythm, document control and internal audit. You still need AI-specific risk and impact work.
  • Your controls already run. You have an inventory, a policy, vendor reviews and records, and the gap is the independent audit.
  • You can keep it up. The system has to keep running after the certificate. You need an owner and time for internal audits and reviews.

Equally, these are signs it is too early:

  • You cannot yet list the AI features you ship or the AI tools your staff use.
  • No one owns AI governance.
  • The only reason is "a competitor announced it".
  • The real blocker in your deals is a thin questionnaire answer or missing contract terms, and a certificate would not fix that.

If you are not sure which AI tools your team uses, start with a shadow AI audit before anything else.

What can you show instead of a certificate?

An open binder of blank tabbed dividers on a wooden desk beside a closed laptop and a cup of tea, warm low evening light, nothing legible.

Many enterprise reviews can be satisfied by a small, honest evidence pack. A buyer's security team reads your answer, then checks the attachment. This is what we would put in it, using wording you can stand behind:

EvidenceWhat it provesNotes
AI use policy with a named ownerWhat it proves: Someone is accountableNotes: Approved models and providers, what data may be sent to them, review before launch, staff use of AI tools. Review it on a set cycle
AI inventoryWhat it proves: You know what you runNotes: System, owner, model and provider, data used, customers affected, date reviewed
Risk and impact notes for each customer-facing AI featureWhat it proves: You assessed it before launchNotes: Short is fine. Dated and signed off is what matters
Vendor and model provider termsWhat it proves: Your data is not used to train provider models without consent, and retention is knownNotes: Attach the contract clause or settings, not the marketing page
Customer data controlsWhat it proves: One customer cannot see another's data through the AINotes: Describe isolation in retrieval, prompts, caches and logs
Incident and change processWhat it proves: You can handle an AI failureNotes: How you detect, escalate, roll back and tell customers
A readiness statementWhat it proves: You are working toward a standardNotes: "Our controls follow ISO/IEC 42001 and we are not certified" is honest. "Compliant with ISO 42001" is not, unless a certification body has said so

The wording matters. Following a standard is not the same as being certified, and buyers do read the difference. Say which one applies. Build the pack once so the same answers work across forms.

ISO 42001 vs NIST AI RMF: which one do you need?

They do different jobs, and you do not have to pick only one.

ISO/IEC 42001NIST AI RMF 1.0
What it isISO/IEC 42001: A management-system standard with requirements (clauses 4 to 10) and reference controls (Annex A)NIST AI RMF 1.0: A voluntary risk framework with four functions: Govern, Map, Measure, Manage
PublishedISO/IEC 42001: 18 December 2023 (ISO/IEC)NIST AI RMF 1.0: 26 January 2023 (NIST). A Generative AI Profile, NIST AI 600-1, followed on 26 July 2024
CertificationISO/IEC 42001: Yes, by accredited certification bodiesNIST AI RMF 1.0: No. NIST has no certification. You can say you align with it, not that you are certified
Best forISO/IEC 42001: Showing a buyer an independently audited AI management systemNIST AI RMF 1.0: Structuring how you think about and measure AI risk, and answering buyers who reference it
StatusISO/IEC 42001: Edition 1. As of 20 November 2026, no newer edition is shown on the ISO pageNIST AI RMF 1.0: NIST says the framework is being revised under the White House AI Action Plan

In practice, many teams use NIST AI RMF as a way of thinking about risk and ISO 42001 as the management system that holds it in place. NIST's Govern, Map, Measure and Manage functions fit well inside the ISO risk and impact steps. If a buyer asks whether you "follow NIST AI RMF", you can answer yes only if you can point to what you did. If they ask whether you are "NIST certified", the honest answer is that no such certification exists.

If you have to choose where to start, start with the one your buyers name. If none do, start with the inventory, policy and risk steps that both share. They carry over to either.

ISO 42001 vs SOC 2: do I need both?

They answer different questions. A SOC 2 report is an attestation examination by a licensed CPA firm under AICPA standards. It reports on controls relevant to Security, Availability, Processing Integrity, Confidentiality or Privacy, using the Trust Services Criteria. It is a CPA's opinion, not a certificate. ISO/IEC 42001 is a certifiable management system for AI specifically.

If your buyers already ask for SOC 2, that is a separate ask and ISO 42001 does not replace it. Many SaaS buyers ask for SOC 2 on its own terms, and AI governance is an extra block on top of it. AICPA has also published exposure drafts of updated Trust Services Criteria that add AI considerations. They are drafts, so plan around the current criteria. For the full side-by-side, including what each proves and the evidence you can reuse for both, read ISO 42001 vs SOC 2.

What should you do this quarter?

  • Find out what buyers actually asked. Read your last ten questionnaires and RFPs. Count how many named ISO 42001 as required, and how many accepted other evidence.
  • Build the inventory and the policy. These help in every case, certified or not.
  • Write honest answers. Use "we are not ISO/IEC 42001 certified" where true, and attach your evidence pack.
  • Do a gap check against the standard. Compare what you have to clauses 4 to 10 and the Annex A controls, and note what you would apply or exclude.
  • Decide with a trigger. Pick the condition (for example, a named tender or a number of buyer requests) that makes you start certification. Write it down, and revisit it each quarter.
  • Choose a certification body only when you are ready. Check its accreditation scope for ISO/IEC 42001 first.

Our work stays on the engineering and evidence side. Legal reading of a contract or a regulator's text goes to your counsel.

Sources: ISO/IEC 42001:2023, ISO page and table of contents (iso.org/standard/42001; DIN table of contents). ISO/IEC 42006:2025 (iso.org/standard/42006). NABCB 220, Accreditation Criteria for AIMS Certification Bodies, April 2026 (nabcb.qci.org.in). NIST AI Risk Management Framework 1.0 and the NIST AI RMF page (nist.gov/itl/ai-risk-management-framework). NIST AI 600-1, July 2024. AICPA, SOC suite of services and the proposed update of the SOC 2 Trust Services Criteria (aicpa-cima.com). Shared Assessments SIG (sharedassessments.org/sig-excel). Cloud Security Alliance, AI Controls Matrix v1.1, 22 June 2026 (cloudsecurityalliance.org/artifacts/ai-controls-matrix-v1-1). RBI Press Release 2026-2027/528, 24 June 2026, and Press Release 2025-2026/902, 13 August 2025. Last reviewed 20 November 2026.

FAQ

Do I need ISO 42001 to sell to enterprise customers?

Often not. We have found no law that requires a SaaS vendor to hold ISO/IEC 42001 certification, and many enterprise buyers ask for AI governance evidence such as a policy, an AI inventory, risk records and vendor terms. Certification matters when a buyer or tender names it, or when several buyers ask for it. If a deal does require it, ask whether a dated roadmap is acceptable.

Is ISO 42001 mandatory?

No. ISO/IEC 42001:2023 is a voluntary international standard for AI management systems. We have found no Indian or international law that makes certification mandatory for a software vendor. A buyer can still write it into its own vendor policy or tender, which makes it a commercial requirement for that deal.

Who can certify a company against ISO 42001?

Only independent certification bodies accredited for ISO/IEC 42001, for example by NABCB in India, ANAB or UKAS. ISO itself does not certify. ISO/IEC 42006:2025 sets requirements for these bodies. Consultants, including Mono, can help you prepare but cannot issue an accredited certificate.

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

NIST AI RMF 1.0 is a voluntary risk framework built around the functions Govern, Map, Measure and Manage, and it has no certification. ISO/IEC 42001 is a management-system standard with auditable requirements and reference controls, and accredited bodies can certify against it. Many teams use the NIST framework to structure risk work inside an ISO-style management system.

What can I show a buyer if I am not ISO 42001 certified?

Show a small evidence pack: an AI use policy with a named owner, an AI inventory, dated risk and impact notes for customer-facing AI features, model provider contract terms, controls that keep customer data separate, and an incident process. Say plainly that you are not certified, and describe which standard your controls follow.

Does ISO 42001 replace SOC 2?

No. A SOC 2 report is a CPA firm's attestation about controls against the Trust Services Criteria. ISO/IEC 42001 certifies an AI management system. They answer different buyer questions, so many SaaS vendors have SOC 2 first and consider ISO 42001 later, when buyers or AI-heavy products make it worth the effort.

Not sure if ISO 42001 is worth it for your deals? Let's look at what your buyers ask for.