ISO 42001 certification is an accredited auditor’s finding that an organization runs an AI management system (AIMS) meeting ISO/IEC 42001, judged through a two-stage audit and kept alive by yearly surveillance. It certifies how you govern AI, not any single model. That distinction is where most of the confusion starts, and it matters whether you are the one being audited or the one reading somebody else’s certificate.
Picture the second case first, because it is the one most security teams meet. A supplier’s security questionnaire comes back with a new badge in the trust section, “ISO 42001 certified”, and the procurement lead asks whether that settles the AI questions. It might. It might also cover two products you never bought, come from a certifier nobody accredited, or say nothing about the regulation your legal team is worried about. We will come back to that badge, because by the end of this post you should be able to test it before the contract is signed.
What ISO 42001 certification covers
ISO/IEC 42001 was published in December 2023 as the first international standard for managing AI, and it applies to any organization that provides, develops or uses AI products or services. It is built on the same Annex SL backbone as ISO 27001 and ISO 9001, so clauses 4 to 10 will look familiar to anyone who has run an ISMS.
What is new sits on top of that backbone. Modulos’s clause guide lists the AI-specific additions as an AI policy (5.2), an AI risk assessment (6.1.2), AI risk treatment (6.1.3) and an AI system impact assessment (6.1.4). The last one is the piece ISO 27001 teams tend to underestimate. Risk assessment looks at risks to the organization, while impact assessment looks at consequences for individuals, groups and society, and the standard wants both, as separate records that feed each other.
The scope statement under clause 4.3 decides everything downstream. It names which AI systems, lifecycle stages and functions are inside the AIMS, anchored in your role as a provider, producer or user of AI. The Stage 2 sampling plan flows from that scope statement, which is why a vague scope produces a vague audit.
ISO 42001 certification requirements: Annex A and the Statement of Applicability
Annex A is where people expect a checklist and find a menu. It groups reference controls into nine areas, A.2 to A.10, covering AI policies, internal organization, 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 per control and Annex C offers an idea bank of objectives and risk sources.
The important difference from ISO 27001 is that ISO 42001 treats Annex A as informative rather than a mandatory checklist. You select controls from your risk and impact assessments and record the decision, with justification and owner, in a Statement of Applicability. Every accredited audit still expects that record. The failure we would warn you about is the one Modulos names directly, which is copying Annex A wording into a spreadsheet and calling it implementation. The SoA should be the output of your risk work, and an auditor who reads it next to the risk register will see quickly if it was written first.
The ISO 42001 audit, stage by stage
The audit itself follows the familiar ISO pattern, and Schellman’s account of the process gives the clearest timings we have found.
Stage 1 is a design review. Auditors read the scope, required policies, your risk management and impact assessment methods, and the Statement of Applicability, and it typically takes one to two days. Schellman puts the gap before Stage 2 at four to twelve weeks, and says it should not exceed six months or Stage 1 may need to be repeated.
Stage 2 tests whether the system actually runs. It focuses on operation (clause 8), risk and impact management and the in-scope Annex A controls, along with monitoring, internal audit, management review and corrective action, and it lasts anywhere from three to nine or more days. Pass it and the certificate is valid for three years, with surveillance audits every year at roughly a third of the initial audit time.
The real constraint on how fast you can get certified is not audit days. It is the evidence window, because the AIMS has to run long enough for auditors to see genuine internal audit records, management review minutes and corrective actions. In our experience that is where rushed programs stall. You can write an impact assessment method in a week, but you cannot backdate a management review.
ISO 42001 vs ISO 27001: what carries over
If you already hold ISO 27001, the good news is real. Schellman notes that risk management frameworks, internal audit and continual improvement can be reused from the ISMS, and the shared clause structure means one management review can serve both systems.
What does not carry over is the thinking. The same source points out that the AI impact assessment, ethical considerations and transparency obligations are new, and that the risk assessment has to widen beyond information security. The Standards Council of Canada’s pilot found the same pressure points from the auditor’s side. It underscored the need for AI inventories, data lineage, management of third-party and model-as-a-service risk, and disciplined change management. An organization that cannot list its AI systems and the models behind them is not ready for Stage 1, however mature its ISMS is. That inventory problem is the same one we wrote about in our CISO case for AI agent governance, and it is the first gap we look for when we run AI governance and assurance work for a client.
How to verify an ISO 42001 certificate
Back to the badge in the questionnaire. Five questions turn it from a logo into evidence.
- Who issued it, and who accredited them? ISO itself does not certify anyone or accredit certification bodies. National accreditation bodies do that, such as ANAB in the US, UKAS in the UK and the Standards Council of Canada. The issuer should name its accreditor.
- Does IAF CertSearch show it? IAF CertSearch includes only accredited certificates. If the certificate is missing, ask the certification body or the accreditation body directly before you draw a conclusion. A listed one will show one of four statuses (Active, Suspended, Withdrawn or Expired).
- Which products are in scope? This is the question that catches most buyers. AWS’s 2024 certificate covered Amazon Bedrock, Amazon Q Business, Amazon Textract and Amazon Transcribe, and Microsoft’s 2025 certificate covers Azure AI Foundry Models and Microsoft Security Copilot. Neither is a blanket statement about the company. Read the scope line and compare it with what you actually buy.
- Is the certificate current? It runs for three years with yearly surveillance, so ask for the most recent surveillance date along with the certificate.
- Does it cover you? It does not, and AWS says so plainly: your organization is not automatically certified by association. A certified model provider helps your own audit. It does not replace it.
Accreditation is not a formality either. MHM Advisory, the first body SCC accredited for ISO 42001, warned about low-cost, non-accredited offers, because without accreditation nobody independently checks the certifier’s competence or impartiality. The rules for certifiers have also only just settled. ISO/IEC 42006, which sets the extra requirements for bodies auditing AI management systems, was published in 2025, and SCC accredited its first body while that standard was still a draft before moving it to the final text. A certificate from that early period is not suspect for that reason alone, but it is worth asking which version of the rules the issuer was assessed against.
Does ISO 42001 make you EU AI Act compliant?
No, and this is the claim we see stretched most often. The Cloud Security Alliance put it bluntly in April 2026, saying that ISO/IEC 42001 alone does not satisfy the EU AI Act and that it sits outside the EU’s harmonisation process. The structural reason is simple enough to repeat in a meeting. ISO 42001 certifies an organization’s management system, while the Act regulates each high-risk AI system as a product.
The CSA note lists what the standard leaves open against Article 17, including a per-system regulatory compliance strategy, pre-determined change management for systems that keep learning, and the Article 73 serious-incident reporting timelines. The European route to a presumption of conformity is a harmonised standard instead. EN 18286, the quality management standard for AI Act purposes, was approved by CEN and CENELEC on 12 July 2026, and it carries that presumption only once it is cited in the Official Journal.
There is time to build on top of an AIMS rather than beside it. Under the Digital Omnibus deal agreed in May 2026, rules for high-risk systems in areas such as employment, education and critical infrastructure will apply from 2 December 2027, and those embedded in products from 2 August 2028. Our advice is to treat ISO 42001 as the organizational layer and map the per-system Article 17 duties onto it, which is what the CSA note recommends too.
Frequently asked questions
Is ISO 42001 certification worth it?
It is worth it when customers or regulators ask for an independent signal about how you govern AI, and when you already run an ISO management system you can extend. BSI reports that 26% of organizations are taking steps to align with ISO/IEC 42001, so the question is coming up in procurement. It is not worth it as a substitute for knowing what AI you run, because the audit will find that gap first.
How long is an ISO 42001 certificate valid?
Three years. Surveillance audits run every year in between and take roughly a third of the time of the initial audit. Recertification then starts the cycle again. When you check a supplier, ask for the latest surveillance date as well as the issue date, because a certificate can be suspended or withdrawn mid-cycle.
Is Microsoft ISO 42001 certified?
Specific Microsoft services are. The July 2025 certificate covers Azure AI Foundry Models, including Azure OpenAI models, and Microsoft Security Copilot, issued by Mastermind under International Accreditation Service accreditation, with the certificate and report on the Service Trust Portal. Check the current scope there for the services you actually use.
What does an ISO 42001 certification cost?
We have not found a public figure we would stand behind, and quotes depend on scope, headcount and the number of AI systems sampled. The cost drivers are visible in the process, though. Stage 2 alone can run three to nine or more audit days, and the internal effort of building those records comes on top of the audit fee.
Is ISO 42001 mandatory?
It is a voluntary standard that no regulation we know of makes compulsory. It is not part of the EU harmonisation process, and even under the AI Act it does not create a presumption of conformity. Contracts are where it becomes mandatory in practice, when a customer writes it into supplier requirements.
Bottom line: what to do before the next audit
Before you accept the next ISO 42001 badge, look it up in IAF CertSearch, read the scope line against the products you buy, and ask for the latest surveillance date. If you are pursuing certification yourself, start with the AI inventory and a scope statement you can defend, then let the AIMS run long enough to produce real records before you book Stage 2.