ISO 27001 Clause 6.1.2: Information security risk assessment

What Clause 6.1.2 means in practice

Use a repeatable method to identify, analyze, evaluate and own information-security risk. 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 a risk assessment methodology, likelihood and impact criteria, calculation method and risk acceptance criteria.
2. Step 2. Identify relevant assets, processes or scenarios and consider confidentiality, integrity and availability.
3. Step 3. Assign risk owners, analyse realistic consequence and likelihood, evaluate priorities and retain results.
4. Final step. Test a recent example, record the result and improve weak handoffs or decisions.

Ownership

• Risk owners
• ISMS manager
• Security and service 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 6.1.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

• How do you identify information-security risks?
• How were likelihood, impact and acceptance criteria established?
• How do you ensure different assessments use the method consistently?
• Show me a recent risk assessment and how its owners were assigned.

Worked example

A customer portal risk links an internet-facing vulnerability, account takeover scenario, business impact, existing controls, likelihood and accountable owner.

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 a risk assessment methodology, likelihood and impact criteria, calculation method and risk acceptance criteria.
• □ Identify relevant assets, processes or scenarios and consider confidentiality, integrity and availability.
• □ Assign risk owners, analyse realistic consequence and likelihood, evaluate priorities and retain results.
• □ A recent example has been traced through its connected ISMS processes.
• □ Weak results and overdue actions have accountable follow-up.

Common mistakes

• scoring risks without a documented methodology
• changing criteria between assessments
• omitting risk acceptance criteria
• treating vulnerability findings as complete risks
• failing to assign or involve risk owners

Related clauses, controls and resources