Compliancemanzill.com
ISO/IEC 23894:2023

ISO/IEC 23894:2023/Process/34 of 34

6.7Recording and reporting

Control family: Process

Control description

The guidance provided in ISO 31000:2018, 6.7 applies.

The organization should establish, record, and maintain a system for the collection and verification of information on the product or similar products from the implementation and post-implementation phases. The organization should also collect and review publicly available information on similar systems on the market.

This information should then be assessed for possible relevance on the trustworthiness of the AI system. In particular, the evaluation should assess whether previously undetected risks exist or previously assessed risks are no longer acceptable. This information can be fed and factored into the organization’s AI risk management process as adjustment of objectives, use cases or lessons learned.

If any of these conditions apply, organizations should perform the following:

- assess the effect on previous risk management activities and feed the results of this assessment back into the risk management process.

- carry out a review of the risk management activities for the AI system. If there is a possibility that the residual risk or their acceptance have changed, the effects on existing risk control measures should be evaluated.

The results of this assessment should be recorded. The risk management record should allow the traceability of each identified risk through all risk management processes. The records can leverage a common template that is agreed upon by the organization.

In addition to the documentation of the scope, context and criteria (see 6.3), risk assessment (see 6.4) and risk treatment (see 6.5), the record should include at least the following information:

- a description and identification of the system that has been analysed;

- methodology applied;

- a description of the intended use of the AI system;

- the identity of the person(s) and organization that carried out the risk assessment;



- the terms of reference and date of the risk assessment;

- the release status of the risk assessment;

- if and to what degree objectives have been met.

How to implement

Coming in phase 2Step-by-step guidance for implementing this control on Microsoft Azure, using services such as Azure Policy, Microsoft Defender for Cloud and Entra ID. It will be matched to your environment.