ISO 27001 Clause 10.2: Nonconformity and corrective action

What Clause 10.2 means in practice

Correct nonconformities, address causes, implement proportionate action and verify effectiveness. Treat the clause as part of a management system rather than an isolated document request. Its outputs should influence connected decisions, and later records should show that those decisions were carried out.

The level of formality should match risk and complexity. What matters is clarity, consistency and a traceable connection between the organization’s circumstances, chosen approach and observed result.

Step-by-step implementation

1. Step 1. Record the issue and apply an immediate correction where needed.
2. Step 2. Analyse cause and determine whether similar issues exist elsewhere.
3. Step 3. Plan and implement corrective action proportionate to the effect.
4. Step 4. Review effectiveness, update the ISMS if needed and formally close the record.
5. Final step. Test a recent example, record the result and improve weak handoffs or decisions.

Ownership

• Process owner
• ISMS manager
• Action owners

Evidence and records

A document can show intent. A complete sample also shows who made the decision, what happened next, whether the result was reviewed and how exceptions were handled.

How an auditor may test Clause 10.2

1. Select a current business or ISMS example affected by the clause.
2. Confirm the method, criteria, owner and required output.
3. Trace the example through its decision records and connected processes.
4. Corroborate the record with operational evidence or participant interviews.
5. Follow an exception, change or adverse result to its accountable conclusion.
6. Check that review and improvement occur when circumstances or results change.

Questions to prepare for

• What immediate correction was made?
• How was the underlying cause established?
• Could the same cause affect another process?
• What evidence shows the corrective action was effective?

Worked example

Repeated overdue access removals are corrected immediately, analyzed to a broken HR-IAM handoff, redesigned and checked against later leavers.

A strong audit trail would identify the trigger, relevant information, accountable participants, decision, resulting actions and later verification. It should be possible to explain why the approach was reasonable without reconstructing it from memory.

Smaller and mature implementation approaches

Smaller organization

Use existing leadership, service-management or risk meetings, assign a named owner and retain concise decision records. Avoid parallel governance where an established process can produce the required outcome.

Mature or complex organization

Define group-wide criteria, delegated accountabilities, integrated workflow, quality checks and consolidated performance reporting while preserving local context and evidence.

Practical implementation checklist

• □ Record the issue and apply an immediate correction where needed.
• □ Analyse cause and determine whether similar issues exist elsewhere.
• □ Plan and implement corrective action proportionate to the effect.
• □ Review effectiveness, update the ISMS if needed and formally close the record.
• □ A recent example has been traced through its connected ISMS processes.
• □ Weak results and overdue actions have accountable follow-up.

Common mistakes

• mistaking correction for corrective action
• using generic root causes such as human error
• choosing action before analysing cause
• closing records without effectiveness review

Related clauses, controls and resources