EU AI Act
EU AI Act - High-Risk Operator Obligations

EU AI Act EUAI-Art.20: Corrective actions and duty of information

A provider that considers, or has reason to consider, that a high-risk AI system it has placed on the market or put into service is not in conformity with the Regulation must immediately take the necessary corrective action to bring it into conformity, withdraw it, disable it or recall it as appropriate, and must inform the distributors of that system and, where applicable, the deployers, the authorised representative and the importers. Where the system presents a risk within the meaning of Art.79(1) and the provider becomes aware of it, the provider must immediately investigate the causes, in collaboration with the reporting deployer where applicable, and inform the competent market surveillance authorities and, where a certificate was issued for the system, the notified body concerned, of the nature of the non-compliance and of any corrective action taken.

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.7 Processes and procedures are in place for decommissioning and phasing out of AI systems safely and in a manner that does not increase risks or decrease the organization's trustworthiness
  • AIRMF-GV-5.2 Mechanisms are established to enable AI actors to regularly incorporate adjudicated feedback from relevant AI actors into system design and implementation
  • AIRMF-GV-6.2 Contingency processes are in place to handle failures or incidents in third-party data or AI systems deemed to be high-risk
  • AIRMF-MN-2.3 Procedures are followed to respond to and recover from a previously unknown risk when it is identified
  • AIRMF-MN-2.4 Mechanisms are in place and applied, and responsibilities are assigned and understood, to supersede, disengage, or deactivate AI systems that demonstrate performance or outcomes inconsistent with intended use
  • AIRMF-MN-4.3 Incidents and errors are communicated to relevant AI actors including affected communities, and processes for tracking, responding to, and recovering from incidents and errors are followed and documented
  • AIRMF-MS-4.3 Measurable performance improvements or declines based on consultations with relevant AI actors including affected communities, and field data about context-relevant risks and trustworthiness characteristics, are identified and documented

NIST SP 800-53 Rev 5 · 6 controls

SOC 2 · 3 controls

  • SOC2-CC2.3 CC2.3 Communication with external parties about internal control (COSO principle 15)
  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • SOC2-CC7.5 CC7.5 Recovering from security incidents

ISO 27001:2022 · 2 controls

  • 5.26 Response to information security incidents
  • 8.8 Management of technical vulnerabilities

ISO/IEC 42001:2023 · 2 controls

  • A.6.2.6 AI system operation and monitoring
  • A.8.4 Communication of incidents

DORA · 1 control

GDPR · 1 control

NIS2 Directive · 1 control

  • Art.21.4 Take corrective measures without undue delay on finding that the measures are not met

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 Operator Obligations

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

EU AI Act EUAI-Art.20 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.