ISO 27001 Clause 8.2: Information security risk assessment

What Clause 8.2 means in practice

Perform risk assessments using the established method at planned intervals and when significant changes could alter the risk picture. 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. Set a risk assessment schedule and change-based triggers.
2. Step 2. Apply the methodology defined under 6.1.2 consistently.
3. Step 3. Update owners, ratings and priorities, then retain and communicate results.
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 8.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

• When are risk assessments performed?
• Which changes trigger a reassessment?
• Show that the latest assessment followed the approved methodology.

Worked example

A current operation decision is traced through the method for information security risk assessment, 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

• □ Set a risk assessment schedule and change-based triggers.
• □ Apply the methodology defined under 6.1.2 consistently.
• □ Update owners, ratings and priorities, then retain and communicate results.
• □ A recent example has been traced through its connected ISMS processes.
• □ Weak results and overdue actions have accountable follow-up.

Common mistakes

• treating the original assessment as permanent
• reassessing on a calendar but not after major change
• changing scores without recorded rationale

Related clauses, controls and resources