Risk = Likelihood × Impact
the simple math behind every prioritization argument
Security teams can never fix everything, so they have to decide what to fix first. The standard way to think about it is that risk is how likely something bad is, multiplied by how bad it would be.[1]
Likelihood and impact
- Likelihood: how probable is it that a threat will exploit a weakness in a given period? It depends on who wants to attack you, how exposed the weakness is, and how easy it is to use.
- Impact: what happens if it does? Money lost, data exposed, downtime, legal trouble, harm to people, damaged trust.
A threat (an attacker with a reason), a vulnerability (a weakness) and an asset (something of value) must all be present for risk to exist. Remove any one and the risk shrinks.
Qualitative and quantitative
Most teams use a qualitative scale: rate likelihood and impact as Low, Medium or High (or 1 to 5) and plot them on a grid. It is quick and good enough to rank things.
A quantitative approach puts numbers on it. A classic formula is annualized loss expectancy: ALE = SLE × ARO, where SLE is the single loss expectancy (cost of one incident) and ARO is the annual rate of occurrence (how many times a year). If a breach would cost 200,000 and is expected once every four years, ALE is 200,000 × 0.25 = 50,000 a year. That number helps compare against the cost of a control. Be aware that the inputs are estimates, so the output is a guide, not a fact.
Inherent and residual risk
- Inherent risk is the risk before any controls.
- Residual risk is what remains after controls. Management decides whether that is acceptable.
Four ways to treat a risk
- Mitigate: reduce it with controls.
- Transfer: share it, for example with insurance or a contract.
- Avoid: stop doing the risky thing.
- Accept: consciously live with it, with the decision recorded and owned.
Why this beats "everything is critical"
A scary-sounding flaw on an isolated test machine may matter less than a modest flaw on a system holding customer data. Risk thinking connects technical findings to the business, so the conversation is about what matters and why, not just severity scores. See also how a CVSS score fits in.
Sources
Test yourself
My notes
Private — saved only on this device, never sent anywhere.