ISO/IEC 42001:2023
Performance evaluation – ISO/IEC 42001:2023

ISO/IEC 42001:2023 9.2.1: General

Run internal audits at scheduled intervals to find out whether the AIMS conforms to the organization's own requirements and to the standard, and whether it is effectively implemented and maintained.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 8 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.

FedRAMP High · 1 control

  • CA-2 Control Assessments

FedRAMP Moderate · 1 control

  • CA-2 Control Assessments

ISO 22301:2019 · 1 control

ISO 27001:2022 · 1 control

  • 5.35 Independent review of information security
  • NIST-CSF-ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties

SOC 2 · 1 control

  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)

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 Performance evaluation – ISO/IEC 42001:2023

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

ISO/IEC 42001:2023 9.2.1 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 8 it maps to, and the evidence behind each claim, over MCP and REST.