Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Mandatory requirement Documented information required
What it means in plain language
When something does not meet requirements (audit finding, incident, policy breach), react to it, find the root cause, fix it so it does not happen again, check the fix worked and keep records.
Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.
Documented information
Nature of nonconformities, actions taken, and results of corrective actions.
Why this requirement matters
Clause 10.2 works best when every nonconformity is treated as a managed work item, not an informal note. Teams should separate symptom correction from root cause removal, assign accountable owners, and keep enough dated evidence to show the action was implemented and later verified as effective. That structure also supports Clause 10.1 continual improvement without mixing the two concepts.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
A finding was closed after the symptom was fixed, but the register lacked root cause analysis, so recurrence prevention was not evidenced.
Effectiveness checks were missing or too early, leaving no dated review showing whether the corrective action actually reduced the underlying issue.
Actions were assigned to no named owner, creating ambiguity over who would implement, validate, and formally close the corrective action.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Log every nonconformity immediately in the Non-Conformity & Corrective Action Register, including source, date, affected requirement, interim containment, and accountable owner. Use a consistent taxonomy so audit findings, incidents, and policy breaches are all traceable to the same record set.
Separate containment from correction and root cause removal. Apply tools such as 5 Whys, fault trees, or timeline reconstruction to identify the mechanism that allowed the issue to occur, then record the chosen corrective action, due date, and dependencies on other teams or suppliers.
Set an effectiveness review date before closing the action. A manager, process owner, or ISMS lead should verify evidence such as re-test results, absence of repeat findings, updated procedure usage, or monitoring trends after an illustrative 30–90 day period.
Keep a closure package with the original issue, root cause, implemented fix, validation outcome, and any spillover changes to training, configuration, or supervision. If the same cause appears again, reopen the record and treat it as a failed corrective action, not a new isolated event.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.