Zum Hauptinhalt springen
AI Compliance Starter Kit · Register

AI Risk Treatment Plan

Updated on 1 min Reviewed by: Cenedril Editorial
ISO/IEC 42001 6.1.3EU AI Act Art. 9(5)

Rating a risk is half the work. ISO/IEC 42001 requires in clause 6.1.3 a plan for how each risk is treated and the approval of the residual risk by the designated management. The AI risk treatment plan shows the mitigating controls, the residual risk and who accepted it and when, per scenario.

What does the template contain?

The CSV file has twelve columns and treats the eight example risks from the AI risk register. In the example, residual risks up to level Medium are acceptable; one scenario is still waiting for confirmation by the risk owner.

Template: AI Risk Treatment Plan

Register Template

AI Risk Treatment Plan

IDRisk scenarioGross riskMitigating controlsElimination or reduction through design and development (Art. 9(5)(a))Residual riskAcceptanceConfirmed byConfirmed onResponsibleOverride reasonNote
KR-001Bias and discriminationHigh (12)A.5.4 Assessing impact on groups of individuals; A.6.2.4 Verification and validation; A.9.4 Intended use–Medium (6)AcceptableHead of HR2026-09-02Head of HR–Monthly analysis of proposals by group
KR-002Excessive automation (automation bias)High (12)A.9.2 Processes for responsible use; A.3.2 AI roles (person exercising oversight)–Medium (6)AcceptableHead of HR2026-09-02Head of HR––
KR-003Hallucination and incorrect outputsHigh (12)A.8.2 Information for users; A.9.2 Processes for responsible use–Medium (6)AcceptableHead of Customer Service2026-09-15Head of Customer Service–Handover to a person for contract and payment questions
KR-004Attacks on confidential dataMedium (8)A.9.2 Processes for responsible use; A.10.3 Suppliers (enterprise version with data processing agreement)–Low (3)AcceptableHead of IT2026-08-05Head of IT––
KR-005Immature technology / model driftHigh (12)A.6.2.6 Operation and monitoring; A.6.2.4 Verification and validationThe hazard was reduced through design and developmentMedium (6)AcceptableHead of Underwriting2026-07-01Head of Data Science–Quarterly performance check against the acceptance thresholds
KR-006Poor data qualityMedium (8)A.7.4 Quality of data; A.7.5 Data provenance; A.7.6 Data preparationThe hazard was reduced through design and developmentLow (3)AcceptableHead of Underwriting2026-07-01Head of Data Science––
KR-007Adversarial examples (targeted evasion)Medium (6)A.6.2.4 Verification and validation; A.6.2.8 Event logsElimination or reduction through design and development was not technically feasibleLow (3)Acceptable––Head of IT Security–Confirmation by the risk owner is pending
KR-008Failure of the external software holding the quality management system documentationMedium (6)A.4.4 Tooling resources; A.6.2.3 Documentation of design and development–Low (2)AcceptableAI Officer2026-07-01AI Officer–Weekly backup of the documentation and a documented fallback

Sources

Frequently asked questions

What is the difference between the risk register and the treatment plan?

The register rates the hazards. The treatment plan records which controls from Annex A of ISO/IEC 42001 mitigate a risk, how high the residual risk is afterwards and who accepted it.

What is the column on Art. 9(5)(a) for?

For high-risk systems the Regulation requires an order: hazards are first eliminated or reduced through design and development, only then through mitigation and control measures. The column records what was achieved through design or why that was not technically feasible.

What happens if the residual risk is above the threshold?

Then further controls are defined. If the organisation accepts the risk nonetheless, the plan records the override reason, for example a time-bound plan or a management decision.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.