ISO/IEC 42001:2023
Annex A AIMS controls - A.6 AI system life cycle

ISO/IEC 42001:2023 A.6.2.6: AI system operation and monitoring

Define and document what the AI system needs for ongoing operation, which at a minimum means monitoring of the system and its performance, repair, updating and support.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

EU AI Act · 7 controls

  • EUAI-Art.13 Transparency and provision of information to deployers
  • EUAI-Art.14 Human oversight
  • EUAI-Art.15 Accuracy, robustness and cybersecurity
  • EUAI-Art.20 Corrective actions and duty of information
  • EUAI-Art.26 Obligations of deployers of high-risk AI systems
  • EUAI-Art.72 Post-market monitoring by providers and post-market monitoring plan for high-risk AI systems
  • EUAI-Art.9 Risk management system
  • 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-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-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
  • 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

CIS Controls v8 · 4 controls

  • NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

ISO 27002:2022 · 3 controls

  • 5.37 Documented operating procedures
  • 8.16 Monitoring activities
  • 8.32 Change management

APRA CPS 234 · 1 control

FedRAMP High · 1 control

  • CA-7 Continuous Monitoring

FedRAMP Moderate · 1 control

  • CA-7 Continuous Monitoring

ISO 27001:2022 · 1 control

  • 8.16 Monitoring activities

NIST SP 800-218 · 1 control

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 Annex A AIMS controls - A.6 AI system life cycle

You are reading one control. How much of ISO/IEC 42001:2023 have you already done?

ISO/IEC 42001:2023 A.6.2.6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO/IEC 42001:2023 your existing evidence covers. Hold NIST AI Risk Management Framework (AI RMF 1.0) and 30 of 38 ISO/IEC 42001:2023 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 NIST AI Risk Management Framework (AI RMF 1.0) pair alone.

Query this from an agent

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