ISO/IEC 42001:2023
Improvement – ISO/IEC 42001:2023

ISO/IEC 42001:2023 10.2: Nonconformity and corrective action

When a nonconformity occurs, react by controlling and correcting it and dealing with consequences; evaluate whether action is needed to remove its causes so it does not recur or happen elsewhere, by reviewing it, finding its causes and checking for similar cases; implement any action needed; review how effective the corrective action was; and change the AIMS if necessary. Corrective action must fit the effects of the nonconformity, and documented evidence of the nonconformity, the actions taken and the results must be kept.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

PCI DSS 4.0 · 7 controls

  • 10.4.3 10.4.3 Exceptions and anomalies from log review addressed
  • 10.7.1 10.7.1 Service providers detect critical control failures (superseded)
  • 10.7.2 10.7.2 Detect and alert on critical security control failures
  • 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
  • 12.10.7 12.10.7 Response procedures for PAN found in unexpected locations
  • 12.4.2.1 12.4.2.1 Documentation of quarterly operational reviews

CIS Controls v8 · 6 controls

  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities
  • CIS-16.3 Perform Root Cause Analysis on Security Vulnerabilities
  • CIS-17.8 Conduct Post-Incident Reviews
  • CIS-18.3 Remediate Penetration Test Findings
  • CIS-18.4 Validate Security Measures
  • CIS-7.2 Establish and Maintain a Remediation Process

NIST SP 800-53 Rev 5 · 5 controls

ISO 27001:2022 · 4 controls

  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.27 Learning from information security incidents
  • 5.35 Independent review of information security

ISO 27002:2022 · 4 controls

  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.27 Learning from information security incidents
  • 5.35 Independent review of information security

NIST SP 800-218 · 4 controls

CMMC 2.0 · 3 controls

  • ISO-50001-10.1 Nonconformity and corrective action
  • 10.1 Nonconformity and corrective action
  • 10.2 Continual improvement
  • NIST-CSF-ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties
  • NIST-CSF-ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities
  • NIST-CSF-RS.AN-08 An incident's magnitude is estimated and validated

SOC 2 · 3 controls

  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-CC7.5 CC7.5 Recovering from security incidents

ISO 22000:2018 · 2 controls

  • 10.1 Nonconformity and corrective action
  • 10.2 Continual improvement

ISO 22301:2019 · 2 controls

  • 10.1 Nonconformity and corrective action
  • 10.2 Continual improvement
  • ISO-22313-10.1 Nonconformity and corrective action
  • ISO22313-10.1 Guidance on nonconformity and corrective action

ISO 30401 · 2 controls

  • ISO30401-10.1 Nonconformity and corrective action
  • ISO30401-15 Nonconformity and corrective action

ISO 37001:2016 · 2 controls

  • 10.1 10.1 Nonconformity and corrective action
  • 10.2 10.2 Continual improvement
  • ISO-37002-10.1 Nonconformity and corrective action
  • ISO37002-10.2 Nonconformity and Corrective Action
  • ISO-39001-10.1 Nonconformity and corrective action
  • ISO39001-10.1 Nonconformity and Corrective Action
  • ISO-41001-10.1 Nonconformity and corrective action
  • ISO41001-10.1 Nonconformity and Corrective Action

ISO 55001:2014 · 2 controls

  • 10.1 Nonconformity and corrective action
  • 10.2 Preventive action

ISO/IEC 27003:2017 · 2 controls

  • 27003-10.1 Nonconformity and Corrective Action
  • ISO27003-10.2 Continual improvement
  • AS9100D-10.2 Nonconformity and Corrective Action
  • SPC1-4.5.4 Nonconformity, Corrective and Preventive Action
  • STAR-NONCONF-01 Nonconformity and corrective action management

FedRAMP High · 1 control

  • CA-5 Plan of Action and Milestones

FedRAMP Moderate · 1 control

  • CA-5 Plan of Action and Milestones

ISO 14001:2015 · 1 control

  • 10.2 Nonconformity and corrective action

ISO 27701:2019 · 1 control

  • 5.8.1 Nonconformity and corrective action
  • ISO28001-4.15 Nonconformity, corrective and preventive action

ISO 37301:2021 · 1 control

  • 10.2 Nonconformity and corrective action

ISO 45001:2018 · 1 control

  • 10.2 Incident, nonconformity and corrective action

ISO 56002 · 1 control

  • ISO-56002-10.2 Deviation, nonconformity and corrective action

ISO 9001:2015 · 1 control

  • 10.2 Nonconformity and corrective action
  • 7.1 7.1 Report and remedy non-compliance

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

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

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