Risk mitigation means reducing the likelihood or impact of a risk. It is one way to treat a risk—not a promise to eliminate it. The aim is to protect important assets while using the organization’s resources where they provide the greatest reduction in risk. section 2.2.3 section 2.0
|
Treatment
|
Definition
|
Example
|
|
Risk Mitigation
|
Reducing the
likelihood and/or impact of a risk through controls
|
Implementing
encryption and multi-factor authentication to reduce the likelihood of a data
breach
|
|
Risk Avoidance
|
Eliminating
the risk by removing the activity or risk source
|
Migrating a
server running a vulnerable unsupported application to a new server running an
alternative secure software.
|
|
Risk Transfer
|
Shifting
part or all the risk to a third party through agreements or insurance
|
Outsourcing
a service with contractual liability clauses or purchasing cyber insurance
|
|
Risk Acceptance
|
Retaining
the risk within defined tolerance levels without additional controls
|
Accepting
the risk of downtime for a non-critical service
|
Compare mitigation with the other treatment choices: avoiding the risk source, transferring risk to a third party, or accepting it within defined limits. section 2.2.3
Reducing data-breach risk
Encryption and multi-factor authentication are examples of controls used to reduce data-breach risk. Choosing controls still requires a practical check: will the expected reduction in risk justify their cost and their effects on usability, performance, and operations? section 2.2.3
Mitigation does not always require a new security control, and it can be combined with another treatment strategy. After taking action, evaluate the residual risk—the risk that remains—and decide whether to accept it or treat it further. Keep that decision within the ongoing process of identifying, assessing, treating, and monitoring risks. section 2.3 section 2.6




