How do we…
How do we set up an ISO 27001 risk assessment and treatment method that stands up to an audit?
Add to board memoOpen the memo
The short answer
- Recommendation
- Approve the scope, then write a short method with criteria, owners and a repeatability test before scoring any risk. Choose controls from the treatments, compare them with Annex A, and have the risk owners approve the plan and accept the residual risk.
- Reasoning
- The auditor tests that the criteria exist, that repeated assessments agree, that each risk has an owner, and that owners approved the treatment and accepted what remains (clauses 6.1.2 and 6.1.3). Scoring before the criteria are fixed means scoring again. A Statement of Applicability written from the Annex A list instead of the treatments has to be rewritten (IS-03). Only the risk owners can accept residual risk, so their approval is part of the method, not an afterthought.
- Considerations
- The standard does not fix one method. The pack's own method writes risks as scenarios and rates them on a four-level scale; any approach your people can repeat will serve.
- A group-wide enterprise risk method can stand as the risk assessment process if it covers information security risk and states the acceptance criteria.
- Controls come from your treatments and from any source. Annex A is the check that nothing needed is missing, so a Statement of Applicability written first from its list has to be rewritten.
- Who may accept a residual risk follows your own rules. At the top that is the board or a committee it has delegated to, the management board in a two-tier structure, or executive management where there is no board.
The decision, step by step
Select any step for the reasoning behind it and where the pack covers it.
- Start
- Step
- Decision
- Outcome
- Loop back
Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.
Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.
Read as text
The same flow written out: each step, its reasoning and where the pack covers it. 21 steps.
Start
We need a risk method for our ISO 27001 risk assessment
The standard asks for a defined risk assessment and a defined risk treatment process, each applied and documented. An auditor tests that the criteria are set, that repeated assessments give consistent results, that each risk has an owner, and that owners approved the treatment and accepted the residual risk. The method has to exist before the first risk is scored.
In the pack
- P08-A02 ISO 27001 Implementation Methodology & Project PlanPhase 2 — Assess risk (5 weeks)
- P05-A02 Risk Assessment Methodology & Scoring ModelHow to defend the method to an auditor
Decision
Has top management approved the ISMS scope?
Every risk depends on what is in scope, so a scope changed after the risk assessment means assessing again. The scope comes first in the plan's order, and top management approves it before the assessment starts. If you are not sure it is approved, answer no.
- Yes: Fix the criteria before anyone scores a risk
- No, or not known: Hold the risk assessment until the scope is approved
In the pack
- P08-A02 ISO 27001 Implementation Methodology & Project PlanSequencing that avoids rework (rule IS-02)
- P08-A02 ISO 27001 Implementation Methodology & Project PlanThe rules (rule IS-01)
Outcome
Hold the risk assessment until the scope is approved
Scoring risks against a scope that may change produces scores that are thrown away. Settle the scope first, then come back to this question.
In the pack
- P08-A02 ISO 27001 Implementation Methodology & Project PlanSequencing that avoids rework
Step
Fix the criteria before anyone scores a risk
Write down how impact and likelihood are rated, with an anchor for each level, and which residual risks may be accepted and by whom. Risks scored before the criteria are fixed are scored again once they are, and the first scores confuse the owners. Where a risk sits between two levels, the pack's method uses the higher.
In the pack
- P08-A02 ISO 27001 Implementation Methodology & Project PlanSequencing that avoids rework (rule IS-03)
- P05-A02 Risk Assessment Methodology & Scoring ModelScales and criteria
- P05-A02 Risk Assessment Methodology & Scoring ModelAppetite, tolerance and position
Decision
Does a risk method you already use cover information security?
A group-wide enterprise risk method can serve as the risk assessment process if it covers information security risk and states the acceptance criteria. A method that only lists risks, or that has no acceptance criteria, does not. If you do not know whether it states them, answer no.
- Yes: Test it against the criteria and add what it lacks
- No, or not known: Write a short method of your own
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents (rule MD-03)
Step
Test it against the criteria and add what it lacks
Check that it sets acceptance criteria you can measure, that its scales work for information security harm such as data loss and service stop, and that it names risk owners. Add the missing parts as a short annex rather than writing a second method. Approve the combined method before any risk is scored.
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents (rule MD-03)
- P05-A02 Risk Assessment Methodology & Scoring ModelScales and criteria
Step
Write a short method of your own
One method of a few pages is enough: the scales and anchors, how a risk is written, who owns it, how it is rated before and after controls, and what each band decides. The pack's method writes each risk as a scenario with a threat, the weakness it uses, the service affected and the consequence. Use any approach your people can repeat.
In the pack
- P05-A02 Risk Assessment Methodology & Scoring ModelThe rules (rules RM-01, RM-03)
- P05-A02 Risk Assessment Methodology & Scoring ModelScales and criteria
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents (rule MD-03)
Decision
Does every risk have one named owner who can accept it?
A risk owner is the executive accountable for the service or asset the risk would hurt, named by role, not a committee or the security team. The owner decides the treatment and signs the acceptance, and may delegate the work but not the decision. The security function owns a risk only where the harm falls on its own duties.
- Yes: Rate each risk, compare it with the criteria and rank it
- No, or not known: Name an owner for each risk and confirm they agree
In the pack
- P05-A02 Risk Assessment Methodology & Scoring ModelEvery risk has one owner (rule RM-02)
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents (rule MD-03)
Step
Name an owner for each risk and confirm they agree
Ask the owner to read the risk and agree it is theirs. An owner who has not seen the risk cannot approve its treatment or accept what remains, and an auditor looks for owners who can say what their risks are. Record the owner by role in the register.
In the pack
- P05-A02 Risk Assessment Methodology & Scoring ModelEvery risk has one owner (rule RM-02)
Step
Rate each risk, compare it with the criteria and rank it
Rate the consequence and the likelihood, before and after existing controls, and read the band from the matrix. Compare each result with the acceptance criteria and put the risks outside them in order for treatment. Record a reason for every rating, so another person can re-derive the result.
In the pack
- P05-A02 Risk Assessment Methodology & Scoring ModelScales and criteria
- P05-A02 Risk Assessment Methodology & Scoring ModelWhat the band decides (rule RM-04)
- P08-A02 ISO 27001 Implementation Methodology & Project PlanPhase 2 — Assess risk (5 weeks)
Decision
Do two assessors reach the same rating on the same risks?
The standard asks that repeating an assessment gives the same answer, so two people rating the same risk should agree. Have two assessors score the same risks independently and compare. A difference of one level on one rating is normal; a difference that changes the band shows an anchor that needs clearer wording. If you have not tested it, answer no.
- Yes: Is any risk above what the criteria let you accept?
- No, or not tested: Tighten the anchors and rate the risks again
In the pack
- P05-A02 Risk Assessment Methodology & Scoring ModelCalibration between assessors
- P05-A02 Risk Assessment Methodology & Scoring ModelHow to defend the method to an auditor
Step
Tighten the anchors and rate the risks again
Change the anchor or add an example in the method itself, not in the assessors' heads, and record the change. Then rate the affected risks again. Repeat the exercise each year.
- Then: Rate each risk, compare it with the criteria and rank it (back to an earlier step)
In the pack
- P05-A02 Risk Assessment Methodology & Scoring ModelCalibration between assessors
- P05-A02 Risk Assessment Methodology & Scoring ModelQuestions auditors commonly ask
Decision
Is any risk above what the criteria let you accept?
A risk within the criteria needs no new treatment decision, though the owner may still reduce it where that is cheap. A risk above them needs a decision on how to treat it. Either way you still decide the controls, because legal and contractual requirements also select them. If a residual rating is not known, treat that risk as above the criteria.
- Yes, or not known: Choose reduce, avoid, transfer or accept for each one
- No, all within the criteria: Decide the controls each treatment needs, from any source
In the pack
- P05-A02 Risk Assessment Methodology & Scoring ModelAppetite, tolerance and position (rule RM-05)
- P05-A02 Risk Assessment Methodology & Scoring ModelTreatment
Step
Choose reduce, avoid, transfer or accept for each one
Reduce changes the likelihood or the impact with controls. Avoid stops the activity. Transfer shares the impact, for example by insurance or contract, and the owner still owns the risk. Accept keeps the residual risk knowingly, recorded and approved at the right level.
In the pack
- P05-A02 Risk Assessment Methodology & Scoring ModelTreatment (rules RM-06, RM-07)
Step
Decide the controls each treatment needs, from any source
Controls come from the treatment you chose, and from any source: your own controls, a customer's requirement or the law. Where no risk is above the criteria, the controls come from those requirements and from what you already run. Choosing from Annex A first produces a checklist that has to be rewritten once the risk work is done.
In the pack
- P08-A02 ISO 27001 Implementation Methodology & Project PlanPhase 3 — Select and document controls (6 weeks) (rule IS-03)
- P08-A04 Statement of Applicability TemplateInstructions (rule IS-03)
Step
Compare the controls with Annex A to catch anything missing
Annex A is the check, not the source. Go through its controls and ask whether any necessary control is missing from your list, and record the comparison. The certification body looks for evidence that the chosen controls were compared with Annex A.
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents (rule MD-04)
- P08-A02 ISO 27001 Implementation Methodology & Project PlanPhase 3 — Select and document controls (6 weeks)
Step
Record every decision in the Statement of Applicability
List all 93 controls, and for each say whether it applies, why, and whether it is implemented. A control that applies is tied to the risks it treats, or to the law or contract that requires it. An exclusion needs a reason that follows from the risk assessment.
In the pack
- P08-A04 Statement of Applicability TemplateInstructions (rule IS-03)
- P08-A04 Statement of Applicability TemplateStatement of Applicability
- P08-A04 Statement of Applicability TemplateWording Guide
Step
Write the treatment plan: action, owner, date, expected residual risk
Each action has an owner, a due date, a cost and the residual score expected when it is done. The plan can be a section of the risk register or the gap tracker, if every action links to a risk and the approval is recorded. The pack drafts this plan during the risk assessment and finishes it once the controls are chosen. Keep it up to date as actions close.
In the pack
- P05-A02 Risk Assessment Methodology & Scoring ModelTreatment (rule RM-07)
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents (rule MD-06)
- P08-A07 ISMS Gap & Remediation TrackerInstructions
Decision
Have the risk owners approved the plan and accepted what remains?
The owners approve the treatment plan and accept the residual risks, and the record shows it. Acceptance is approved at the level the band requires, and outside tolerance only the board or its equivalent may accept. Residual risk not accepted by the risk owners is a gap auditors commonly find. If there is no record, answer no.
- Yes: Method, assessment and plan approved: keep the records
- No, or no record: Take it back to the risk owners for a recorded decision
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents (rules MD-04, MD-06)
- P05-A02 Risk Assessment Methodology & Scoring ModelWhat the band decides (rule RM-08)
Outcome
Take it back to the risk owners for a recorded decision
Put each risk and its plan to its owner, with the residual risk in plain words, and get a signed or minuted decision. Where the criteria send a risk to the top, who decides depends on how you are governed: the board or a committee it has delegated to, the management board in a two-tier structure, or executive management where there is no board.
In the pack
- P05-A02 Risk Assessment Methodology & Scoring ModelWhat the band decides (rule RM-08)
- P08-A04 Statement of Applicability TemplateSoA Approval
Outcome
Method, assessment and plan approved: keep the records
Keep the method, the dated assessment results, the treatment plan, the Statement of Applicability and the owners' acceptance as controlled records. Reassess at the planned interval and after a significant change, and review the Statement of Applicability when the assessment changes. Later results of treatment become records too.
In the pack
- P08-A05 Mandatory ISMS Documentation ChecklistRequired Documents (rules MD-11, MD-12)
- P08-A04 Statement of Applicability TemplateSoA Approval
Practical checklist
- Approve the scope, then fix the criteria: the impact and likelihood scales and the residual risk each level of approver may accept.
- Write the method down: how risks are identified, owned, rated and compared with the criteria.
- Name one owner for every risk, the executive who would answer for the harm.
- Have two assessors rate the same risks, compare the results, and tighten any anchor that gave a different band.
- Rate each risk, compare it with the criteria, and put those above them in order for treatment.
- Choose a treatment for each, decide the controls it needs, and compare them with Annex A to catch gaps.
- Record every decision in the Statement of Applicability and write the treatment plan with owner, date and expected residual risk.
- Take the plan to the risk owners for approval and acceptance of the residual risk, and keep the records.
Evidence to have ready
- The approved risk method, with its criteria and scales, under document control.
- The risk register: dated assessments, each risk's owner and the reason for each rating.
- The record of two assessors rated against each other and of any anchor changed as a result.
- The Statement of Applicability and treatment plan, each tracing its controls to the risks they treat.
- The risk owners' approval of the plan and their acceptance of the residual risk.
Assumptions
- The ISMS scope is approved, or about to be, because every risk is assessed within it.
- You aim to certify against ISO/IEC 27001:2022, or want a method that would stand an audit against it.
- The four-level scales and the treatment options are the CISO Times pack's defaults. Your own method may set different ones.
Not covered here
- Setting the scope the risks are assessed within. That is “How do we set the scope of our ISMS?”.
- Justifying why a single Annex A control is excluded. That is “How do we justify excluding an Annex A control?”.
- Who may accept a particular residual risk. That is “Who can accept a risk, and does the answer change with its rating?”.
- Building a risk register from nothing. That is “How do we build a risk register from nothing?”.
Related questions
- How do we set the scope of our ISMS?
- How do we justify excluding an Annex A control?
- Who can accept a risk, and does the answer change with its rating?
- Do we need a separate register of risks and opportunities for our ISMS itself, apart from our risk register?
- How do we decide what to monitor and measure in our ISMS, and who evaluates it?