EU AI Act
EU AI Act - High-Risk Classification and Requirements

EU AI Act EUAI-Art.9: Risk management system

Providers shall establish, implement, document and maintain a risk management system as a continuous iterative process planned and run throughout the entire lifecycle of a high-risk AI system, including identification and analysis of known and reasonably foreseeable risks, estimation/evaluation of risks arising from use and from misuse, and adoption of appropriate targeted risk-management measures.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 28 controls across 9 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • AIRMF-GV-1.4 The risk management process and its outcomes are established through transparent policies, procedures, and other controls based on organizational risk priorities
  • AIRMF-MN-1.1 A determination is made as to whether the AI system achieves its intended purpose and stated objectives and whether its development or deployment should proceed
  • AIRMF-MN-1.2 Treatment of documented AI risks is prioritized based on impact, likelihood, or available resources or methods
  • AIRMF-MN-1.3 Responses to the AI risks deemed high priority as identified by the MAP function are developed, planned, and documented, and risk response options can include mitigating, transferring, avoiding, or accepting
  • AIRMF-MN-2.1 Resources required to manage AI risks are taken into account, along with viable non-AI alternative systems, approaches, or methods, to reduce the magnitude or likelihood of potential impacts
  • AIRMF-MP-1.5 Organizational risk tolerances are determined and documented
  • AIRMF-MP-5.1 Likelihood and magnitude of each identified impact are identified and documented, based on expected use, past uses of AI systems in similar contexts, public incident reports, feedback from those external to the team, or other data
  • AIRMF-MS-3.1 Approaches, personnel, and documentation are in place to regularly identify and track existing, unanticipated, and emergent AI risks based on factors such as intended and actual performance in deployed contexts

NIST SP 800-53 Rev 5 · 5 controls

ISO/IEC 42001:2023 · 4 controls

  • A.5.2 AI system impact assessment process
  • A.5.4 Assessing AI system impact on individuals or groups of individuals
  • A.5.5 Assessing societal impacts of AI systems
  • A.6.2.6 AI system operation and monitoring

SOC 2 · 3 controls

  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

GDPR · 2 controls

DORA · 1 control

ISO 27001:2022 · 1 control

  • 5.8 Information security in project management

NIS2 Directive · 1 control

  • Art.21.2.a Policies on risk analysis and on information system security

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in EU AI Act - High-Risk Classification and Requirements

You are reading one control. How much of EU AI Act have you already done?

EU AI Act EUAI-Art.9 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of EU AI Act your existing evidence covers. Hold ISO/IEC 42001:2023 and 17 of 43 EU AI Act controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the ISO/IEC 42001:2023 pair alone.

Query this from an agent

The graph holds this control, the 28 it maps to, and the evidence behind each claim, over MCP and REST.