ISO/IEC 42001:2023
Annex A AIMS controls - A.3 Internal organization

ISO/IEC 42001:2023 A.3.2: AI roles and responsibilities

Define and allocate AI roles and responsibilities according to the organization's needs.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC1.3 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)
  • SOC2-CC1.5 CC1.5 Accountability for internal control responsibilities (COSO principle 5)
  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • AIGE-IG-1 Establish internal AI governance structures and oversight body
  • AIGE-IG-2 Define roles and responsibilities for AI oversight
  • AIGE-P6 Accountability and Integrity

EU AI Act · 2 controls

  • AIRMF-GV-2.1 Roles and responsibilities and lines of communication related to mapping, measuring, and managing AI risks are documented and are clear to individuals and teams throughout the organization
  • AIRMF-GV-2.3 Executive leadership of the organization takes responsibility for decisions about risks associated with AI system development and deployment
  • 10.2 10.2 Accountable Owner registers each use case once at the right level
  • 5.4.2.a 5.4.2 a System accountability
  • ANSSI-HYG-39 Designate an Information System Security Officer and Make the Role Known

APRA CPS 234 · 1 control

  • CPS234-14 Definition of Information Security Roles and Responsibilities
  • SEC11-BP08 Build a program that embeds security ownership in workload teams
  • 8.1 8.1 Establish clear roles and responsibilities
  • GS-1 Align organization roles, responsibilities and accountabilities

CIS Controls v8 · 1 control

  • CIS-17.5 Assign Key Roles and Responsibilities

FedRAMP High · 1 control

  • PS-9 Position Descriptions (PS-9)

FedRAMP Moderate · 1 control

  • PS-9 Position Descriptions (PS-9)

HIPAA Security Rule · 1 control

ISO 22320:2018 · 1 control

  • ISO-22320-5.4 Roles and responsibilities

ISO 27001:2022 · 1 control

  • 5.2 Information security roles and responsibilities

ISO 27002:2022 · 1 control

  • 5.2 Information security roles and responsibilities

ISO 37001:2016 · 1 control

  • 5.3.1 5.3.1 Roles and responsibilities

ISO/IEC 27010:2015 · 1 control

  • 27010-6.1 Roles and Responsibilities
  • 27050-2.2 Roles and Responsibilities

ISO/IEC 30111:2019 · 1 control

  • 30111-5.3 Roles and responsibilities
  • NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced

NIST SP 800-128 · 1 control

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.3 Internal organization

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

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