Summary
- ISO/IEC 42001:2023 sets the requirements for an AI management system (AIMS): the policies, roles, risk processes, records and reviews an organisation needs to manage AI responsibly.
- It follows the same "harmonised structure" as ISO 27001 and ISO 9001: Clauses 4 to 10 are mandatory, and Annex A is a menu of 38 AI controls in 9 groups (A.2 to A.10) that you include or exclude through a Statement of Applicability (SoA).
- It is voluntary and certifiable. An accredited certification body audits you and issues a three-year certificate.
- It is a governance standard, not a technical security standard. It has no prompt-injection, jailbreak, model-abuse or runtime security controls. Pair it with NIST AI 600-1, the OWASP LLM Top 10 (2025) and MITRE ATLAS for that layer.
- Status (as of 2026-10-19): Edition 1 is current. The iso.org page shows stage 60.60 (published) with no amendment or revision project listed. Two companion standards were added in 2025: ISO/IEC 42005 (impact assessment guidance) and ISO/IEC 42006 (rules for certification bodies).
Who it applies to
- Any organisation, of any size or sector, that provides, develops or uses AI systems. The standard asks you to work out your AI role (for example provider, producer, customer, user) as part of Clause 4.
- No legal reach. It applies only where an organisation chooses it, or where a customer, regulator or contract asks for it.
- Commonly requested in enterprise procurement, especially by EU and US buyers, and increasingly referenced as supporting evidence for EU AI Act readiness (see EU AI Act).
Key dates
- New project approved and registered in the SC 42 work programme
- Draft International Standard (DIS) registered
- ISO/IEC 42001:2023 (Edition 1) published
- ISO/IEC 42005:2025 on AI system impact assessment published (iso.org gives month only)
- ISO/IEC 42006:2025 on requirements for AIMS audit and certification bodies published (iso.org gives month only)
Full date record
| Date | Event |
|---|---|
| 2020-08-26 | New project approved in ISO/IEC JTC 1/SC 42 |
| 2022-09-12 | DIS registered (public enquiry stage) |
| 2023-12-18 | ISO/IEC 42001:2023, Edition 1, published (51 pages) |
| 2025-05 | ISO/IEC 42005:2025, AI system impact assessment guidance, published |
| 2025-07 | ISO/IEC 42006:2025, requirements for bodies that audit and certify an AIMS, published |
| 2026-10-19 | iso.org still shows Edition 1 at stage 60.60; no amendment or revision listed |
| Around 2028 | ISO reviews every standard at least every five years, so a first systematic review is expected by then (SecComply inference, not stated on the page) |
Penalties and enforcement
- No fines or legal penalties. Nobody enforces ISO 42001 by law.
- The real "enforcement" is the certification audit. Certification bodies raise major or minor nonconformities; majors must be closed before a certificate is issued or kept.
- Unresolved nonconformities can lead to suspension or withdrawal of the certificate, which can cost you deals that required it.
- Certification process:
- Use a certification body that is accredited for ISO/IEC 42001 by a national accreditation body that is a member of the IAF (in India, check NABCB; elsewhere, for example, ANAB or UKAS). ISO itself does not certify anyone.
- Stage 1 audit: a readiness and documentation review (scope, AI policy, risk and impact assessment method, SoA, internal audit and management review evidence).
- Stage 2 audit: tests whether the system actually runs as documented, with interviews, samples and records.
- Certificate is valid for three years, with surveillance audits (normally yearly) in years one and two and a recertification audit before expiry.
- ISO/IEC 42006:2025 now sets the extra competence and audit-time rules that AIMS certification bodies must meet, on top of the general ISO/IEC 17021-1 rules.
What it means for an Indian company
- SaaS and AI product exporters: ISO 42001 is fast becoming the AI equivalent of ISO 27001 in security questionnaires. A certificate shortens enterprise sales cycles in the EU, UK and US. If you already hold ISO 27001, roughly half the management system (Clauses 4 to 10 shape, document control, internal audit, management review) can be reused.
- BFSI (banks, NBFCs, payment firms): RBI's RBI FREE-AI recommendations (board-approved AI policy, risk tiers, inventory, model lifecycle governance, audit) line up closely with Clauses 5, 6 and 8 and Annex A.2, A.5, A.6. An AIMS is a practical way to show RBI supervisors structured governance, though it does not cover FREE-AI's red teaming, kill switch or customer-facing items on its own.
- IT services and GCCs: clients will push ISO 42001 duties down through contracts (Annex A.10). Expect requests for your AI inventory, impact assessments and supplier controls.
- Personal data: ISO 42001 does not replace DPDP Act compliance. Map your lawful basis and retention work alongside Annex A.7.
- Security gap: if your product is an LLM app or agent, buyers will still ask how you defend against prompt injection and data leakage. Certification does not answer that; SC-AI-029 AI-specific security controls (prompt injection, model abuse) and SC-AI-018 Robustness and adversarial testing (red teaming) do.
- Budget for: a purchased copy of the standard, a gap assessment, one internal audit cycle, a management review and Stage 1 plus Stage 2 audit fees.
Obligations
Clause rows are mandatory for certification. Annex A rows summarise each control group; individual controls apply only if selected in your SoA. All wording is a paraphrase.
| ID | Obligation | Reference | Applies to | Controls |
|---|---|---|---|---|
| ISO42001-01 | Understand your internal and external context, including which legal and regulatory rules touch your AI, and decide what role you play for each AI system (for example provider, developer or user) | Cl. 4.1 | Both | |
| ISO42001-02 | Identify interested parties (customers, regulators, affected people, staff) and which of their requirements the AIMS will address | Cl. 4.2 | Both | |
| ISO42001-03 | Define and document the boundaries and scope of the AIMS, including which AI systems and activities are in or out | Cl. 4.3 | Both | |
| ISO42001-04 | Set up, run, maintain and continually improve the AIMS and the processes it needs | Cl. 4.4 | Both | |
| ISO42001-05 | Top management must lead visibly: tie the AIMS to business strategy, provide resources, promote improvement and support managers in their AI duties | Cl. 5.1 | Both | |
| ISO42001-06 | Publish an AI policy suited to your purpose that gives a frame for AI objectives and commits to meeting requirements and improving; communicate it and make it available | Cl. 5.2 | Both | |
| ISO42001-07 | Assign and communicate roles, responsibilities and authorities for the AIMS, including who reports on its performance to top management | Cl. 5.3 | Both | |
| ISO42001-08 | Plan actions for AI risks and opportunities, and set criteria that separate acceptable from unacceptable AI risk | Cl. 6.1.1 | Both | |
| ISO42001-09 | Define a repeatable AI risk assessment process that identifies, analyses and evaluates risks and gives consistent results | Cl. 6.1.2 | Both | |
| ISO42001-10 | Define AI risk treatment: choose options and controls, compare them against Annex A so nothing needed is missed, produce a Statement of Applicability with justifications, and get risk owner sign-off on residual risk | Cl. 6.1.3 | Both | |
| ISO42001-11 | Define a process to assess the possible consequences of AI systems for individuals, groups and society, and keep the results | Cl. 6.1.4 | Both | |
| ISO42001-12 | Set measurable AI objectives at relevant levels, with owners, resources, deadlines and a way to evaluate results | Cl. 6.2 | Both | |
| ISO42001-13 | Plan changes to the AIMS in a controlled way | Cl. 6.3 | Both | |
| ISO42001-14 | Provide the people, budget, tools and infrastructure the AIMS needs | Cl. 7.1 | Both | |
| ISO42001-15 | Ensure people doing AIMS work are competent (education, training, experience), act on gaps and keep proof | Cl. 7.2 | Both | |
| ISO42001-16 | Make staff aware of the AI policy, their contribution and what happens if they do not follow the AIMS | Cl. 7.3 | Both | |
| ISO42001-17 | Decide what to communicate about the AIMS, internally and externally, when, to whom and how | Cl. 7.4 | Both | |
| ISO42001-18 | Create, update and control the documented information the standard and the AIMS require (versions, access, retention) | Cl. 7.5 | Both | |
| ISO42001-19 | Plan and control the processes needed to meet AIMS requirements, including outsourced processes, and control planned changes | Cl. 8.1 | Both | |
| ISO42001-20 | Run AI risk assessments at planned intervals and when significant changes happen, and keep the results | Cl. 8.2 | Both | |
| ISO42001-21 | Carry out the AI risk treatment plan, check it works, and keep results | Cl. 8.3 | Both | |
| ISO42001-22 | Carry out AI system impact assessments at planned intervals and on significant change, and keep results | Cl. 8.4 | Both | |
| ISO42001-23 | Decide what to monitor and measure, how and when, then analyse and evaluate AIMS performance and effectiveness | Cl. 9.1 | Both | |
| ISO42001-24 | Run internal audits at planned intervals against the standard and your own rules, with an audit programme, objective auditors and reported results | Cl. 9.2 | Both | |
| ISO42001-25 | Top management reviews the AIMS at planned intervals (changes, performance, audit results, risks, improvement chances) and records decisions | Cl. 9.3 | Both | |
| ISO42001-26 | Keep improving how suitable, adequate and effective the AIMS is | Cl. 10.1 | Both | |
| ISO42001-27 | When a nonconformity occurs, react, find the root cause, fix it, check the fix worked and keep records | Cl. 10.2 | Both | |
| ISO42001-28 | Annex A group: maintain a documented AI policy, align it with other company policies (security, privacy, quality) and review it on schedule | A.2 (A.2.2 to A.2.4) | Both | |
| ISO42001-29 | Annex A group: define AI roles and responsibilities, and give people a way to raise concerns about the organisation's AI | A.3 (A.3.2, A.3.3) | Both | |
| ISO42001-30 | Annex A group: document the resources each AI system relies on: data, tooling, compute and the people and skills involved | A.4 (A.4.2 to A.4.6) | Both | |
| ISO42001-31 | Annex A group: run and document impact assessments covering effects on individuals or groups and on society | A.5 (A.5.2 to A.5.5) | Both | |
| ISO42001-32 | Annex A group: manage the AI lifecycle: responsible development objectives, requirements, design records, verification and validation, deployment, operation and monitoring (A.6.2.6), technical documentation and event logs | A.6 (A.6.1.2 to A.6.2.8) | Both | |
| ISO42001-33 | Annex A group: govern data for AI: what data is used, how it is acquired, its quality, provenance and preparation | A.7 (A.7.2 to A.7.6) | Both | |
| ISO42001-34 | Annex A group: give users and other parties the information they need, decide what to report externally, and communicate incidents | A.8 (A.8.2 to A.8.5) | Both | |
| ISO42001-35 | Annex A group: define processes and objectives for responsible use of AI and make sure systems are used as intended | A.9 (A.9.2 to A.9.4) | Deployer | |
| ISO42001-36 | Annex A group: split AI responsibilities clearly with suppliers, partners and customers, and manage supplier AI to your own standard | A.10 (A.10.2 to A.10.4) | Both |
Controls that do the most work here
- SC-AI-001 AI governance policy approved by the board or top management7 obligations
- SC-AI-005 AI risk assessment5 obligations
- SC-AI-040 Board reporting and AI risk metrics5 obligations
- SC-AI-002 AI roles, accountability and oversight committee3 obligations
- SC-AI-006 AI impact assessment (people and society)3 obligations
- SC-AI-008 AI literacy and staff training3 obligations
Evidence an auditor will ask for
- AIMS scope statement and the list of in-scope AI systems.
- Context analysis: interested parties register, legal and regulatory register, your AI role per system.
- Approved AI policy with evidence of communication (intranet page, acknowledgements).
- RACI or role descriptions for the AIMS, including the person who reports to top management.
- AI risk assessment method, risk criteria, risk register and treatment plan with owner sign-off.
- Statement of Applicability listing all 38 Annex A controls, included or excluded, with reasons.
- AI system impact assessments (method plus completed assessments); ISO/IEC 42005 is a useful guide.
- AI objectives with metrics and progress tracking.
- Training and competence records; awareness campaign material.
- Document control procedure and version history.
- Lifecycle records per AI system: requirements, design notes, validation results, deployment approvals, monitoring dashboards, event logs.
- Data records: sources, acquisition terms, quality checks, provenance.
- Supplier and customer agreements showing AI responsibilities.
- Internal audit programme and reports; management review minutes; nonconformity and corrective action log.
Common mistakes
- Treating ISO 42001 certification as proof an AI product is secure. It has no technical controls for prompt injection, jailbreaks, data exfiltration via the model or agent abuse.
- Swapping 10.1 and 10.2. In the 2023 edition 10.1 is continual improvement and 10.2 is nonconformity and corrective action.
- Citing A.3.3 as "training". A.3.3 is reporting of concerns; competence and awareness sit in 7.2 and 7.3, and human resources for AI in A.4.6.
- Inventing Clause 8 sub-numbers beyond 8.4, or placing change planning anywhere other than 6.3.
- Running the impact assessment (6.1.4, 8.4) as a copy of the risk assessment. The risk assessment is about the organisation; the impact assessment is about people and society.
- An SoA that excludes controls without a reason, or that silently drops A.10 because "we only use vendor AI". Vendor AI is exactly what A.10 covers.
- Quoting the standard's text in public material. It is copyrighted.
- Picking a certification body that is not accredited for ISO/IEC 42001 specifically. An unaccredited certificate carries little weight with buyers.
- Scoping the AIMS so narrowly (one chatbot) that the certificate impresses no customer.
Glossary
- AIMS (AI management system): the set of policies, roles, processes and records an organisation uses to manage AI.
- Harmonised structure: the common clause layout (4 to 10) shared by ISO management system standards, so ISO 27001, 9001 and 42001 fit together.
- Annex A: the normative list of 38 AI controls in 9 groups (A.2 to A.10).
- Statement of Applicability (SoA): the document listing every Annex A control, whether you use it and why.
- AI system impact assessment: a structured look at how an AI system may affect people and society; required by 6.1.4 and 8.4.
- Nonconformity: a failure to meet a requirement; "major" findings block certification.
- Accredited certification body: an auditing firm checked by a national accreditation body (for example NABCB in India) as competent to certify against this standard.
- Stage 1 / Stage 2 audit: the two parts of the first certification audit; documents and readiness first, then real operation.
- Surveillance audit: the smaller yearly check that keeps a certificate valid between full audits.
- JTC 1/SC 42: the joint ISO and IEC committee that writes AI standards.
Key takeaways
- Voluntary, certifiable, global: the AI counterpart of ISO 27001, published 18 Dec 2023 and still on Edition 1 with no amendment listed as of 2026-10-19.
- 27 mandatory clause obligations (4.1 to 10.2) plus 9 Annex A control groups (38 controls, chosen through the SoA): 36 rows here.
- Certification: accredited body, Stage 1 then Stage 2, three-year certificate with yearly surveillance; ISO/IEC 42006:2025 now governs the certifiers.
- Governance only: pair it with NIST AI 600-1, OWASP LLM Top 10 (2025) and MITRE ATLAS for technical AI security.
- For Indian BFSI it is a strong backbone for RBI FREE-AI; for exporters it is a sales enabler.
- The date is the publication date, not an enforcement date, and the requirement count depends on granularity (this note uses 36).
Official sources
- ISO/IEC 42001:2023 AI management systems, iso.org catalogue page (status, edition, life cycle; full text must be purchased), accessed 2026-10-19
- ISO/IEC 42005:2025 AI system impact assessment, iso.org, accessed 2026-10-19
- ISO/IEC 42006:2025 Requirements for AIMS audit and certification bodies, iso.org, accessed 2026-10-19
- Clause and Annex A numbering follows the structure in iso 42001 overview; the full text was not accessed for this note, so a reviewer should confirm row references against a purchased copy. No ISO text reproduced.
This is general information, not legal advice. Last verified 19 Oct 2026 against the official source. Laws change; confirm the current position with qualified counsel before acting.