ISO 42001 Requirements: Clauses, Annex A and Evidence

ISO/IEC 42001:2023 sets its requirements in clauses 4 to 10 of the standard, the same harmonised management system structure used by ISO 27001, plus Annex A’s reference controls across nine control themes, A.2 to A.10, which you select and justify through a Statement of Applicability. Annex B gives normative implementation guidance for those controls; Annexes C and D are informative. The requirement text itself is paywalled: ISO publishes only the informative sections free, so the clause list below comes from the standard’s published table of contents. [Source: ISO Online Browsing Platform preview and iso.org standard page, both checked 13-08-2026; published table of contents via Standards Australia and the official ISO preview PDF, checked 13-08-2026]

ISO/IEC 42001 is, in ISO’s own words, “the world’s first AI management system standard”. It specifies requirements for establishing, implementing, maintaining and continually improving an Artificial Intelligence Management System (AIMS), and it applies to any organisation, regardless of size, type and nature, that provides or uses products or services that use AI systems. [Source: iso.org standard page and ISO OBP Clause 1 Scope, checked 13-08-2026]

The ISO 42001 requirements at a glance

Every certified AIMS is built from the same parts: seven requirement clauses (4 to 10), a normative Annex A of reference controls applied through a Statement of Applicability, normative implementation guidance in Annex B, and two informative annexes. [Source: published table of contents via Standards Australia and the official ISO preview PDF, checked 13-08-2026]

GroupReferenceStatusWhat it asks, in one line
Context of the organizationClause 4 (4.1 to 4.4)Normative requirementDefine your context, interested parties and the scope of the AIMS
LeadershipClause 5 (5.1 to 5.3)Normative requirementTop management commitment, an AI policy, assigned roles
PlanningClause 6 (6.1 to 6.3)Normative requirementAI risk assessment, AI risk treatment, AI system impact assessment, AI objectives
SupportClause 7 (7.1 to 7.5)Normative requirementResources, competence, awareness, communication, documented information
OperationClause 8 (8.1 to 8.4)Normative requirementRun the risk assessment, risk treatment and impact assessment in operation
Performance evaluationClause 9 (9.1 to 9.3)Normative requirementMonitor the AIMS, run internal audits, hold management reviews
ImprovementClause 10 (10.1 to 10.2)Normative requirementContinual improvement, nonconformity and corrective action
Reference controlsAnnex A (A.2 to A.10)NormativeControl objectives and controls selected via the Statement of Applicability
Implementation guidanceAnnex B (B.2 to B.10)NormativeGuidance for implementing the Annex A controls
Objectives and risk sourcesAnnex CInformativePotential AI-related organizational objectives and risk sources
Sector useAnnex DInformativeUsing the AIMS across domains or sectors

[Source: published table of contents via Standards Australia, and the official ISO preview PDF, both checked 13-08-2026]

Why listen to us

Atoro is an Irish AI governance and cyber compliance consultancy for software companies, and the first consultancy in Europe certified against ISO 42001. Our certificate is AIMS-AT-120224, issued by A-LIGN under ANAB accreditation. We deliver ISO 42001 implementation on a fixed scope and independent ISO 42001 internal audits for software companies across the UK and Ireland, so the requirements below are clauses we work to, not clauses we have only read.

The full requirements list, grouped

The standard’s normative requirements sit in clauses 4 to 10 and Annex A. What follows is the complete structure as published in the table of contents; ISO sells the requirement text itself, so nothing here reproduces paywalled wording. [Source: published table of contents via Standards Australia and the official ISO preview PDF, checked 13-08-2026]

Clauses 4 to 10: the management system requirements

  • 4 Context of the organization:
    • 4.1 Understanding the organisation and its context;
    • 4.2 Understanding the needs and expectations of interested parties;
    • 4.3 Determining the scope of the AI management system;
    • 4.4 AI management system
  • 5 Leadership:
    • 5.1 Leadership and commitment;
    • 5.2 AI policy;
    • 5.3 Roles, responsibilities and authorities
  • 6 Planning:
    • 6.1 Actions to address risks and opportunities
      • 6.1.1 General,
      • 6.1.2 AI risk assessment,
      • 6.1.3 AI risk treatment,
      • 6.1.4 AI system impact assessment;
    • 6.2 AI objectives and planning to achieve them;
    • 6.3 Planning of changes
  • 7 Support:
    • 7.1 Resources;
    • 7.2 Competence;
    • 7.3 Awareness;
    • 7.4 Communication;
    • 7.5 Documented information
      • 7.5.1 General,
      • 7.5.2 Creating and updating documented information,
      • 7.5.3 Control of documented information
  • 8 Operation:
    • 8.1 Operational planning and control;
    • 8.2 AI risk assessment;
    • 8.3 AI risk treatment;
    • 8.4 AI system impact assessment
  • 9 Performance evaluation:
    • 9.1 Monitoring, measurement, analysis and evaluation;
    • 9.2 Internal audit
      • 9.2.1 General,
      • 9.2.2 Internal audit programme;
    • 9.3 Management review
      • 9.3.1 General,
      • 9.3.2 Management review inputs,
      • 9.3.3 Management review results
  • 10 Improvement:
    • 10.1 Continual improvement;
    • 10.2 Nonconformity and corrective action

[Source: published table of contents via Standards Australia and the official ISO preview PDF, checked 13-08-2026]

Two structural facts matter before you start. First, this is the harmonised structure shared by all modern ISO management system standards, which ISO says “facilitates implementation and consistency with other management system standards, e.g. related to quality, safety, security and privacy”. If you already run ISO 27001, clauses 4, 5, 7, 9 and 10 will feel familiar; the genuinely new work concentrates in clauses 6 and 8 and Annex A. [Source: ISO OBP, Introduction, checked 13-08-2026] Second, the standard’s single normative reference is ISO/IEC 22989:2022, the AI concepts and terminology standard, so its definitions underpin the requirement text. [Source: ISO OBP, Clause 2, checked 13-08-2026]

Annex A: reference controls across nine control themes

Annex A, “Reference control objectives and controls”, is normative. It organises controls under nine control themes, A.2 to A.10. The published table of contents lists the same themes under Annex B (which mirrors the Annex A controls with implementation guidance):

  • A.2 / B.2 Policies related to AI
  • A.3 / B.3 Internal organization
  • A.4 / B.4 Resources for AI systems
  • A.5 / B.5 Assessing impacts of AI systems
  • A.6 / B.6 AI system life cycle
  • A.7 / B.7 Data for AI systems
  • A.8 / B.8 Information for interested parties
  • A.9 / B.9 Use of AI systems
  • A.10 / B.10 Third-party and customer relationships

[Source: published table of contents via Standards Australia, checked 13-08-2026]

A note on the control count, because vendors disagree on it. Counting the control items in the published table of contents gives 38 reference controls across the nine control themes. ISO’s public pages do not print that number, and some vendor sources say 39, so treat 38 as a count derived from the published table of contents, not an ISO-published figure. [Source: derivation from the published table of contents, checked 13-08-2026; vendor sources differ between 38 and 39]

The Statement of Applicability

The Statement of Applicability (SoA) is the mechanism that turns Annex A into your control set. The standard defines it, in the publicly visible terminology clause, as “documentation of all necessary controls and justification for inclusion or exclusion of controls”, and its Note 1 states: “Organizations may not require all controls listed in Annex A or may even exceed the list in Annex A with additional controls established by the organization itself.” [Source: ISO OBP, Clause 3.26, checked 13-08-2026]

Two practical consequences. You do not have to implement every Annex A control; you have to justify each inclusion and exclusion in the SoA. And you may add controls of your own where Annex A does not cover a risk your assessment found. The SoA is therefore the document an audit tests your Annex A decisions against, because it is where your risk assessment meets the control set.

Annexes B, C and D

Annex B, “Implementation guidance for AI controls”, is normative and walks the same nine themes as Annex A with guidance on implementing each control. Annex C, “Potential AI-related organizational objectives and risk sources”, and Annex D, “Use of the AI management system across domains or sectors”, are both informative: they help you plan, they are not audited requirements. [Source: published table of contents via Standards Australia and the official ISO preview PDF, checked 13-08-2026]

What each group of requirements asks for, and the evidence that satisfies it

The clause titles name the deliverables. Each group below states what the clause covers and the documented information its titles point to; the exact requirement wording sits in the paid standard, and per-clause auditor expectations beyond the titles are flagged at the end of this section.

Clause 4: Context of the organization

Clause 4 asks you to define the world the AIMS operates in: your context, your interested parties, and a documented scope.

The evidence the clause titles point to: a documented analysis of internal and external context (4.1), a record of interested parties and their requirements (4.2), and a written AIMS scope statement (4.3). Scope is the decision everything else inherits: which AI systems, products, sites and teams sit inside the AIMS. Practitioner forum language warns that teams get this wrong early: “A lot of people misclassify themselves at the start and build the wrong scope.” Treat that as a practitioner warning from a forum thread, not a published statistic. [Source: r/ISO27001, Lead Auditor course thread, captured 06-08-2026, language source only]

Clause 5: Leadership

Clause 5 asks top management to own the AIMS: visible commitment, an AI policy, and named roles, responsibilities and authorities.

The evidence the titles point to: an approved AI policy (5.2) and documented role assignments (5.3), with leadership commitment shown through decisions and records rather than a signed statement alone (5.1). The AI policy causes real uncertainty in practice. One in-house implementer working towards certification wrote: “I’m struggling to finish it because I’m unsure how detailed it needs to be… how long are your AI policies?” That is the right instinct to bring to an auditor conversation: the policy has to connect to your roles, objectives and controls, and its length follows from that, not from a template. [Source: r/cybersecurity thread “Seeking Guidance on AI Policy for ISO 42001 Certification”, 28-07-2025, captured 13-08-2026, language source only]

Clause 6: Planning

Clause 6 is where ISO 42001 stops being ISO 27001 with new labels. It requires an AI risk assessment, an AI risk treatment plan, an AI system impact assessment, and AI objectives with plans to achieve them.

The four planning deliverables named in the titles: risk assessment records (6.1.2), risk treatment decisions (6.1.3), the AI system impact assessment (6.1.4), and measurable AI objectives (6.2), plus controlled planning of changes (6.3). The impact assessment is the one with no ISO 27001 equivalent, and practitioners flag it as the hardest gap: “The AI Impact Assessment requirement in clause 6 has no equivalent in ISO 27001 or 9001… Most companies I’ve worked with have nothing here. It’s the single most common gap.” Again, that is practitioner forum language, useful as a warning, not a published fact. [Source: r/ISO27001, Lead Auditor course thread, captured 06-08-2026, language source only]

Clause 7: Support

Clause 7 covers the machinery that keeps the AIMS running: resources, competence, awareness, communication and controlled documented information.

The evidence the titles point to: competence and training records for people in AIMS roles (7.2), evidence that staff are aware of the AI policy and their part in it (7.3), a communication approach (7.4), and document control: created, updated and version-controlled documented information (7.5). If you hold ISO 27001, this clause’s discipline is the same one you already operate.

Clause 8: Operation

Clause 8 takes the plans from clause 6 and makes them operational: the risk assessment, risk treatment and impact assessment actually run, on live AI systems, under operational planning and control.

The repeated titles are the point. Clause 6 plans the AI risk assessment, treatment and impact assessment; clause 8 executes them (8.2, 8.3, 8.4) under controlled operations (8.1). The evidence is operating records: completed assessments, treatment actions carried out, impact assessments performed for the AI systems in scope. This is also why certification bodies expect the system to have run before they audit it. NQA, a UKAS-accredited certification body, states you must demonstrate that your management system “has been operational for a minimum of three months and has been subject to a management review and a full cycle of internal audits” before the initial certification audit. [Source: NQA ISO 42001 page, checked 13-08-2026]

Clause 9: Performance evaluation

Clause 9 asks you to check the AIMS works: monitoring and measurement, an internal audit programme, and management reviews with recorded inputs and results.

The evidence the titles point to: monitoring and measurement records (9.1), an internal audit programme and completed audit reports (9.2), and management review records covering the required inputs and results (9.3). The internal audit is a common outsourcing point because it must be independent of the people running the system; it is also one of the two services Atoro delivers in this standard, noted above.

Clause 10: Improvement

Clause 10 closes the loop: continual improvement, and a corrective action process for nonconformities.

The evidence the titles point to: records of nonconformities, the corrective actions taken and their results (10.2), and evidence the AIMS itself improves over time (10.1). Auditors read clause 9 and clause 10 records together: findings should produce corrective actions, and corrective actions should close.

A sourcing caveat for this whole section: the evidence descriptions above are derived from the published clause titles and certification-body statements. The only clause-by-clause requirement-to-evidence mapping our research found in the public domain is a single-author, unreviewed GitHub repository, which is not a citable fact source.

Common failure points

The failures practitioners report concentrate in three places: the clause 6 impact assessment, the Annex A data controls, and scope set wrong at the start. All three come from practitioner forum language, not published data, so treat them as informed warnings.

  • The AI system impact assessment (6.1.4 and 8.4) is the most reported gap. “The AI Impact Assessment requirement in clause 6 has no equivalent in ISO 27001 or 9001… Most companies I’ve worked with have nothing here. It’s the single most common gap.” Unlike the risk assessment, which has an ISO 27001 analogue, the impact assessment asks what your AI systems do to individuals and groups, and teams extending an ISMS often have no artefact that answers it. [Source: r/ISO27001, Lead Auditor course thread, language source only]
  • The data controls are heavier than expected. The same practitioner: “Annex A data controls are brutal in practice.” The A.7 / B.7 theme, “Data for AI systems”, is where training data, input data and data quality meet the management system, and it rewards companies that already document their data lineage. [Source: r/ISO27001, Lead Auditor course thread, language source only; theme title from the published TOC]
  • Scope misclassification at the start. “A lot of people misclassify themselves at the start and build the wrong scope.” The standard applies to organisations that provide or use AI systems, and which side of that line your products sit on changes the control emphasis. [Source: r/ISO27001, Lead Auditor course thread, language source only; scope wording from ISO OBP Clause 1]
  • The AI policy stalls the programme. An in-house implementer reported being stuck on “how detailed it needs to be”, asking peers how long their AI policies are. The fix is to write the policy against your roles, objectives and SoA, not to calibrate its page count. [Source: r/cybersecurity, 28-07-2025, language source only]
  • Treating certification as a documentation project. A US consultancy that publishes its delivery experience puts it plainly: “The most common failure is treating it as a documentation project. An AIMS written in a quarter but never operated produces Stage 2 nonconformities on evidence, which are the hardest kind to fix quickly, because the only remedy is time.” [Source: BD Emerson, checked 13-08-2026, tier 2]

Requirements people assume exist, but do not

Most of the folklore around ISO 42001 requirements comes from treating it like a product certification or a fixed checklist. The published structure says otherwise.

  • “We must implement every Annex A control.” No. The Statement of Applicability definition states organisations “may not require all controls listed in Annex A” and may add their own. You justify inclusions and exclusions; you do not adopt the list wholesale. [Source: ISO OBP, Clause 3.26 Note 1, checked 13-08-2026]
  • “ISO 42001 certifies our AI product or model.” It does not. ISO frames the standard as a management system standard using Plan-Do-Check-Act: “Rather than looking at the details of specific AI applications, it provides a practical way of managing AI-related risks and opportunities across an organization.” The certificate covers your management system, not a model. [Source: iso.org, ISO/IEC 42001 FAQ, checked 13-08-2026]
  • “ISO 42001 certification makes us EU AI Act compliant.” Certification to a voluntary management system standard is not the same thing as conformity with the EU AI Act, and buyer-forum threads warn that some sellers present ISO 42001 certification as EU AI Act conformity, which it is not. Whether a European adoption of ISO/IEC 42001 becomes a harmonised standard under the AI Act is unresolved as of our research date. [Source: r/ISO27001 search sample, language source only, checked 13-08-2026]
  • “ISO publishes the requirements free online.” Only the informative sections are publicly available; clauses 4 to 10 are not in the free preview. The standard costs CHF 225 (Swiss francs) from iso.org, with identical national adoptions sold by national bodies. [Source: ISO OBP preview notice and iso.org standard page, checked 13-08-2026]
  • “There is an official control count.” ISO’s public pages print no Annex A count. The figure 38 comes from counting control items in the published table of contents; some vendor sources say 39. [Source: derivation from the published table of contents, checked 13-08-2026]
  • “The standard sets a minimum operating period before certification.” The public structure does not state one. The three-month floor comes from certification bodies: NQA publishes it, other bodies set their own expectations. [Source: NQA ISO 42001 page, checked 13-08-2026]
  • “It is only for large enterprises.” The scope clause says the standard “is applicable to any organization, regardless of size, type and nature, that provides or uses products or services that utilize AI systems.” [Source: ISO OBP, Clause 1, checked 13-08-2026]

For what meeting these requirements costs, our ISO 42001 certification cost guide covers the published market figures.

FAQs

1. What are the requirements of ISO 42001?

The requirements sit in clauses 4 to 10 of ISO/IEC 42001:2023: context of the organisation, leadership, planning, support, operation, performance evaluation and improvement. Alongside them, Annex A provides reference controls across nine control themes (A.2 to A.10), which you select and justify through a Statement of Applicability. Annex B is normative implementation guidance; Annexes C and D are informative. [Source: published table of contents via Standards Australia, checked 13-08-2026]

2. How many controls does ISO 42001 Annex A have?

Counting the control items in the standard’s published table of contents gives 38 reference controls across the nine control themes. ISO does not print that count on its public pages, and some vendor sources say 39, so treat any bare count with caution. What matters operationally is the Statement of Applicability: you justify which controls apply, not how many there are. [Source: derivation from the published TOC via Standards Australia, checked 13-08-2026]

3. Do we have to implement every Annex A control?

No. The standard’s own definition of the Statement of Applicability notes that organisations “may not require all controls listed in Annex A or may even exceed the list in Annex A with additional controls established by the organization itself.” You document each inclusion and exclusion with justification, and you can add controls of your own where your risk assessment calls for them. [Source: ISO OBP, Clause 3.26, checked 13-08-2026]

4. What is the Statement of Applicability in ISO 42001?

It is the document that connects your risk assessment to your control set: “documentation of all necessary controls and justification for inclusion or exclusion of controls”, in the standard’s terminology clause. Because it shows why your Annex A selections look the way they do, it is the document an audit tests those selections against. [Source: ISO OBP, Clause 3.26, checked 13-08-2026]

5. Do we need ISO 42001 if we have ISO 27001?

Not automatically, but the work transfers well. ISO 42001 uses the same harmonised management system structure as ISO 27001, which ISO says exists to facilitate consistency across management system standards, so clauses covering context, leadership, support, performance evaluation and improvement share their machinery. The new work concentrates in the AI-specific requirements: the AI risk assessment, the AI system impact assessment, and the Annex A control themes. [Source: ISO OBP, Introduction, checked 13-08-2026; published TOC]

6. How detailed does the AI policy need to be for ISO 42001?

The standard requires an AI policy under clause 5.2, but its public text specifies no length or format, and practitioners asking the same question online get no fixed answer either. The workable test is whether the policy connects to your assigned roles, your AI objectives and your Statement of Applicability, because an auditor will follow those links. Write it against your management system, not against someone else’s page count. [Source: clause title from the published TOC; r/cybersecurity thread, 28-07-2025, language source only]

7. Is ISO 42001 certification legally required, or does it make us EU AI Act compliant?

No law we can point to makes ISO 42001 certification mandatory; it is a voluntary international standard, and buyer-side forum threads describe ISO 42001 starting to appear in enterprise procurement requirements. Certification is also not the same as EU AI Act conformity, and the standard’s status as a harmonised European standard under the AI Act was unresolved as of our research date. Treat “get certified and you are AI Act compliant” as a red flag in any pitch. [Source: iso.org standard page, checked 13-08-2026; buyer-side forum threads, language source only]

8. Where can we read the actual requirement text?

Buy the standard from iso.org or your national standards body; the iso.org list price is CHF 225 (Swiss francs). ISO’s free Online Browsing Platform shows only the informative sections, so clauses 4 to 10 are not readable there, but the full table of contents is visible in the free official preview PDF and on national-body store pages. [Source: iso.org standard page and ISO OBP, checked 13-08-2026]

Next step

If the structure above tells you one thing, it is that scoping and the Statement of Applicability decide how much work this standard asks of you. The honest next step is a scoping conversation about which AI systems you provide or use and who is asking you to prove it. Atoro delivers ISO 42001 implementation at a fixed price agreed after scoping, with independent internal audits for the clause 9.2 requirement, and we will tell you if the scope you need is smaller than the one you feared.

Sources

Tier 1:

  1. ISO, ISO/IEC 42001:2023 standard page (“world’s first AI management system standard”; AIMS requirements description; Edition 1, published 2023-12, 51 pages, CHF 225), checked 13-08-2026.
  2. ISO Online Browsing Platform, ISO/IEC 42001 preview (only informative sections public; harmonised structure Introduction text; Clause 1 Scope; Clause 2 normative reference ISO/IEC 22989:2022; Clause 3.26 Statement of Applicability definition and Note 1), checked 13-08-2026.
  3. Standards Australia store page for AS ISO/IEC 42001:2023 (identical national adoption; published table of contents with clause and annex structure), checked 13-08-2026.
  4. Official ISO preview PDF hosted by licensed reseller iTeh (ISO copyright pages; published table of contents), checked 13-08-2026.
  5. NQA (UKAS-accredited certification body), ISO 42001 page (“operational for a minimum of three months and has been subject to a management review and a full cycle of internal audits”), checked 13-08-2026.

Tier 2 (provider named, date checked):

  1. BD Emerson (US consultancy), “The ISO 42001 Certification Path” (documentation-project failure quote), checked 13-08-2026.

Language sources only (never cited as fact):

  1. Reddit r/ISO27001, “Took the ISO 42001 Lead Auditor course. Here’s what actually surprised me about the exam.” (impact assessment gap, Annex A data controls, scope misclassification quotes), captured 06-08-2026
  2. Reddit r/cybersecurity, “Seeking Guidance on AI Policy for ISO 42001 Certification“, 28-07-2025 (AI policy depth question), captured 13-08-2026.
  3. Reddit r/ISO27001 search sample (buyer-forum threads on the AI Act conflation, characterised in “Requirements people assume exist, but do not”), captured 06-08-2026;restrict_sr=on&sort=relevance&t=all

Atoro supplied facts: Atoro’s positioning, first-in-Europe certification claim, certificate AIMS-AT-120224 (A-LIGN, ANAB accreditation), fixed-scope ISO 42001 implementation and independent ISO 42001 internal audit services.