logo
language iconarrow
menu icon

ISO/IEC 27005:2018

27005-07 Risk treatment and risk acceptance

8 min read · V, IA

All articles

For: V, IA
Source: ISO/IEC 27005:2018(en), English. Clause 9, Clause 10, Annex F informative

9.1 takes the prioritized list. The action: controls to reduce, retain, avoid or share the risks should be selected and a treatment plan established. Four options are available: risk modification (9.2), risk retention (9.3), risk avoidance (9.4) and risk sharing (9.5). Figure 3 is not reproduced.

The options should be selected according to the result of the assessment, the expected cost of implementation and the expected benefit. Where large reductions are achievable with relatively little effort, such options should be implemented. Further improvements can be uneconomic. Then judgement needs to be exercised on whether they are justified. “Judgement needs to be exercised”. In general the adverse consequences should be made as low as reasonably practicable, independently of absolute criteria. The English wording is “as low as reasonably practicable”. That is a recommendation of the implementation guidance, not a legal benchmark and not a performance target of this PDF. Managers should bear in mind rare but severe risks. Then it can be necessary to implement controls that are not justified on purely economic grounds, for example business continuity controls for certain high risks.

The four options are not mutually exclusive. A combination can increase the benefit, for instance lowering the likelihood, lowering the consequences and sharing or retaining residual risks. Some treatments can address more than one risk effectively, for example training and awareness. A treatment plan should be established that clearly shows the order in which the individual treatments should be implemented, and their time limits. Priorities can be set with various techniques, including ranking and cost-benefit analysis. It lies in the responsibility of the managers of the organization to decide the balance between the cost of the controls and the allocation of the budget.

The identification of existing controls can show that they exceed the current need, in the cost comparison including maintenance. If removal of surplus or unnecessary controls is considered, especially where maintenance costs are high, information security and cost should be taken into account. Because controls can influence one another, removal can reduce the existing security overall. It can be cheaper to leave them in place.

The options should be considered with a view to how those affected perceive the risk and how best to communicate with them. The risk for organizations is the failure to meet requirements, and treatment options that limit this possibility should be implemented. All constraints, organizational, technical, structural, that were recognized in the context should be taken into account in the treatment.

Once the plan is established, the residual risks need to be determined. The English wording is “need to be determined”, not “shall”. This includes an update or a further iteration of the assessment under the expected effects of the proposed treatment. If the residual risk does not yet meet the acceptance criteria, a further iteration of the treatment can be needed before acceptance follows. Output: treatment plan and residual risks that are subject to the acceptance decision of the managers.

9.2 Risk modification. The level of risk should be managed by introducing, removing or changing controls, so that the residual risk can be reassessed as acceptable. Suitable and justified controls should be selected in order to meet the requirements identified by the assessment and the treatment. The selection should also take into account cost and time limit, or technical, environmental and cultural aspects. Often it is possible to lower the total cost of ownership of a system with correctly selected controls. Controls can provide one or more of these kinds of protection: correction, elimination, prevention, reduction of impact, deterrence, detection, recovery, monitoring and awareness. In the selection it is important to weigh the cost of acquisition, implementation, administration, operation, monitoring and maintenance against the value of the assets protected. The return in the form of risk reduction and the possibility of using certain controls to take new business opportunities should be taken into account. In addition, particular skills that can be needed in order to specify and implement new controls or to change existing ones should be borne in mind. According to this paragraph, ISO/IEC 27002 provides detailed information on controls. That edition is not available here as the subject of the article. The German edition of 2017 is not drawn on.

Many constraints can influence the selection. Technical constraints such as performance requirements, manageability and compatibility can hinder particular controls or provoke human error, defeat the control, give a false sense of security, or even increase the risk beyond the state without the control. The example in the text: complex passwords without adequate training, so that users write them down. A control can affect performance. Managers should seek a solution that meets performance requirements and at the same time ensures sufficient information security. The result is a list of possible controls with cost, benefit and implementation priority.

In selection and implementation, the following should typically be taken into account: time, finance, technology, operation, culture, ethics, environment, ease of use, personnel, and constraints in connecting new and existing controls. The English list entry for operation reads “operational constrains”. Further information is in Annex F.

9.3 Risk retention. The decision to retain the risk without further action should be made depending on the risk evaluation. If the level of risk meets the acceptance criteria, there is no need to implement additional controls, and the risk can be retained.

9.4 Risk avoidance. The activity or the condition that gives rise to the risk in question should be avoided. If the risks are regarded as too high, or the costs of other options exceed the benefit, it can be decided to avoid the risk completely by abandoning a planned or existing activity or a set of activities, or by changing the conditions. The example: for risks from nature, it can be the most cost-effective alternative to move the information processing facilities to a place where the risk does not exist or is controlled.

9.5 Risk sharing. The risk should be shared with another party that can handle the risk in question most effectively, depending on the evaluation. Sharing can create new risks or change risks already recognized. Then additional treatment can be needed. Sharing can take place through insurance that covers the consequences, or by contracting a partner whose role is to monitor the information system and to act immediately in order to stop an attack before it causes a specified degree of harm. It should be noted that responsibility for the handling can be shared, but liability for an impact normally is not. Customers usually attribute an adverse impact to the organization.

Clause 10 is a step of its own after the treatment. Input: treatment plan and assessment of the residual risk, which are subject to the acceptance decision. The action: the decision to accept the risks, and the responsibilities for the decision, should be made and formally recorded. Treatment plans should describe how assessed risks are treated in order to meet the acceptance criteria, see 7.2. It is important that responsible managers review and approve the proposed plans and the residual risks and record all conditions of that approval.

Acceptance criteria can be more complex than the question whether a residual risk lies above or below a single threshold. Sometimes the residual risk does not meet the criteria, because the criteria applied do not take the given circumstances into account. For example, it can be argued that risks would have to be accepted because the accompanying benefit is very attractive or the cost of the modification is too high. Such circumstances show that the criteria are inadequate and should be revised if possible. It is not always possible to revise them in time. Then decision-makers can accept risks that do not meet the normal criteria. If that is needed, the decision-maker should comment on the risks expressly and include a justification for the deviation from the normal criteria. Output: a list of accepted risks with a justification for those that do not meet the organization's normal acceptance criteria.

Annex F is informative and sets out the constraints on risk modification. Time: many kinds, for example implementation within a time limit acceptable to management, within the lifetime of the information or of the system, or the time that counts as acceptable exposure. Finance: controls should not be more expensive in implementation or maintenance than the value of the risks they are intended to protect against. An attempt should be made not to exceed allocated budgets. In some cases the desired degree of security and risk acceptance cannot be reached because of the budget. That then becomes a decision for management. Great care is called for when the budget reduces the number or the quality of the controls, because that can retain a higher risk than planned. The budget should be used as a limiting factor only with considerable care. The remaining points of the annex, technology, operation, culture, ethics, environment, ease of use, personnel and the bringing together of new and existing controls, are the same guidance with examples, including cultural differences and the conflict of a new access control with an existing one. The examples are not copied as a checklist. “Should” and “may” of the informative annex do not create a second demand beside Clause 9. The sentence that controls should not be more expensive than the value of the risks stands beside the pointer to use the budget as a limit only with care, and beside 9.1, according to which rare severe risks can require controls that are not justified on purely economic grounds.

Not in this text: a cost formula, an obligation to insure, a catalogue of controls from ISO/IEC 27002, and the statement of applicability. This guidance does not describe that. See 27005-10.