Guide

ISO 27001 risk assessment

The risk assessment is the engine of ISO 27001. Every control you apply, and every one you exclude, should trace back to it. Clauses 6.1.2 and 6.1.3 set out what the assessment and treatment must achieve. Here is a practical method that meets them.

What the standard requires

A practical method

Common mistakes

Assessing once and never again, scoring without defined criteria, and controls in the Statement of Applicability that no risk justifies. Auditors look for the trail from risk to control to evidence.

Next steps

  1. Set the criteria. Agree scoring scales and the acceptance threshold before assessing anything.
  2. Assess and treat. Score risks, choose treatments and map them to controls.
  3. Review on a cadence. Re-run at planned intervals and after significant change.

Frequently asked questions

Asset based or scenario based?

Either. The 2022 edition does not require an asset based approach, as long as the method is defined and repeatable.

How often should we reassess?

At planned intervals, commonly annually, and whenever significant changes occur, such as a new system or supplier.

Related guides

Keep risk and controls connected

The platform links each risk to its Annex A controls and evidence, so your Statement of Applicability always reflects the current assessment.