Explanations of ISO/IEC 42001:2023
Source is ISO/IEC 42001:2023(en). Title: Information technology — Artificial intelligence — Management system. It was prepared by the joint…
Read articleISO/IEC 42001:2023
For: V, IA
Source: ISO/IEC 42001:2023(en), English. A.10, B.10. The sentence in 8.1 on externally provided processes, products or services is in 42001-09.
The control objective A.10 is to ensure that the organization understands its responsibilities and remains accountable, and that risks are appropriately allocated when third parties are involved at any stage of the life cycle. Three reference controls, to the extent necessary.
A.10.2: ensure that responsibilities in the life cycle of the AI system are allocated between the organization, its partners, suppliers, customers and third parties.
A.10.3: establish a process that ensures that the use of services, products or materials from suppliers is consistent with the organization’s approach to the responsible development and use of AI systems.
A.10.4: ensure that the responsible approach to development and use takes into account the expectations and needs of the customers.
B.10 uses “should”. B.10.2: responsibilities can be divided between parties that provide data, parties that provide algorithms and models, and parties that develop or use the system. The organization should document all parties involved and their roles, and determine their responsibilities. If it supplies a system to a third party, it should ensure a responsible development approach and be able to provide the necessary documentation. Where personal data are processed, responsibilities are usually divided between controllers and processors. ISO/IEC 29100 and, where privacy is to be preserved, controls such as in ISO/IEC 27701 should be considered. The organization can have the role of the controller, of the joint controller, of the processor, or of both. Neither standard is retold here. “Usually” and “can” remain guidance.
B.10.3: suppliers can supply data sets, algorithms, models, libraries or a whole system. Organizations should consider the types of suppliers, what is supplied and the differing risk when they select, set requirements and determine monitoring. They should document how the system and the components are integrated into their own systems. If a system or a component does not fulfil the intended performance, or can have impacts that do not fit the responsible approach, the organization should require corrective actions from the supplier. It can cooperate with the supplier. It should ensure that appropriate documentation is supplied.
B.10.4: the organization should understand expectations and needs when it supplies itself. That can be requirements in design and technology, or contractual requirements, or agreements on use. It should understand where the responsibility lies with the provider and where it lies with the customer, and in doing so meet the needs and expectations. It can identify risks of use by the customer and address them by giving the customer information so that the customer addresses the corresponding risks. The limits of a domain for which the system applies should be communicated to the customer. “Should” and “can”.
Not in this text: a supplier questionnaire, an obligation to certify the supplier, and a determination of roles under data protection law. A.10.2 to A.10.4 are the requirements, to the extent they are necessary. 8.1 requires the control of externally provided processes, products or services that are relevant to the system, independently of that, as a sentence of Clause 8.