What ISO 27001 requires
Risk appears in several clauses, each with a different job. In short:
| Clause | What it asks for |
|---|---|
| 6.1.1 | Risks and opportunities for the ISMS itself, drawn from your context and interested parties. A short list, separate from your information security risks |
| 6.1.2 | A defined risk assessment process with acceptance criteria, producing consistent, valid and comparable results; risks identified, owned, analysed and evaluated |
| 6.1.3 | Treatment options chosen, controls determined and compared with Annex A, a Statement of Applicability and a risk treatment plan approved by risk owners |
| 8.2 and 8.3 | The assessment repeated at planned intervals and on significant change, and the treatment plan carried out, with results kept as records |
The method and processes are documents; the results are records. See ISO 27001 clauses 4 to 10 explained for the surrounding requirements.
Step 1: Define your method
Write down how you'll score risks (for example likelihood and impact on a 1–5 scale), what level of risk is acceptable, and who can accept residual risk. Clause 6.1.2 requires repeated assessments to give consistent, valid and comparable results, so keep it simple enough that two people would score the same risk the same way.
Choose an approach
| Approach | How it works | Suits |
|---|---|---|
| Scenario-based | Start from things that could happen, such as “a supplier with access to customer data is breached” | Most SMEs; quick to run and easy for leaders to understand |
| Asset-based | List information assets, then the threats and vulnerabilities for each | Larger or more complex estates; ties neatly to the asset inventory |
| Hybrid | Scenarios, checked against the asset inventory so nothing in scope is missed | Teams that want speed without gaps |
Define the scales
Each point on a scale needs a description, or scoring turns into guesswork. Impact should cover more than money: customers, legal and regulatory exposure, operations and reputation. An example impact scale for an Australian SME:
| Score | Impact | Looks like |
|---|---|---|
| 1 | Negligible | Internal inconvenience, no customer or legal effect |
| 2 | Minor | Short disruption to one team; no personal information involved |
| 3 | Moderate | Customer-visible outage of hours; a contract obligation breached |
| 4 | Major | A notifiable data breach to the OAIC; loss of a key customer; days of disruption |
| 5 | Severe | Large-scale breach of sensitive personal information; threat to the viability of the business |
Likelihood works the same way, from “not expected in the next few years” to “expected more than once this year”. Then set the acceptance criteria: for example, scores up to 6 can be accepted by the risk owner, 8 to 12 need treatment or a documented decision by leadership, and 15 or above must be treated.
Step 2: Identify risks
Work through what could affect the confidentiality, integrity or availability of information in scope. Good prompts:
- Your key systems and data: customer data, source code, finance, credentials
- Your people: joiners, leavers, privileged admins, contractors
- Your suppliers: cloud hosting, SaaS tools, outsourced IT
- Threats you see in your sector: phishing, ransomware, business email compromise, misconfigured cloud storage
- Your obligations: Privacy Act duties, customer contract terms, tender requirements
- What went wrong before: incidents, near misses, audit findings and gap analysis results
A facilitated workshop of two to three hours with the right people usually surfaces most of the register. Write each risk as a cause and a consequence (“a phishing email leads to a compromised mailbox and fraudulent invoices”), not a single word like “phishing”.
Step 3: Assign owners
Every risk needs an owner who has the authority to decide on it, usually a department head rather than the IT team. Auditors check that owners know their risks and have approved the treatment.
Step 4: Analyse and evaluate
Score each risk for likelihood and impact, taking into account the controls you already have. Base the likelihood on something real where you can: incidents you've had, what suppliers report, threat information from the ASD. Then compare the score with your acceptance criteria and decide whether the risk needs treating.
| Risk | Likelihood | Impact | Score | Decision |
|---|---|---|---|---|
| Phishing leads to a compromised mailbox | 4 | 4 | 16 | Treat |
| Main cloud region outage | 2 | 4 | 8 | Treat (backups, recovery plan) |
| Theft of an encrypted laptop | 3 | 1 | 3 | Accept |
- A Phishing leads to a compromised mailboxScore 16: treat
- B Main cloud region outageScore 8: treat
- C Theft of an encrypted laptopScore 3: accept
- High Treat Monitor Accept
After treatment, score each risk again. The difference between the current score and the target residual score shows leadership what the treatment buys, and the residual score is what the risk owner formally accepts.
Step 5: Choose treatments
For each risk above your threshold, choose to modify it (add controls), avoid it (stop the activity), share it (insurance or a supplier) or retain it (accept it with a reason). Compare the controls you choose against Annex A so nothing necessary is missed, and use ISO/IEC 27002 for guidance on implementing them (see ISO 27001 vs ISO 27002).
| Option | Example | Keep in mind |
|---|---|---|
| Modify | Enforce phishing-resistant MFA and payment verification calls for the mailbox risk | The most common choice; each control should name the risk it treats |
| Avoid | Stop storing full card or identity document details you don't need | Often the cheapest fix for privacy risks |
| Share | Cyber insurance; a managed provider running backups under contract | Accountability stays with you; Notifiable Data Breaches obligations don't move to the insurer or supplier |
| Retain | Accept the encrypted laptop theft risk | Needs a reason and the risk owner's recorded acceptance |
Step 6: Produce the outputs
- Risk register: every risk with its owner, score and decision
- Risk treatment plan: actions, owners and dates
- Statement of Applicability: the controls that result
- Owner sign-off on the plan and on any residual risk
The assessment and treatment results are required records; see ISO 27001 required documents for the full list. Each action in the treatment plan should name the control it implements, and each included control in the SoA should cite the risks it treats, so an auditor can follow the line either way.
A worked example: one risk, end to end
Take a 30-person Melbourne software company whose finance team pays suppliers by email invoice.
- Risk: a phishing email compromises a finance mailbox, and an attacker changes a supplier's bank details on a genuine invoice thread. Owner: the finance manager.
- Current controls: MFA by app push on all accounts, annual awareness training.
- Analysis: business email compromise is a common attack on Australian businesses, and the team has seen attempts, so likelihood 4. A fraudulent payment plus exposure of customer and staff details in the mailbox, so impact 4. Score 16: above the threshold, must be treated.
- Treatment: modify. Phishing-resistant MFA for finance and admins, a call-back rule for any change to bank details, mailbox forwarding alerts and phishing simulations. These map to Annex A controls 5.14, 6.3, 8.5 and 8.16.
- Residual: likelihood 2, impact 4, score 8. The finance manager accepts it and signs the treatment plan; leadership notes the decision.
That one row now links a risk, an owner, four controls, a treatment action with dates and a recorded acceptance. Multiply it by twenty or thirty and you have an assessment an auditor can follow.
Keeping it current
Clause 8.2 requires the assessment to be repeated at planned intervals and when significant changes happen. Most SMEs do a full review once a year, before the management review, and a targeted review when something changes: a new product or market, a key supplier, an acquisition, a significant incident, a move to new infrastructure or a change in law. Record each review, even when the conclusion is that nothing changed. The register then feeds your surveillance audits, where auditors look for evidence that it's still alive.
What auditors check
- A documented method someone else could follow, with defined scales and acceptance criteria
- Risks that reflect your actual business, systems and suppliers, not a generic library
- Owners with authority who can explain their risks and treatments in interview
- A clear line from risk to treatment to control to SoA
- Recorded approval of the treatment plan and acceptance of residual risk
- Dated results, including reviews after significant change
Common pitfalls
- A 400-line spreadsheet nobody reads. Fifteen to forty well-described risks is typical for an SME.
- Scoring everything “medium”.
- IT owning every risk.
- Never revisiting the register after certification.
- Starting from Annex A and writing a “risk” for each control, which reverses the logic auditors want to see.
- Scales without descriptions, so scores change depending on who's in the room.
- Treatment actions with no owner or date, which can't be shown as carried out under clause 8.3.
We facilitate the risk workshop as part of every ISO 27001 implementation, and the same register supports ISO 42001 AI risks when you add them. For where risk fits in the whole project, see how to implement ISO 27001. To talk through your risks, book a free 30-minute consultation.
