How to Carry Out an ISMS Risk Analysis: Method and Sample Records

Risk criteria, choice of method, workshops, a sample risk register and treatment plan: an ISMS risk analysis for ISO/IEC 27001 that holds up in an audit, step by step.
Technical summary
Technology
ISO/IEC 27001 Clause 6, ISO/IEC 27005
Topic
Risk analysis
Level
Intermediate
In this article8 sections

When an auditor opens the risk register, the first thing they look at isn’t the scores but the decision behind them: Why is this risk a 12, why is it being reduced, who approved it? If there’s no answer, the risk analysis is an Excel file, not an input to the ISMS. Which controls will be applied, how much budget will be allocated and which risks will be knowingly accepted all come out of this work. ISO/IEC 27001 doesn’t impose a specific method; but it expects results to be consistent, comparable and valid. The method and sample records below are at a level a medium-sized organization can apply.

1. Set the risk criteria with management

Before starting, you need three things approved by management: a likelihood scale, an impact scale and a risk acceptance criterion.

Score Likelihood Impact (financial / operational / legal examples)
1 Not expected Negligible; processes aren’t affected
2 Once every few years Short disruption in one unit
3 Once a year Hours of outage in a critical process
4 A few times a year Customer delivery or a legal obligation is affected
5 Continuous Days of outage, serious financial and reputational loss

Risk score = likelihood × impact. Example acceptance criterion: 8 and below is acceptable; 9–14 is treated by decision of the risk owner; 15 and above goes on management’s agenda.

Without written definitions of the scales, everyone in every workshop gives their own “3”. Make the impact scale concrete in your organization’s own language: instead of “hours of outage”, write something a manager will understand immediately, such as “one shift’s production lost”. Management must also sign the acceptance criterion. If IT sets the criterion, every accepted risk stays on IT’s shoulders.

2. Choose the method: asset or scenario?

In the asset-based method, threats and vulnerabilities are assessed for each information asset (e.g. the ERP database); it’s detailed but becomes hard to manage as the number of assets grows. In the scenario-based method, realistic incident scenarios (e.g. “the ERP is encrypted by ransomware”) are assessed; it’s easy to explain to management. ISO/IEC 27005:2022 describes both approaches. For small and medium-sized organizations, the scenario-based method is usually more sustainable.

In organizations that start with the asset-based method, you may find this picture: an asset list hundreds of rows long, the same five threats on every row, the same score for every threat. The file grows, and no decisions come out of it. In the scenario method, the asset inventory is kept separately and scenarios reference the relevant assets. The inventory isn’t lost. The risk register stays readable.

3. Identify risks in workshops

For each critical process, 60–90 minute workshops are held with the process owner, IT and, if needed, a production representative. The questions asked in the workshop: Which information and systems does this process depend on? What kinds of incidents have happened in recent years? Which incident would affect this process most? What controls are in place today, and do they really work?

The last question is the most important. When you get the answer “We have backups”, follow up with: When was the last restore done, is the backup independent of the domain, could an attacker delete the backup with an admin account? A likelihood score given without questioning the effectiveness of existing controls measures hope, not reality. Invite the person from IT who actually manages the system to the workshop; someone who can open the screen and show it.

4. Sample risk register

Field R-07 R-12
Scenario The ERP is encrypted by ransomware Customer drawings are accessed with a leaver’s account
Risk owner Operations director Engineering manager
Existing controls Daily backup (in the same domain), antivirus Manual account closure, irregular
Likelihood × impact 3 × 5 = 15 3 × 4 = 12
Decision Reduce Reduce
Controls Immutable backup, restore testing, EDR, separation of admin accounts Automatic HR–IT notification, monthly account reconciliation
Target / residual risk End of quarter / 2 × 5 = 10 End of month / 1 × 4 = 4
SoA reference Information backup; privileged access; malware protection Identity management; access rights

The point to note in R-07: after the controls are applied, impact stays at 5; only likelihood drops. If ransomware does happen, the ERP stopping is still severe; what changes is the chance of it happening and recoverability. If you also want to lower the impact, a separate control that shortens restore time (e.g. a standby backup server) is needed. As the residual risk is 10 and the acceptance threshold is 8, the risk owner must knowingly approve this risk; that approval must be recorded.

5. Risk treatment plan and approval

Decisions for risks above the acceptance threshold are gathered in the risk treatment plan: control, owner, target date and, if needed, budget. The residual risks expected after the plan and controls are applied are approved by the risk owners. The selected controls are carried over to the Statement of Applicability; see What is an SoA?

There are four treatment options: reduce, avoid (stop the activity), share (through insurance or contract) and accept. Sharing doesn’t eliminate the risk. Cyber insurance can split the financial impact; it doesn’t stop production from halting. The plan should separately mark controls that require budget approval and go into management review in that form.

6. Monitoring and updating

  • A full review at planned intervals (usually once a year).
  • Updates when significant changes occur (a new system, location, acquisition or major incident).
  • Incident records and audit findings feeding into the risk register.
  • Reporting the risk status to management review.

Link change management and the risk register: when a new cloud service, new supplier access or new location comes up for approval, the form should have a field for “impact on the risk register”. That one field heads off changes that would otherwise wait until the annual review.

Common mistakes

  1. Giving every risk the same score; with no differentiation, prioritization is impossible.
  2. Listing only the IT manager as risk owner.
  3. Scoring a risk low without questioning the effectiveness of existing controls.
  4. Not recording the justification for accepted risks.
  5. Leaving the risk register as a file opened once a year.

A short self-audit checklist:

  • Are likelihood, impact and acceptance criteria written down and approved by management?
  • Is there at least one workshop record for each critical process?
  • Is each risk’s owner, treatment decision and residual risk approval recorded?
  • Do the selected controls reference the related risk in the SoA?
  • Was the register updated after the last major change or incident?

Frequently asked questions

Is software needed for risk analysis?

No. A well-designed Excel or SharePoint list is enough for most organizations. As scale grows, GRC tools can be considered.

How many risks should be identified?

There’s no fixed number. In medium-sized organizations, 25–60 scenarios is a manageable range; what matters is covering critical processes.

Who should the risk owner be?

The manager who bears the impact if the risk materializes and has the authority to make the treatment decision; usually the process owner.

For the risk methodology, risk register and SoA work, take a look at our ISO 27001 Risk Analysis, Risk Treatment and SoA service; for organizations without a standards target, our Enterprise Information Security Risk Assessment service.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles