Clause 4
Context and scope
Your role with respect to AI, the internal and external issues that matter, interested parties, and the boundaries of the AI management system.
ISO/IEC 42001:2023
What an AI management system has to contain, the Annex A controls, how certification works, and where it does and does not help with the EU AI Act.
ISO/IEC 42001:2023 is the international, certifiable standard for an AI management system (AIMS) — the policies, roles, processes and controls an organisation uses to develop, provide or use AI responsibly. It follows the same clause structure as ISO 27001: context, leadership, planning, support, operation, performance evaluation and improvement in clauses 4 to 10, with AI-specific requirements for risk assessment, risk treatment and AI system impact assessment. Annex A lists 38 reference controls under nine objectives, selected through a statement of applicability. Certification is voluntary, but it is fast becoming what enterprise buyers ask AI vendors for, and it gives the EU AI Act's governance duties an auditable home.
Key takeaways
Scope
ISO 42001 has no legal scope — you choose to adopt it. Where it earns its keep is predictable.
Requirements
The clauses are mandatory for certification; Annex A controls are selected through the statement of applicability.
Clause 4
Your role with respect to AI, the internal and external issues that matter, interested parties, and the boundaries of the AI management system.
Clause 5
Top management commitment, an AI policy aligned with the organisation's objectives, and assigned roles and responsibilities.
Clause 6.1.2–6.1.3
A repeatable process to identify and assess AI risks, choose treatments, and produce a statement of applicability that justifies each Annex A control included or excluded.
Clause 6.1.4
Assessing the potential consequences of AI systems for individuals, groups and society — the requirement with no equivalent in ISO 27001. ISO/IEC 42005 gives guidance on how.
Clauses 7–8
Resources, competence, awareness, communication and documented information, and operational planning and control of AI system processes, including changes.
Clauses 9–10
Monitoring and measurement, internal audit, management review, and corrective action for nonconformities.
Annex A
Policies, internal organisation, resources, impact assessment, the AI system life cycle, data, information for interested parties, responsible use, and third-party and customer relationships (A.2 to A.10).
Timeline
ISO 42001 has no statutory deadlines. The dates that matter are the ones your certification cycle and your customers set.
Overlaps
ISO 42001 rarely arrives alone. Where it meets the other regimes you probably already run.
Clauses 4 to 10 share their structure, so leadership, internal audit, management review and documented information can run as one integrated management system.
ISO 42001 supplies much of the governance the Act assumes — inventory, risk management, impact assessment, oversight. It does not cover conformity assessment, CE marking or the Act's specific technical requirements for high-risk systems.
Guidance on AI risk management that can inform how you run the clause 6.1 risk assessment.
An AI system impact assessment and a data protection impact assessment often look at the same system. Running them from the same facts saves describing it twice.
On Noru
The same control library, evidence vault and registers as the rest of your programme — not a separate project.
ISO 42001 is one of the frameworks you switch on in Noru. Its controls go through verification like ISO 27001's, with evidence in the same vault, so one management system serves both.
Where an AI system asserts a management-system control, the ISO 42001 clause is recorded against that system and mapped to the control library, beside its EU AI Act findings.
The AI register comes from the repository and CI rather than a spreadsheet, and every classification carries the name of the person who accepted it and when it expires — the kind of record clause 9 internal audit expects.
No. It is a voluntary standard. Organisations certify because customers, investors or regulators ask how their AI is governed, and a certificate from an accredited body is a stronger answer than a self-assessment.
No, but it helps. It gives you the inventory, risk management, impact assessment and oversight processes the Act relies on. It is not a harmonised standard under the Act, so certification does not create a presumption of conformity, and it does not cover conformity assessment or CE marking for high-risk systems.
Thirty-eight, grouped under nine control objectives numbered A.2 to A.10. You select the ones that apply through your statement of applicability and justify any exclusions. Annex B gives implementation guidance for each.
They share clauses 4 to 10, so the management system mechanics are the same. ISO 27001 protects information; ISO 42001 governs AI systems, with AI risk assessment, AI system impact assessment and AI-specific Annex A controls on data, life cycle and responsible use.
It depends on how much governance already exists. The certification itself is a two-stage audit; most of the time goes into the work before it — building the AI inventory, running risk and impact assessments, and operating the controls long enough to evidence them. An existing ISO 27001 ISMS shortens that considerably.
Regulatory references on this page were last checked on .
A 45-minute walkthrough of ISO 42001 against your own controls, integrations and evidence.