Quantitative risk analysis puts a money figure on a risk. Security+ tests it with three linked formulas: single loss expectancy (SLE), annualized rate of occurrence (ARO) and annualized loss expectancy (ALE). Enter your own numbers below to see each step worked out, then read the formulas, examples and the traps that catch people on the exam.
ALE calculator
Enter the asset value, the exposure factor as a percentage and how often the event happens. Tick the control box to see whether a control pays for itself. The results and formulas update as you type.
Your results
ALE $2,500 a year. SLE $25,000 per incident.
- Single loss expectancy (SLE)
- $25,000
- Annualized rate of occurrence (ARO)
- 0.1
- Annualized loss expectancy (ALE)
- $2,500
SLE = AV × EF = $100,000 × 25% (0.25) = $25,000
ARO = 1 ÷ 10 years = 0.1
ALE = SLE × ARO = $25,000 × 0.1 = $2,500
A quantitative estimate from your inputs. Real risk decisions also weigh things the formula leaves out, such as legal duties and reputation. Nothing you enter is saved.
The formulas: SLE, ARO and ALE
| Term | What it means | Formula |
|---|---|---|
| Asset value (AV) | What the asset is worth to the organisation: replacement cost, and lost revenue or data value where they apply. | An input |
| Exposure factor (EF) | The share of the asset’s value lost in one incident, from 0% (no loss) to 100% (total loss). | An input, 0–100% |
| Single loss expectancy (SLE) | The expected cost of one incident. | SLE = AV × EF |
| Annualized rate of occurrence (ARO) | How many times a year you expect the incident. Can be below 1 or above 1. | ARO = 1 ÷ N for once every N years |
| Annualized loss expectancy (ALE) | The expected loss from that risk over one year. | ALE = SLE × ARO |
Put together, the annual figure is:
ALE = AV × EF × ARO
ALE is what makes risks comparable and lets you judge a control. A control usually lowers the ARO (it makes the incident less likely) or the EF (it makes each incident less damaging). The value of the control is the loss it prevents each year, minus what it costs each year:
Value of control = (ALE before − ALE after) − annual cost of the control
If the result is positive, the control saves more than it costs. If it is negative, the control costs more than the loss it prevents, and accepting or transferring the risk may be the better business decision. The ALE that remains after the control is part of your residual risk. These formulas sit under objective 5.2; our risk management objective page covers the rest of it, from risk registers to appetite and tolerance.
Worked examples
These examples use made-up numbers chosen to look like real situations. They are for practice, not benchmarks.
Example 1: laptop theft, with a control that pays for itself
A company values each laptop at $1,500. A stolen laptop is a total loss, so the EF is 100%. It loses about 6 laptops a year.
SLE = AV × EF = $1,500 × 100% (1) = $1,500
ARO = 6 per year
ALE = SLE × ARO = $1,500 × 6 = $9,000
Cable locks, tracking software and staff reminders would cost $3,000 a year and are expected to cut thefts to 2 a year. The ALE with the control is $3,000.
Value = (ALE before − ALE after) − annual cost = ($9,000 − $3,000) − $3,000 = $3,000
The control is worth it: it prevents $6,000 of loss a year and leaves $3,000 a year after paying for itself.
Example 2: a flood, with a control that does not pay
A data centre and its equipment are valued at $2,000,000. A flood would damage about 25% of it, and the site floods about once every 20 years.
SLE = AV × EF = $2,000,000 × 25% (0.25) = $500,000
ARO = 1 ÷ 20 years = 0.05
ALE = SLE × ARO = $500,000 × 0.05 = $25,000
Flood defences would cost $30,000 a year, counting their purchase price spread over their life plus upkeep. They would not stop floods, but they would cut the damage from each one to 10%, so the SLE drops to $200,000 and the ALE to $10,000.
Value = (ALE before − ALE after) − annual cost = ($25,000 − $10,000) − $30,000 = −$15,000
On cost alone the defences are not worth it: they prevent $15,000 of loss a year but cost $30,000. Insurance (transferring the risk) or accepting it may make more sense, though a real decision would also weigh safety and downtime.
Example 3: ransomware on a file server
The data on a file server is valued at $200,000. Backups mean an attack would cost about 60% of that in lost work, recovery time and clean-up, and the company expects an attack about once every 4 years.
SLE = AV × EF = $200,000 × 60% (0.6) = $120,000
ARO = 1 ÷ 4 years = 0.25
ALE = SLE × ARO = $120,000 × 0.25 = $30,000
Notice that the ALE ($30,000) is smaller than the SLE ($120,000). That is normal when an event happens less than once a year. It does not mean one attack would cost $30,000; one attack still costs $120,000.
Common exam traps
- EF as a percentage versus a decimal. 25% and 0.25 are the same EF, but you multiply by 0.25. Multiplying $100,000 by 25 instead of 0.25 gives an answer 100 times too big. If a question gives EF as a percentage, convert it before you multiply.
- ARO below 1. An ARO of 0.1 means once in 10 years, not 10 times a year. Questions often say "once every five years", and you have to turn that into 1 ÷ 5 = 0.2 yourself. ARO can also be above 1: six incidents a year is an ARO of 6.
- ALE versus SLE. Read whether the question asks for the cost of one incident (SLE) or the expected cost per year (ALE). When you judge a control, compare its annual cost with the ALE, not the SLE, because both are yearly figures.
- Annual cost of the control. A control with a purchase price has to be turned into a yearly figure first. Spread the price over the years it will be used and add yearly running costs, then compare.
- Quantitative versus qualitative. SLE, ARO and ALE are quantitative: they use money and numbers. A risk matrix or heat map that rates likelihood and impact as low, medium or high is qualitative, even when the ratings are scored 1 to 5, because the scores rank risks rather than measure money. Qualitative analysis is quicker and is used when you cannot put reliable numbers on a risk.
RTO, RPO, MTTR and MTBF
Objective 5.2 also expects the business impact analysis metrics. They measure time rather than money, and they are easy to mix up, so learn them as a set.
| Metric | What it means | Example |
|---|---|---|
| RTO: recovery time objective | The longest a system can stay down before the outage is unacceptable; how fast it must be restored. | Payroll has an RTO of 4 hours, so it must be running again within 4 hours of failing. |
| RPO: recovery point objective | The most data you can afford to lose, measured as time back to the last good copy. It sets how often you back up. | An RPO of 1 hour means backups or replication at least every hour. A nightly backup gives an RPO of up to 24 hours. |
| MTTR: mean time to repair | The average time it takes to fix a failed component and return it to service. Lower is better. | Three outages took 2, 3 and 4 hours to fix: MTTR = 9 ÷ 3 = 3 hours. |
| MTBF: mean time between failures | The average time a repairable system runs between one failure and the next. Higher is better. | Servers ran 50,000 hours in total with 5 failures: MTBF = 50,000 ÷ 5 = 10,000 hours. |
Two quick checks help on the exam. RTO is about downtime and RPO is about data loss. And if your MTTR is longer than your RTO, you cannot meet the RTO by repairing the system alone, so you need a faster recovery option such as a standby system. Add these terms to your revision with our Security+ acronyms list, and fit risk management into your week with the Security+ study plan generator.