ISO/IEC 27005
ISO27k-aligned security awareness service

ISO/IEC 27005:2011 Information technology — Security techniques — Information security risk management  (second edition) Status update Feb

Introduction

The ISO27k standards are deliberately risk-aligned, meaning that organizations are encouraged to assess the security risks to their information as a prelude to treating them in various ways. Dealing with the highest risks first makes sense from the practical implementation and management perspectives.

Scope of the standard

The standard ‘provides guidelines for information security risk management’ and ‘supports the general concepts specified in ISO/IEC 27001 and is designed to assist the satisfactory implementation of information security based on a risk management approach.’

It cites ISO/IEC 27000 and the 2005 version of ISO/IEC 27001 as normative (essential) standards, and also mentions ISO/IEC 27002 in the scope section.

Noted in Dec 2015 The next version may be broader in scope than merely addressing the risk management requirements identified in ISO/IEC 27001 ... but changing scope was not a stated objective of the revision project.

Content of the standard

At around 70 pages, ISO/IEC 27005 is a heavyweight standard although the main part is just 26 pages, the rest being mostly annexes with examples and further information for users.

The standard doesn't specify, recommend or even name any specific risk management method. It does however imply a continual process consisting of a structured sequence of activities, some of which are iterative:

  • Establish the risk management context (e.g. the scope, compliance obligations, approaches/methods to be used and relevant policies and criteria such as the organization’s risk tolerance or appetite);
  • Quantitatively or qualitatively assess (i.e. identify, analyze and evaluate) relevant risks, taking into account the information assets, threats, existing controls and vulnerabilities to determine the likelihood of incidents or incident scenarios, and the predicted business consequences if they were to occur, to determine a ‘level of risk’;
  • Treat (i.e. modify [use information security controls], retain [accept], avoid and/or share [with third parties]) the risks appropriately, using those ‘levels of risk’ to prioritize them;
  • Keep stakeholders informed throughout the process; and
  • Monitor and review risks, risk treatments, obligations and criteria on an ongoing basis, identifying and responding appropriately to significant changes.

Extensive appendices provide additional information, primarily examples to demonstrate the recommended approach.

Status of the standard

The second edition of ISO/IEC 27005 was published in 2011. It reflects the general corporate or enterprise-wide risk management standard ISO 31000:2009 “Risk management - Principles and guidelines” in the specific context of risks to or involving information.

Feb status update A project to revise the standard is in progress, re-aligning ISO/IEC 27003, 27004 and 27005 with the 2013 versions of ISO/IEC 27001 and 27002, plus the latest version of ISO 31000.  If the revision project succeeds (which is not certain), the next version of 27005 will be substantially different. WD5 is nearly 100 pages long (half main body, half annexes) making this a meaty standard offering stacks of advice e.g. noting that information risks can be analyzed by asset-threat-vulnerability, scenario-based/event-driven, quantitative and/or qualitative approaches.  The 3rd edition is now at CD stage, although several national bodies do not consider it stable enough or ready for CD as yet and some raised concerns that the project has lost sight of its original goal (it was only supposed to be updating the standard for ISO/IEC 27001:2013).  It is possible that the revision project may be cancelled and re-started.

[A study period looking into cloud computing security risks wanted an annex to 27005 but, given the extent of changes already in progress, that looks unlikely.  About 5 pages of comments have already been ruled out-of-scope of the 27005 revision project but may be addressed by the study period on ‘information risks and opportunities’.]

Further reading

Read more about selecting suitable information security risk analysis methods and tools in the ISO27k FAQ.

Personal comments

A color-coded two-dimensional graphic remarkably similar to the one I described as an “Analog Risk Assessment” (ARA) metric was at one point proposed for inclusion in the standard but, unfortunately, reverted to typical risk matrix with a mathematical calculation based on adding ordinal numbers assigned to levels of likelihood and consequence.  However, simple arithmetic is inappropriate for ordinals, making this approach technically invalid (although commonplace).  Furthermore, cells in the body of the risk matrix are colored red for unacceptable or uncolored for acceptable, totally ignoring wide variations in each category. In fact I find the very concept of categorizing likelihoods, consequences, risks and acceptability unnecessary and unhelpful, compared to simply ranking them relative to each other on continuous scales.  Risks don’t fit into neat little boxes.

Copyright © 2016 IsecT Ltd.