ISO 27001 risk assessment step by step is the heart of the standard, and it is where many first-time projects stall. The idea is simple: find what could go wrong with your information, decide how serious each risk is, and choose sensible actions. The difficulty is doing it in a way that is clear, repeatable and useful, not a spreadsheet nobody reads.
ISO/IEC 27001:2022 requires you to define and apply an information security risk assessment process, and to keep records of the results. The standard does not force one method. It asks that your method produces consistent, comparable results, and that risk owners approve the treatment. This guide gives a practical path that works for most organisations.
What is the ISO 27001 risk assessment step by step?#
- Define the method and criteria. Decide how you will rate likelihood and impact, what scale you will use and what level of risk you accept.
- Set the scope. Use the scope of your ISMS, so the assessment covers the same people, systems and sites.
- List your assets. Include information, applications, hardware, people, suppliers and services that matter. Give each an owner.
- Identify risks. For each asset, ask what could go wrong, such as loss, leak, change or unavailability, and why it could happen.
- Analyse the risks. Rate the likelihood and the impact using your scale, and work out a risk level.
- Evaluate the risks. Compare each level with your acceptance criteria, and rank the risks that need action.
- Choose treatments. For each unacceptable risk, decide to reduce it, avoid it, share it or accept it.
- Select controls. Choose the controls that carry out the treatment, and compare them with Annex A so none is missed.
- Write the risk treatment plan. Record the actions, owners and dates.
- Get approval. Risk owners approve the plan and accept any residual risk.
Do the early steps with the people who know the business. A workshop with team leads usually finds more real risks in a morning than one person finds alone in a week. Ask them what keeps them awake, what has failed before and which systems they could not work without. Their answers are the raw material of a useful register.
How do you rate likelihood and impact?#
Keep the scale simple. Many organisations use three or five levels for each factor, with short descriptions so different people rate in the same way. For impact, describe consequences in business terms, such as service stopped for a defined time, customer data exposed or a contract breached. For likelihood, describe how often you expect the event, using the history of your own industry and your own incidents.
| Level | Likelihood example | Impact example |
|---|---|---|
| Low | Unlikely in the coming year | Minor disruption, no customer effect |
| Medium | Could happen in the coming year | Noticeable disruption or limited data exposure |
| High | Likely in the coming year | Serious outage, major data exposure or contract breach |
Multiply or combine the two ratings using a simple matrix, and define which results are acceptable. The exact scale matters less than using it the same way every time and explaining it to those who must follow it.
Worked example: a company stores customer files on a cloud drive. The risk is that a staff account is taken over and files are copied. Likelihood is medium, because phishing is common, and impact is high, because customer data is exposed. The treatment is to reduce the risk with multi-factor sign-in, access reviews and logging. The residual risk is then lower, and the owner records acceptance.
What should the risk register and treatment plan contain?#
- The asset, the risk description and the risk owner.
- The likelihood, impact and resulting risk level before treatment.
- The chosen treatment and the controls selected.
- The actions, responsible person and target date.
- The residual risk after treatment, and who accepted it.
The risk treatment plan feeds the Statement of Applicability. Every control you include there should trace back to a risk, a legal duty or a contract. If you cannot trace it, ask why you have it.
Remember that treatment is a choice. You can reduce a risk with controls, avoid it by stopping the activity, share it through insurance or a contract, or accept it knowingly. Acceptance is legitimate if the owner agrees and the reason is recorded, but it is not a way to skip hard work.
Which mistakes do auditors find most often?#
- A generic risk list copied from a template with no link to the real business.
- Assets without owners, so nobody accepts the risk.
- A rating method that nobody can explain or reproduce.
- No review after incidents, new systems or supplier changes.
- A treatment plan with no dates or owners.
- Controls in the Statement of Applicability that do not match the risk results.
Keep the assessment alive. Review it at planned intervals and after significant change, such as a new cloud service, a new office or a major supplier. Link it to incidents and audit findings, so the register reflects real experience.
Templates help you start. Our ISO 27001 toolkit offers an editable risk assessment template and other documents, with one year of e-mail support and a free upgrade within 6 months. Adapt the method and the examples to your own business. If you want guided help, see our ISO 27001 consulting in India. No one can promise an audit result, because the certification body decides.
Finally, keep the output readable. A short summary for management, showing the top risks, their treatment and progress, is more useful at a management review than a long spreadsheet. Auditors like it too, because it shows that the results are used to make decisions.
Frequently asked questions#
Do we have to use a particular risk method?#
No. The standard asks for a defined process that gives consistent, comparable results. Choose a method that fits your size and explain it in writing.
Should we assess assets or scenarios?#
Either can work. Many organisations assess risks against assets, and some use scenarios. What matters is that the method is clear and covers confidentiality, integrity and availability.
How often should we repeat the assessment?#
At planned intervals, and when there are significant changes. Many organisations review it at least once a year, for example before the management review.
For the wider picture read our complete guide to ISO 27001 or contact AdWiser for help.

Leave a Comment