Top management must set an AI policy that suits the organization's purpose, gives a framework for AI objectives, commits to meeting applicable requirements and commits to continual improvement of the AIMS. The policy must be documented, cross-refer to other organizational policies where relevant, be communicated inside the organization and be made available to interested parties where suitable; the A.2 controls and B.2 guidance apply, and ISO/IEC 38507 is cited for policy design.
This control maps to 72 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.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
NIST-CSF-GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders
You are reading one control. How much of ISO/IEC 42001:2023 have you already done?
ISO/IEC 42001:2023 5.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.