Clause 8 – Operation

Clause 8.2 Information security risk assessment (operation)

Mandatory requirement Documented information required

What it means in plain language

Actually perform risk assessments at planned intervals (e.g. yearly) and whenever significant changes occur, using the method from 6.1.2, and keep the results.

Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.

Documented information

  • Results of the information security risk assessments.

Why this requirement matters

Teams should prove that information security risk assessments are performed on a planned cycle and repeated when material change occurs. Retain the method reference from 6.1.2, identify ownership by the risk owner or ISMS manager, and preserve dated outputs that show scope, criteria, and triggers. A common weakness is treating the risk register as static rather than as a living record tied to incidents, new suppliers, system changes, and formal review dates.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • The organisation has a risk register, but dated reassessments are missing after major changes, leaving stale likelihood and impact ratings.
  • Assessment criteria differ between teams, so similar assets receive inconsistent scores and the basis for comparing risks is unclear.
  • Review notes exist, but they do not identify the trigger, assessor, or version of the underlying register used for the decision.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define a planned reassessment cadence in the risk process, such as annual full reviews plus event-driven reviews for new systems, suppliers, incidents, legal change, or architecture changes. Assign the risk owner to prepare inputs, with the ISMS manager coordinating closure and version control.
  • Use the 6.1.2 method consistently: confirm context, identify threats and vulnerabilities, rate inherent risk, decide whether the existing controls still hold, and record any changed assumptions. Keep the scoring rubric with the register so reviewers can trace why a rating moved.
  • Link reassessment triggers to operational change controls, incident management, supplier review, and management review minutes. If a change request or incident shows exposure has altered, create a dated reassessment entry and note the resulting decision, including acceptance, treatment, or escalation.
  • Maintain evidence samples that an auditor can trace end to end: meeting notes, redlined register entries, approval comments, and action IDs. Where risks are accepted, record who accepted them, on what date, and against which residual risk statement, not just a brief status flag.

What an auditor will ask to see

  • Dated risk assessment worksheet showing scope, trigger, assessor, and scoring rationale.
  • Version history from the Risk Register & Treatment Plan with before-and-after entries.
  • Change, incident, or supplier event that triggered reassessment, linked to the updated risk decision.

Baseline documents in the kit

These free kit documents help you document or evidence clause 8.2. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with 6.1.2 — Information security risk assessment and 8.3 — Information security risk treatment (operation). Keep the ownership and evidence consistent across these activities.

Plan your ISO/IEC 27001 implementation timeline for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.