10.2 Nonconformity and corrective action
If a nonconformity arises, the organization must respond to it and, as applicable, act to control and correct it and handle what follows from it; evaluate whether action is needed to remove its causes so it does not recur or arise elsewhere, by reviewing it, finding its causes and checking whether similar nonconformities exist or could occur; implement any action needed; review how effective the corrective action was; and change the ISMS if necessary. Corrective actions must suit the effects of the nonconformities. Documented information must be available as evidence of the nature of nonconformities, the actions taken and the results of corrective action.
Source: ISO/IEC 27001:2022, 10.2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.
Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Root cause analyses and checks for similar nonconformities elsewhere · Policy repository / GRC workspace
- Effectiveness reviews of completed corrective actions · Policy repository / GRC workspace
governing documentDocuments that govern the control
- A nonconformity and corrective action register with description, containment, cause analysis, actions and outcome · Policy repository / GRC workspace
- Resulting ISMS changes where needed · Policy repository / GRC workspace
First move
Common gaps auditors find
- Nonconformities are corrected without root cause analysis
- Effectiveness of corrective actions is not verified
- Checks for similar issues elsewhere are skipped
- Records omit the result of corrective action
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet10.1 Continual improvement · A.5.1 Policies for information security