ISO/IEC 42001:2023
Context of the organization – ISO/IEC 42001:2023

ISO/IEC 42001:2023 4.3: Determining the scope of the AI management system

Set the boundaries and applicability of the AIMS to define its scope, considering the issues from 4.1 and the requirements from 4.2. Keep the scope as documented information; the scope fixes which of the organization's activities the standard's requirements cover (from the management system itself and leadership through planning, support and operation to evaluation, improvement, the controls and the objectives).

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 26 controls across 17 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-CSF-GV.OC-01 The organizational mission is understood and informs cybersecurity risk management
  • NIST-CSF-GV.OC-02 Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered
  • NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
  • NIST-CSF-GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated

NIST SP 800-53 Rev 5 · 4 controls

ISO 22301:2019 · 3 controls

  • 4.3 Determining the scope of the business continuity management system
  • 4.3.1 General
  • 4.3.2 Scope of the business continuity management system

ISO 56002 · 2 controls

  • ISO-56002-4.3 Determining the scope of the innovation management system
  • ISO56002-4.3 Determining scope of innovation management system

ISO 14001:2015 · 1 control

  • 4.3 Determining the scope of the environmental management system

ISO 22000:2018 · 1 control

  • 4.3 Determining the scope of the food safety management system

ISO 27701:2019 · 1 control

  • 4.3 Application of ISO/IEC 27002:2013 guidelines

ISO 37001:2016 · 1 control

  • 4.3 4.3 Determining the scope of the anti-bribery management system
  • ISO-37002-4.3 Determining the scope of the whistleblowing management system

ISO 37301:2021 · 1 control

  • 4.3 Determining the scope of the compliance management system
  • ISO-39001-4.3 Determining the scope of the RTS management system
  • ISO-41001-4.3 Determining the scope of the FM management system

ISO 45001:2018 · 1 control

  • 4.3 Determining the scope of the OH&S management system
  • 4.3 Determining the scope of the energy management system

ISO 55001:2014 · 1 control

  • 4.3 Determining the scope of the asset management system

ISO 9001:2015 · 1 control

  • 4.3 Determining the scope of the quality management system

PCI DSS 4.0 · 1 control

  • 12.5.2 12.5.2 Annual and change-driven scope confirmation

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 Context of the organization – ISO/IEC 42001:2023

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

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