{"id":16,"date":"2022-04-12T00:52:01","date_gmt":"2022-04-12T00:52:01","guid":{"rendered":"http:\/\/tcm.gov.to\/?page_id=16"},"modified":"2022-08-18T01:22:21","modified_gmt":"2022-08-18T01:22:21","slug":"risk-treatment","status":"publish","type":"page","link":"https:\/\/tcm.gov.to\/?page_id=16","title":{"rendered":"Risk Treatment"},"content":{"rendered":"
\n \t\n\t
\n\t \t
\n\t\t\t
\n\t \t \t
\n\t\t \n
\n
\n

Risk Treatment and Security Controls<\/h1>\n

\"\"<\/p>\n

Figure 3. Risk treatment activity according to ISO\/IEC 27005:2018<\/em><\/p>\n

In general, risk treatment gives four options to consider for each and every identified risk. These options are risk modification, retention, avoidance and risk sharing.<\/p> <\/div>\n<\/div>\n\n\n

\n
\n

Risk modification\u00a0<\/h4>\n

The level of risk should be managed by introducing, removing or altering security controls so that the residual risk can be reassessed as being acceptable.\u00a0<\/p>\n

Appropriate and justified controls should be selected to meet the requirements identified by the risk assessment and risk treatment. This selection should also take account of the cost and timeframe for implementation of controls, or technical, environmental and cultural aspects.\u00a0<\/p>\n

In general, controls can provide one or more of the following types of protection: correction, elimination, prevention, impact minimization, deterrence, detection, recovery, monitoring and awareness. During control selection, it is important to weigh the cost of acquisition, implementation, administration, operation, monitoring, and maintenance of the controls against the value of the assets being protected.\u00a0\u00a0<\/p> <\/div>\n<\/div>\n\n\n

\n
\n

Risk retention<\/h4>\n

The decision on retaining the risk without further action should be taken depending on risk evaluation.\u00a0<\/p>\n

If the level of risk meets the risk acceptance criteria, there is no need for implementing additional controls and the risk can be retained.<\/p> <\/div>\n<\/div>\n\n\n

\n
\n

Risk avoidance<\/h4>\n

The activity or condition that gives rise to the particular risk should be avoided.\u00a0<\/p>\n

When the identified risks are considered too high, or the costs of implementing other risk treatment options exceed the benefits, a decision can be made to avoid the risk completely, by withdrawing from a planned or existing activity or set of activities, or changing the conditions under which the activity is operated. For example, for risks caused by nature it can be the most cost-effective alternative to physically move the information processing facilities to a place where the risk does not exist or is under control.\u00a0\u00a0<\/p> <\/div>\n<\/div>\n\n\n

\n
\n

Risk sharing\u00a0<\/h4>\n

The risk should be shared with another party that can most effectively manage the particular risk depending on the risk evaluation.\u00a0<\/p>\n

Risk sharing involves a decision to share certain risks with external parties. Risk sharing can create new risks or modify existing, identified risks. Therefore, additional risk treatment may be necessary. Sharing can be done by an insurance that covers the consequences, or by sub-contracting a partner whose role is to monitor the information system and take immediate action to stop an attack before it makes a defined level of damage.\u00a0<\/p>\n

It should be noted that it can be possible to share the responsibility to manage risks but it is not normally possible to share the liability of an impact.\u00a0\u00a0<\/p> <\/div>\n<\/div>\n\n\n

\n
\n

Specific risk treatment starts with selecting the appropriate treatment option \u2013 risk modification, retention, avoidance or sharing. According to the chosen risk treatment option, security controls for the system can now be selected and tailored to achieve the desired security objectives. Once the applicable security controls have been identified for a system, the implementation process follows. To facilitate the risk treatment process, a tool (see Annex 1<\/a>) has been created that helps to record details about the implementation status of the control, required resources, responsible persons and deadlines of control implementation.\u00a0<\/p>\n

The following listed security controls should be considered as a baseline, and not be considered as an exhaustive list of applicable security controls.\u00a0<\/p>\n

The security controls listed in this manual cover the following domains:\u00a0\u00a0<\/p>\n