Risk Calculation: Using Likelihood and Impact to Determine Risk Severity
CISM · Information Security Risk Management · By Super Admin
Understand how combining likelihood of occurrence and magnitude of impact produces a risk severity score used to prioritize organizational risks.
The Two Factors of Risk Calculation
Not all risks are equal, and organizations need a structured way to compare and prioritize them. Risk calculation is the process used to evaluate and compare risks based on two distinct factors. The first factor is the likelihood of occurrence, or probability, that the risk will occur. This is expressed as the percentage of chance that a threat will exploit a vulnerability over a specified period of time, such as within the next year. The second factor is the magnitude of the impact that the risk will have on the organization if it does occur, which may be expressed as the financial cost incurred as a result of the risk, although other measures are also possible.
Using these two factors, risk analysts assign each risk a conceptual score by combining the probability and the magnitude. This leads many risk analysts to express the severity of a risk using the formula: Risk Severity = Likelihood × Impact. It is important to note that this equation does not always have to be interpreted literally. Although values may be multiplied together in some risk assessment processes, it is best to think of this conceptually as combining the likelihood and impact to determine the severity of a risk.
Applying Risk Calculation to Real Scenarios
The risk calculation framework becomes clearer when applied to concrete examples. Consider the risk of being struck by a bicycle versus being struck by a meteor while walking on a sidewalk. There might be a high probability of being struck by a bicycle, and that type of accident might have a moderate magnitude, making it worth considering steps to reduce the risk. Being struck by a meteor would clearly have a catastrophic magnitude of impact, but the probability of such an incident is incredibly unlikely, leading a person to acknowledge the risk and move on without changing behavior.
This example demonstrates that a very high impact does not automatically make a risk the highest priority. Probability plays an equally important role in determining overall risk severity. A risk with moderate impact but very high probability may warrant more attention and resources than a catastrophic but extremely rare event. Risk calculation provides the analytical structure to make these comparisons in a consistent and defensible way.
The Role of Laws and Regulations in Impact Assessment
The laws and regulations facing an industry may play a significant role in determining the impact of a risk. For example, an organization subject to the European Union's General Data Protection Regulation (GDPR) faces significant fines if they have a data breach affecting the personal information of EU residents. The size of these fines would factor significantly into the impact assessment of the risk of a privacy breach. Organizations must, therefore, remain aware of the current regulations that affect their risk posture.
Regulatory considerations can substantially change the calculated severity of a risk that might otherwise appear manageable. A data breach that causes limited direct operational damage could carry enormous financial consequences when regulatory fines are factored into the impact calculation. This means that risk managers must incorporate legal and regulatory context into their impact assessments, not just technical or operational consequences, to arrive at an accurate picture of risk severity.
Key takeaways
- Risk severity is determined by combining the likelihood of occurrence and the magnitude of impact using the formula Risk Severity = Likelihood × Impact.
- A catastrophic but extremely unlikely risk, such as a meteor strike, may warrant less attention than a moderate-impact but high-probability risk.
- Regulatory requirements such as GDPR fines must be factored into the impact assessment of risks like privacy breaches.
Discussion (0)
No discussion on this article yet — be the first to comment.
Please sign in to join the discussion.