Clause 6 – Planning

Clause 6.1.2 Information security risk assessment

Mandatory requirement Documented information required

What it means in plain language

Define one repeatable method to find, analyse and evaluate information security risks – including how you score likelihood and impact and what level of risk is acceptable. Apply it so that repeated assessments give consistent, comparable results, and give every risk an owner.

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

  • Information about the risk assessment process (methodology) must be retained.

Why this requirement matters

A reliable risk assessment method prevents inconsistent scoring, hidden assumptions, and disputes over what counts as acceptable risk. Teams should define likelihood and impact criteria, how to apply them consistently across scenarios, and how to keep the process repeatable when different people participate. It should also make the risk owner’s role explicit so each assessed risk has someone who can respond, challenge, and escalate decisions.

Common auditor findings to check for

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

  • The risk matrix exists, but likelihood and impact definitions are vague, so similar scenarios receive different scores depending on who performs the assessment.
  • Risk ownership is missing or generic, which leaves no accountable person to confirm analysis, challenge assumptions, or approve acceptance decisions.
  • Assessments are performed ad hoc after incidents, rather than through a repeatable method that can be compared across assets, suppliers, and projects.

How you can implement it

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

  • Document one assessment method in the Risk Assessment Methodology and use it for all ISMS risk work. Define the scoring scale, the evidence expected for each score, the acceptance threshold, and how scenario, asset, and supplier risks are evaluated so results remain comparable over time.
  • Run assessments using practical workshops with IT, operations, HR, procurement, and system owners where relevant. Record the threat source, vulnerable condition, business impact, existing controls, final score, residual risk, and named owner. Avoid single-person scoring for complex areas unless the assumption set is reviewed by a second accountable role.
  • Calibrate scoring with worked examples such as ransomware on a file server, lost laptop with client data, or supplier portal outage. Revisit the examples when the matrix is changed, when material incidents occur, or when staff turnover affects interpretation. This helps keep the method stable rather than subjective.
  • Retain the methodology and completed risk records together so a reviewer can trace how a score was reached. Update the risk register after new projects, major changes, or annual reassessment, and note any exceptions where a risk was accepted above the normal threshold with explicit management approval.

What an auditor will ask to see

  • Risk Assessment Methodology with scoring definitions, acceptance criteria, owner responsibilities, and review triggers.
  • Completed risk register entries showing scenario description, likelihood, impact, residual score, and named risk owner.
  • Workshop notes or calibration examples demonstrating consistent scoring across similar risks and documented management acceptance where needed.

Baseline documents in the kit

These free kit documents help you document or evidence clause 6.1.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.1 — Actions to address risks and opportunities – General and 6.1.3 — Information security risk treatment. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core 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.