ISO 27001 Clause 6.3: Planning of changes

What Clause 6.3 means in practice

Plan material ISMS changes deliberately so responsibilities, resources, dependencies and unintended effects are understood before implementation. 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. Define when a change requires structured ISMS planning.
2. Step 2. Assess purpose, consequences, dependencies and resource needs.
3. Step 3. Allocate responsibilities and verify the change after implementation.
4. Final step. Test a recent example, record the result and improve weak handoffs or decisions.

Ownership

• ISMS manager
• Accountable process owner
• Relevant leadership

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 6.3

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

• Which recent changes affected the ISMS?
• How were security consequences assessed before implementation?
• How did you confirm the change achieved its purpose?

Worked example

A current planning decision is traced through the method for planning of changes, its accountable owner, resulting actions and later review.

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

• □ Define when a change requires structured ISMS planning.
• □ Assess purpose, consequences, dependencies and resource needs.
• □ Allocate responsibilities and verify the change after implementation.
• □ A recent example has been traced through its connected ISMS processes.
• □ Weak results and overdue actions have accountable follow-up.

Common mistakes

• making significant changes informally
• ignoring process and people dependencies
• closing changes without verification

Related clauses, controls and resources