logo
language iconarrow
menu icon

ISO/IEC 27005:2018

27005-02 Overview of the process

4 min read · V

All articles

For: V
Source: ISO/IEC 27005:2018(en), English. Clause 6

A high-level view of the risk management process is set out, according to Clause 6, in ISO 31000 and shown in Figure 1. Figure 2 shows how this document applies the process. Both figures are not reproduced here. ISO 31000 stands in the bibliography as “Risk management — Principles and guidelines”, undated, and is not available.

The process consists of establishing the context (Clause 7), the risk assessment (Clause 8), the risk treatment (Clause 9), the risk acceptance (Clause 10), risk communication and consultation (Clause 11), and monitoring and review (Clause 12).

Figure 2 illustrates that the process for assessment and treatment can be iterative. An iteration can increase the depth and detail of the assessment at each pass. It is to provide a balance between low effort in identifying controls and an adequate assessment of high risks. “Provides a good balance” describes the figure, not a mandatory number of passes.

First the context is established. Then a risk assessment is carried out. If it provides enough information to determine the actions by which the risks are modified to an acceptable level, this task is complete and the treatment follows. If the information is not sufficient, a further iteration is carried out with a revised context, for example with other evaluation criteria, acceptance criteria or impact criteria, possibly only for parts of the scope. The text calls this risk decision point 1.

The effectiveness of the treatment depends on the results of the assessment. Treatment is a cycle: assess a treatment; decide whether the residual risk levels are acceptable; generate a new treatment if the levels are not acceptable; assess the effectiveness of this treatment.

It is possible that the treatment does not immediately lead to an acceptable residual risk. Then a further iteration of the assessment with changed context parameters can be needed, followed by further treatment. The text calls this risk decision point 2. “Can be required”.

On risk acceptance, Clause 6 says the activity has to ensure that residual risks are expressly accepted by the managers of the organization. The English wording is “has to ensure”. This applies in particular when the implementation of controls is omitted or postponed, for example because of cost. The document's own description of acceptance stands in Clause 10, see 27005-07. The sentence names “managers of the organization”. It does not name the risk owners from ISO/IEC 27001:2022.

Throughout the process it is important that risks and their treatment are communicated to the responsible managers and to operational personnel. Even before treatment, information on identified risks can be valuable for handling incidents and can reduce possible harm. Awareness among management and personnel of the risks, of the nature of the controls in place and of the organization's concerns helps in dealing with incidents and unexpected events. The detailed results of each activity and of the two decision points should be documented. “Should”.

According to this clause, ISO/IEC 27001 specifies that the controls implemented in the scope, within the boundaries and in the context of the ISMS need to be risk-based. The English wording is “need to be risk-based”. That is the summary of the guidance, not a “shall” of this PDF. Applying an information security risk management process can fulfil this requirement. There are many approaches by which controls can be determined in order to implement the chosen treatment options. The clause cites ISO/IEC 27001 without a year of edition. It does not reproduce the wording of ISO/IEC 27001:2022, 6.1.2 and 6.1.3.

The organization should establish, implement and maintain a process in order to identify the legal requirements that are applicable to: the selection of the criteria for evaluation (7.2.2), impact (7.2.3) and acceptance (7.2.4); the establishment of scope and boundaries (7.3 and A.2); the risk evaluation (8.4); the treatment (9.1) and the implementation of plans for risk reduction (9.2 and Annex F); monitoring, review and improvement (12.2); identification of assets (B.1.3) and their valuation (B.2.3); risk estimation, examples in E.2.1. This is a recommendation of the guidance. The clause names no particular law.

Not in this text: the figures, the content of ISO 31000, and a list of laws. The individual activities follow in the next articles.