Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is ISO/IEC 27005?

ISO/IEC 27005 is the guidance standard for managing information security risk, describing how to identify, analyse, evaluate, and treat risk within an ISO 27001 management system.

Illustration for the cybersecurity term ISO/IEC 27005
Home / Blog / Cybersecurity Terms / What Is ISO/IEC 27005?
17 November 2026

What Is ISO/IEC 27005?

What Is ISO/IEC 27005?

ISO 27001 tells you that you must assess information security risk, define criteria, and treat the results. It does not tell you how. ISO/IEC 27005 fills that gap: it is the guidance standard describing a workable process for information security risk management, updated most recently in 2022 to align with ISO 31000 and the restructured control set.

It is guidance, not requirements. You cannot be certified against it, and ISO 27001 does not mandate its use. What it offers is a defensible method, which matters because a risk assessment that cannot be explained to an auditor is a liability rather than an asset.

The Process

The standard follows the ISO 31000 structure applied to information security.

  1. Context establishment. Define the scope, the organisational context, and the risk criteria. Criteria cover how impact and likelihood will be expressed, how risk levels are derived, and at what level risk may be accepted and by whom. Getting this wrong at the start poisons everything after it.
  2. Risk identification. Find the risks. The 2022 edition explicitly supports two approaches, discussed below.
  3. Risk analysis. Determine consequence and likelihood, and derive a risk level. The standard accommodates qualitative, semi-quantitative, and quantitative methods.
  4. Risk evaluation. Compare results against criteria, decide which risks require treatment, and prioritise them.
  5. Risk treatment. Choose from four options: modify the risk by applying controls, retain it by informed acceptance, avoid it by not doing the activity, or share it through insurance or contract. Record the resulting residual risk and obtain the risk owner’s acceptance.
  6. Communication and monitoring. Keep stakeholders informed, and review as the context changes.

The output feeds directly into the Statement of Applicability, which is the point at which many organisations realise their risk assessment and their control set were produced independently of each other.

Event-Based and Asset-Based Identification

The most practically useful change in the 2022 edition is the explicit recognition of two identification approaches.

Asset-based identification starts from an inventory: for each asset, consider threats, vulnerabilities, and consequences. It is thorough, maps neatly to control selection, and is how most organisations were taught to do it. Its weakness is scale. An estate of 4,000 assets produces an unmanageable register, and teams end up assessing asset classes while pretending to assess assets.

Event-based identification starts from scenarios: what could happen, to which part of the business, and with what consequence. Ransomware encrypting the production environment, a supplier breach exposing client data, a privileged insider exfiltrating source code. It produces a shorter, more comprehensible register that executives can engage with, and it aligns naturally with threat modelling and MITRE ATT&CK techniques.

Most mature programmes use both: event-based scenarios for the top-level register reported to the board, asset-based analysis where detailed control selection is required, such as for a specific platform or a regulated system.

Qualitative and Quantitative Methods

Qualitative scoring, typically a five-point scale for impact and likelihood multiplied into a risk level, is what most organisations run. It is quick, it is comparable within one organisation, and it is unreliable across organisations because the scales are arbitrary.

Quantitative methods express risk in money and frequency, as FAIR does. They are harder, require data most organisations have not collected, and produce outputs that finance directors take seriously. ISO/IEC 27005 does not prescribe either, which is appropriate: the right choice depends on the decisions the output has to support.

Whatever method is chosen, the two requirements that matter are consistency and repeatability. Two assessors examining the same risk should reach a similar result, and the standard’s emphasis on documented criteria is what makes that achievable.

Using It in a UK Context

ISO/IEC 27005 fits alongside UK references rather than competing with them. The NCSC’s risk management guidance is sceptical of matrix scoring used mechanically and emphasises making risk decisions explainable, which complements the standard’s insistence on documented criteria. UK GDPR data protection impact assessments are a different exercise with a different subject — risk to individuals rather than to the organisation — but can share method and evidence.

Other useful references include NIST SP 800-30 for a detailed assessment methodology, and ISO 31000 for the enterprise risk framework into which information security risk should feed rather than sitting apart from it.

The Practical Test

A risk management process is working when it changes decisions. If the register is reviewed quarterly and every risk retains the same score and the same treatment plan, the process is recording opinions rather than managing risk. If risk owners can describe their risks without the register in front of them, and if a treatment decision has recently been made because of the assessment, it is working.

Technical testing supplies the evidence that makes likelihood estimates something other than guesswork. Our cyber risk analysis services help organisations connect the register to what is genuinely exploitable in their environment.

FAQ – Frequently Asked Questions

Is ISO/IEC 27005 Mandatory for ISO 27001 Certification?

No. ISO 27001 clause 6.1.2 requires a defined information security risk assessment process with documented criteria, but does not specify which methodology. ISO/IEC 27005 provides one recognised approach, and auditors are familiar with it. Other methods are acceptable provided they are documented, consistent, repeatable, and demonstrably drive the selection of controls.

Should We Use an Asset-Based or Event-Based Approach?

Event-based scenario identification produces a shorter register that executives engage with and suits board-level reporting. Asset-based identification is more thorough and maps directly to control selection for specific systems. Many organisations use event-based analysis for the top-level register and asset-based analysis where detailed control decisions or regulatory evidence are required.

What Are the Four Risk Treatment Options?

Modify the risk by applying or improving controls; retain it through informed acceptance by the risk owner; avoid it by not undertaking the activity that creates it; or share it through insurance, contract, or outsourcing. Sharing transfers financial consequence but rarely transfers accountability, which remains with the organisation under regulations such as UK GDPR.

How Often Should Risk Assessments Be Reviewed?

ISO 27001 requires assessment at planned intervals and when significant changes occur. Annual full review with quarterly register updates is common practice, supplemented by assessment of material changes: a new product, a major supplier, an acquisition, or a significant incident. A register that has not changed between reviews usually indicates the process is not being applied.

Related Terms

You May Be Interested In These

What Is Identity and Access Management (IAM)?

Cybersecurity Terms

17 November 2026

What Is Identity and Access Management (IAM)?

Read More
What Is an Indicator of Compromise (IoC)?

Cybersecurity Terms

17 November 2026

What Is an Indicator of Compromise (IoC)?

Read More
What Is Security Telemetry?

Cybersecurity Terms

17 November 2026

What Is Security Telemetry?

Read More