Skip to main content
ISO 27001

ISO 27001 Risk Assessment: Step by Step with Examples

Published
Last updated
ISO 27001
A colour-coded risk heat map under a magnifying glass beside a clipboard risk register and a shield with a check mark, representing an ISO 27001 risk assessment

The risk assessment is the engine of an ISO 27001 information security management system (ISMS). It decides which Annex A controls you need, what goes into your Statement of Applicability and where your team spends its effort. This guide walks through a method that holds up at audit, with generic examples you can adapt. For hands-on help, see our ISO 27001 consulting page.

The examples below are illustrations, not templates to copy word for word. Auditors look for a method that fits your organisation and is applied the same way every time.

What does ISO 27001 require for risk assessment?

ISO 27001 requires a defined information security risk assessment process (clause 6.1.2) and a risk treatment process (clause 6.1.3). You must set criteria for accepting risk, identify risks to the confidentiality, integrity and availability of information, name a risk owner for each, analyse and evaluate them, and keep documented results.

The standard also asks you to perform the assessment at planned intervals and when significant changes are proposed or happen (clause 8.2), and to carry out the treatment plan (clause 8.3). It does not prescribe a method, a scoring scale or a tool. That freedom is useful, but it means the auditor judges your method by the standard's own test: repeated assessments must produce consistent, valid and comparable results.

Should you use an asset-based or scenario-based approach?

Either works. The 2022 edition does not require you to start from an asset list, so you can identify risks from assets, from threat scenarios or from business processes. Choose the approach your team can repeat consistently. Many organisations combine them: an asset inventory for coverage, and scenarios to describe what could actually go wrong.

  • Asset-based: list information and supporting assets (customer database, source code, laptops, a payroll system), then ask what threats and weaknesses apply to each. It gives good coverage but can produce long, repetitive registers.
  • Scenario-based: describe events, such as "customer data exposed through a misconfigured cloud storage bucket", and assess each one. Registers are shorter and easier for managers to understand, but you need a way to check nothing important is missed.

Whichever you pick, you still need an inventory of information and other associated assets, because Annex A control 5.9 asks for one.

Step-by-step ISO 27001 risk assessment

Step 1: Write the methodology and acceptance criteria

Document how you identify, score and evaluate risks, who does it, and how often. Set your risk acceptance criteria: which score a risk owner can accept, and which must be treated. Get top management to approve it, because every later decision depends on it.

Step 2: Identify risks

Run short workshops with the people who know each area: engineering, IT, HR, finance, operations. Use your asset inventory or scenario list as prompts. Record each risk as a clear sentence with a cause and a consequence, so it can be scored.

Step 3: Assign a risk owner to each risk

Name the person with the authority to decide how the risk is treated. That is usually a department or business head, not the security team.

Step 4: Analyse likelihood and impact

Score each risk on the scales in your methodology. A simple example:

ScoreLikelihoodImpact
1RareNegligible
2UnlikelyMinor
3PossibleModerate
4LikelyMajor
5Almost certainSevere

Multiply likelihood by impact to get a score from 1 to 25. Describe what each impact level means for your business, such as customer harm, legal exposure or downtime, so two people scoring the same risk land on the same number.

Step 5: Evaluate and prioritise

Compare each score with your acceptance criteria. As an example, you might treat anything scoring 12 or more, and let risk owners accept anything lower with a recorded reason. Set your own thresholds; these are only illustrations.

Step 6: Choose a treatment and controls

Decide how to treat each risk and which controls do it. Compare your chosen controls with all 93 Annex A controls, so nothing necessary is missed.

Step 7: Build the treatment plan and update the Statement of Applicability

The treatment plan lists each action, its owner and due date. The Statement of Applicability records, for every Annex A control, whether it applies, why, and whether it is implemented. See our Annex A controls list and SoA guide.

Step 8: Review and repeat

Reassess at your planned interval and whenever something significant changes, such as a new product, a new major supplier or a move to another cloud platform.

Example risk register rows

These rows are fictional and generic. They show the level of detail auditors expect, not risks you must copy.

IDRiskOwnerLIScoreTreatmentExample controls
R-01A laptop holding customer data is lost or stolenIT manager3412Modify8.1 User endpoint devices; 8.24 Use of cryptography
R-02A former employee keeps access to SaaS toolsHead of HR3412Modify5.18 Access rights; 6.5 Responsibilities after termination or change of employment
R-03Cloud storage is misconfigured and exposedHead of engineering2510Modify8.9 Configuration management; 5.23 Information security for use of cloud services
R-04A key supplier is unavailable for a weekHead of operations236Retain5.22 Monitoring, review and change management of supplier services
R-05A phishing email leads to account takeoverSecurity lead4416Modify6.3 Information security awareness, education and training; 8.5 Secure authentication
R-06An unsupported legacy application is exploitedCTO248AvoidRetire the application

What are the four risk treatment options?

ISO 27001 lets you treat each risk in one of four ways: modify it by adding or improving controls, retain it when it falls within your acceptance criteria, avoid it by stopping the activity that causes it, or share it, for example through insurance or a contract. The risk owner approves the choice and the remaining risk.

Most risks end up as "modify". "Retain" is fine when it is a deliberate, recorded decision by the right person. "Share" does not remove accountability: if a supplier holds your data, you still need controls over that supplier.

Who should be the risk owner?

A risk owner is the person with the authority and accountability to manage a risk, usually a business or department head rather than the security team. Risk owners approve the treatment plan and formally accept the residual risk, which clause 6.1.3 requires. Control owners then run the chosen controls day to day.

Mixing the two roles up is a common audit finding. Read risk owner vs control owner for how the roles divide in practice.

What records do auditors expect?

Auditors expect your documented methodology and acceptance criteria, the risk register with results, the risk treatment plan, the Statement of Applicability, and evidence that risk owners approved the plan and accepted residual risk. They also check that you repeated the assessment at your planned interval and after significant changes.

In practice, keep:

  • the approved methodology, with version and date
  • the risk register, showing scores before and after treatment
  • the treatment plan, with owners, due dates and status
  • the Statement of Applicability, linked to the risks it addresses
  • sign-offs from risk owners, by email or in a tool
  • notes from reassessments, including what triggered them

Common mistakes that cause findings

  • A methodology that exists on paper but is not what the team actually did.
  • Scores with no definitions, so two people rate the same risk differently.
  • The security lead listed as owner of every risk.
  • Residual risk never formally accepted by anyone.
  • Annex A controls excluded in the Statement of Applicability with no link to the risk assessment.
  • No reassessment after a major change, such as a new product or cloud migration.

How CyberWave GRC helps

We write the methodology with you, run the first workshops, and set up a register your team can keep up to date. We then connect it to your Statement of Applicability, internal audit and management review, so the whole ISMS tells one consistent story. Our ISO 27001 work is a fixed fee, end to end, including the audit, quoted after a free scoping call. An accredited certification body performs Stage 1 and Stage 2 and issues the certificate; we never issue certificates ourselves.

Next, read how to plan your ISO 27001 internal audit, which tests whether your risk process works as written.

Frequently asked questions

ISO 27001 requires you to repeat the risk assessment at planned intervals and whenever significant changes are proposed or happen, such as a new product, a major new supplier or a move to another cloud platform. Most organisations set an annual review and record what triggered any reassessment carried out between reviews.

No. ISO 27001 does not require a tool. A well-structured spreadsheet is enough for many organisations, as long as the method is documented and applied consistently. Software helps when you have many risks, owners or sites, but the auditor checks your method and records, not the tool you used to produce them.

Yes, if the exclusion is justified. Your risk assessment and scope decide which Annex A controls you need, and the Statement of Applicability records each one as included or excluded with a reason. Auditors check that exclusions match reality, so a control excluded because you have no such systems must reflect your actual environment.

Inherent risk is the level of a risk before the controls you are planning are applied, and residual risk is what remains after treatment. ISO 27001 asks risk owners to approve the treatment plan and accept the residual risk, so your register should show both levels and who accepted the risk that remains.
Hi! I'm your AI Assistant 💬