ISO/IEC 42001:2023
Operation – ISO/IEC 42001:2023

ISO/IEC 42001:2023 8.3: AI risk treatment

Implement the AI risk treatment plan under 6.1.3 and verify it works; run the treatment process for newly identified risks; where treatment options prove ineffective, review and revalidate them through 6.1.3 and update the plan. Keep documented results of all AI risk treatments.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 57 controls across 20 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 · 12 controls

PCI DSS 4.0 · 6 controls

  • 10.7.3 10.7.3 Respond promptly to critical security control failures
  • 11.4.4 11.4.4 Correct exploitable findings from penetration tests
  • 6.5.1 6.5.1 Change control procedure for production
  • 6.5.2 6.5.2 Confirm PCI DSS controls after significant change
  • 6.5.3 6.5.3 Separate pre-production from production
  • 6.5.4 6.5.4 Separate roles between production and pre-production

ISO 27001:2022 · 5 controls

  • 5.37 Documented operating procedures
  • 8.25 Secure development life cycle
  • 8.27 Secure system architecture and engineering principles
  • 8.31 Separation of development, test and production environments
  • 8.32 Change management

ISO 27002:2022 · 5 controls

  • 5.8 Information security in project management
  • 8.25 Secure development life cycle
  • 8.27 Secure system architecture and engineering principles
  • 8.31 Separation of development, test and production environments
  • 8.32 Change management

SOC 2 · 5 controls

  • SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

NIST SP 800-218 · 4 controls

CIS Controls v8 · 3 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.10 Apply Secure Design Principles in Application Architectures
  • CIS-16.5 Use Up-to-Date and Trusted Third-Party Software Components
  • NIST-CSF-GV.RM-07 Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated

CMMC 2.0 · 2 controls

FedRAMP Moderate · 2 controls

  • CA-5 Plan of Action and Milestones
  • RA-7 Risk Response

FedRAMP High · 1 control

  • CA-5 Plan of Action and Milestones

HIPAA Security Rule · 1 control

ISO 22000:2018 · 1 control

  • 8.3 Traceability system

ISO 22301:2019 · 1 control

  • 8.3 Business continuity strategies and solutions

ISO 37001:2016 · 1 control

  • 8.3 8.3 Financial controls

ISO 37301:2021 · 1 control

  • 8.3 Raising concerns

ISO 55001:2014 · 1 control

  • 8.3 Outsourcing

ISO 9001:2015 · 1 control

  • 8.3 Design and development of products and services

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

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

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