ISO/IEC 42001:2023
Attaches to every line through the responsible-use controls (A.9), to every line with a named tool through the supplier control (A.10.3), and to the lines that draft or decide through verification, operation, logging and impact assessment; the ISO/IEC 23894 risk rows render with it.
On the register, tick "ISO/IEC 42001" and these rows appear on every line the regime reaches. Source framework: ISO/IEC 42001:2023.
Which lines it reaches, and with what
| On every classified line | A.9.2, A.9.3, A.9.4. Responsible use: the documented process for using third-party AI systems, the objectives that guide it, and use within the intended use the documentation states. |
|---|---|
| On lines that name a tool | A.10.3. The supplier: the provider of the tool is assessed against the entity's approach to responsible AI and bound by contract to it. |
| On lines that draft or decide | A.6.2.4, A.8.2. Verification and validation with the results documented, and the information users of the system need to use it as intended. |
| On lines that decide (with review or alone) | A.6.2.6, A.6.2.8. Operation and monitoring with guidance available to the operators, and event logs that support accountability and investigation. |
| On listed-use lines (Annex III, or Article 22 on a line that decides alone) | A.5.2, A.5.4. The impact assessment process and its assessment of the impact on the individuals or groups the line affects. |
| On lines that decide (with review or alone) | ISO/IEC 23894 6.4.2.5, ISO/IEC 23894 B.4. From ISO/IEC 23894, the risk guidance 42001 points to: the controls already in place and how effective they are, and the level of automation as a source of risk. |
| On lines that decide alone | ISO/IEC 23894 6.5.2, ISO/IEC 23894 6.6. From ISO/IEC 23894: the treatment options on a fully automated line (change the level of automation, change the oversight, share through the contract) and monitoring against the system's actual behaviour in operation. |
The record it expects
| informs | The tool produces a summary, a ranking or a flag that a person reads before deciding; the person owns the decision. The record holds: who read the output and what it informed; date and the tool version; the output kept with the decision it informed. |
|---|---|
| drafts | The tool produces the draft of a document, a figure or a position that a person edits and signs; the person owns the content. The record holds: who edited and who signed; date and the tool version; the draft kept beside the signed version; what was changed, classed as omission, misstatement or wording. |
| decides with review | The tool takes the decision and a named person reviews every case or a stated share before the effect; the reviewer can change the outcome. The record holds: reviewer, role and the competence that qualifies them (Art. 26); date and the tool version; sample reviewed: the count out of the total, and the share; overrides: count and rate; escalations and to whom; log reference and retention period (Art. 12, Art. 26); input data checked as relevant and representative (Art. 26). |
| decides alone | The tool takes the decision and the effect follows with no person in between; a person may audit afterwards. The record holds: who audits the line afterwards, role and competence (Art. 26); date, the tool version and the volume decided; audit sample: the count out of the total, and the share; reversals after audit: count and rate; escalations and to whom; log reference and retention period (Art. 12, Art. 26); input data checked as relevant and representative (Art. 26); incidents reported to the provider and the date (Art. 26). |
The ISO/IEC 23894 rows
ISO/IEC 42001 points to ISO/IEC 23894 for AI risk management, so its rows render under this tick: the controls already in place and their effectiveness (6.4.2.5), the level of automation as a risk source (B.4) on every line that decides, and the treatment options and monitoring against actual behaviour (6.5.2, 6.6) on every line that decides alone.
Named reference: ISO/IEC 23894, AI risk management (rendered with ISO/IEC 42001 ticked, which points to it).
The clauses, quoted
10 of 38 in the framework, plus ISO/IEC 23894:2023 rendered with itRequirement text in our own words, read clause by clause from the published standards: our statement of each clause, not the instrument verbatim.
ISO/IEC 42001 A.9.2 Processes for responsible use of AI systemsThe organization shall define and document processes for the responsible use of AI systems, including processes for the use by employees of AI systems provided by third parties.
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.9.3 Objectives for responsible use of AI systemIdentify and record the objectives that steer how AI systems are used responsibly.
Common gap: Are use objectives distinct from development objectives?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.9.4 Intended use of the AI systemMake sure the AI system is used in line with its intended uses and its accompanying documentation.
Common gap: Is off-label use detected and addressed?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.10.3 SuppliersSet up a process so that the services, products or materials the organization obtains from suppliers fit its approach to developing and using AI systems responsibly.
Common gap: standard security due diligence used with nothing AI specific
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.6.2.4 AI system verification and validationAI systems shall be verified and validated, and the results documented. Verification confirms requirements are met; validation confirms intended use is achieved.
Common gap: Are V&V results signed off independently from developers?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.8.2 System documentation and information for usersThe organization shall determine and provide the necessary information for users of the AI system.
Common gap: Are limitations communicated as clearly as capabilities?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.6.2.6 AI system operation and monitoringAI systems shall be operated and monitored according to organizational and operational requirements throughout their lifetime. Operational guidance shall be available to operators.
Common gap: Is monitoring active and alerts acted upon?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.6.2.8 AI system event loggingEvent logs shall be generated and recorded during AI system operations to enable monitoring, accountability, and incident investigation.
Common gap: Are logs sufficient to reconstruct an incident or audit a decision?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.5.2 AI system impact assessment processPut in place a way of assessing what an AI system could mean for individuals, groups of individuals and societies across its life cycle.
Common gap: Does the procedure require consultation with affected stakeholders?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.5.4 Assessing AI system impact on individuals or groupsEvaluate and record how AI systems could affect individuals or groups of individuals over the system's life cycle.
Common gap: Are demographic-specific impacts analyzed where relevant?
Source framework: ISO/IEC 42001:2023
ISO/IEC 23894 6.4.2.5 Identification of controlsThe organization should identify the controls already in place that affect the AI risk, including technical measures in the system, organizational measures around it and the human oversight applied, and how effective they are.
Common gap: Existing controls assumed effective without evidence
Source framework: ISO/IEC 23894:2023
ISO/IEC 23894 B.4 Level of automationAI-related risk source: The degree to which the system acts without human involvement determines how far a wrong output can propagate before anyone intervenes, so the level of automation and the human oversight around it are a source of risk.
Common gap: Full automation with no defined intervention point
Source framework: ISO/IEC 23894:2023
ISO/IEC 23894 6.5.2 Selection of risk treatment optionsOptions balance the benefits against the cost, effort and disadvantages of implementing them and are not mutually exclusive: avoiding the risk by not starting or continuing the activity, taking or increasing the risk to pursue an opportunity, removing the risk source, changing the likelihood, changing the consequences, sharing the risk through contracts or insurance, and retaining the risk by informed decision (ISO 31000:2018, 6.5.2). For AI, removing a risk source or changing likelihood can mean changing data, model, level of automation or human oversight, and sharing can mean contractual terms with AI providers and users.
Common gap: Every AI risk 'accepted' with no option considered
Source framework: ISO/IEC 23894:2023
ISO/IEC 23894 6.6 Monitoring and reviewMonitoring and review assure and improve the quality and effectiveness of the process and should be a planned part of it, covering planning, gathering and analysing information, recording results and providing feedback (ISO 31000:2018, 6.6); for AI it should determine the effectiveness of the risk management process against the system's actual behaviour in operation, detect drift, emerging risks and changed context, and identify improvements.
Common gap: No monitoring of the deployed system's behaviour against the assessed risks
Source framework: ISO/IEC 23894:2023
See what it attaches to your list
Paste the list, tick the regime, and every line it reaches carries these rows. Eight lines free, no account.
Build my decision register