EU AI Act
EU AI Act - Post-Market Monitoring, Market Surveillance and Rights

EU AI Act EUAI-Art.72: Post-market monitoring by providers and post-market monitoring plan for high-risk AI systems

Providers must establish and document a post-market monitoring system proportionate to the nature of the AI technologies and to the risks of the high-risk AI system. That system must actively and systematically collect, document and analyse relevant data on the performance of the system throughout its lifetime, whether provided by deployers or collected through other sources, so the provider can evaluate the system's continuous compliance with the Chapter III Section 2 requirements, including where relevant an analysis of interaction with other AI systems. The system must be based on a post-market monitoring plan that forms part of the Annex IV technical documentation and follows the template adopted by the Commission. Where an equivalent post-market monitoring system and plan already exist under Section A of Annex I legislation, the required elements may be integrated into them provided an equivalent level of protection is achieved.

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

What else in your programme already covers this

This control maps to 30 controls across 8 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.5 Ongoing monitoring and periodic review of the risk management process and its outcomes are planned, organizational roles and responsibilities are clearly defined, including determining the frequency of periodic review
  • AIRMF-GV-5.1 Organizational policies and practices are in place to collect, consider, prioritize, and integrate feedback from those external to the team that developed or deployed the AI system regarding the potential individual and societal impacts related to AI risks
  • 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-MN-4.1 Post-deployment AI system monitoring plans are implemented, including mechanisms for capturing and evaluating input from users and other relevant AI actors, appeal and override, decommissioning, incident response, recovery, and change management
  • AIRMF-MP-5.2 Practices and personnel for supporting regular engagement with relevant AI actors and integrating feedback about positive, negative, and unanticipated impacts are in place and documented
  • AIRMF-MS-1.2 Appropriateness of AI metrics and effectiveness of existing controls is regularly assessed and updated, including reports of errors and impacts on affected communities
  • AIRMF-MS-2.4 The functionality and behavior of the AI system and its components, as identified in the MAP function, are monitored when in production
  • 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 · 4 controls

  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies

ISO 27001:2022 · 3 controls

  • 5.22 Monitoring, review and change management of supplier services
  • 5.27 Learning from information security incidents
  • 8.16 Monitoring activities

ISO/IEC 42001:2023 · 3 controls

DORA · 2 controls

  • DORA-Art.13 Learning and evolving
  • DORA-Art.24 General requirements for the performance of digital operational resilience testing

NIS2 Directive · 1 control

  • Art.21.2.f Policies and procedures to assess the effectiveness of the cybersecurity risk-management measures

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 - Post-Market Monitoring, Market Surveillance and Rights

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

EU AI Act EUAI-Art.72 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 30 it maps to, and the evidence behind each claim, over MCP and REST.