ISC2 CISSP guideStudy & preparation

CISSP Risk Calculations: SLE, ALE, ARO and Whether a Control Is Worth Its Cost

CISSP risk math uses five quantities and one comparison: asset value, exposure factor, single loss expectancy, annualized rate of occurrence, annualized loss expectancy, and whether a safeguard saves more than it costs. Here is each step with original worked examples, the risk responses NIST names, and the traps that cost points.

Short answer

CISSP quantitative risk items use a standard chain. Single loss expectancy (SLE) is the loss from one occurrence: asset value × exposure factor. Annualized loss expectancy (ALE) is the expected loss per year: SLE × annualized rate of occurrence (ARO), where an event expected once every N years has an ARO of 1/N. A safeguard is worth its cost when the ALE before it, minus the ALE after it, minus its annual cost is positive. ISC2's outline doesn't print these formulas, but its exams include calculation items, and Domain 1 covers risk analysis and response.

ISC2's CISSP outline never prints a risk formula. Objective 1.9, "Understand and apply risk management concepts," lists risk analysis, assessment and scope, and risk response and treatment, and ISC2's Candidate Information Bulletin says exams can include calculation items. Put together, that means a CISSP candidate should be able to turn a short scenario into a loss figure and a decision. The method below is the standard quantitative approach taught for the CISSP, with NIST's definitions where NIST provides them. It applies to both the 2024 outline and the 2027 outline, which keeps objective 1.9 and adds "risk mitigation strategies" as an example.

The five quantities in CISSP risk math

QuantityWhat it meansHow to get it
Asset value (AV)What the asset is worth to the organizationGiven in the scenario
Exposure factor (EF)The share of the asset's value lost in one eventA percentage, given or estimated
Single loss expectancy (SLE)The loss from one occurrenceAV × EF
Annualized rate of occurrence (ARO)How many times a year the event is expectedEvents per year; once every N years = 1 ÷ N
Annualized loss expectancy (ALE)The expected loss per yearSLE × ARO

NIST's IR 8286Ar1 (December 2025) describes the two outputs the same way: SLE as the loss for each occurrence, and ALE as the total loss for that risk over an annual period. The formulas in the right-hand column are the arithmetic that connects them.

A worked example (original, Passy's numbers). A customer database is valued at $1,200,000. A breach would cost 40% of that value (the exposure factor), and analysts expect such a breach about once every eight years.

  1. SLE = $1,200,000 × 0.40 = $480,000
  2. ARO = 1 ÷ 8 = 0.125
  3. ALE = $480,000 × 0.125 = $60,000 a year

Turning "once every N years" into an ARO

A common slip happens here, because scenarios rarely say "ARO." They say how often.

The scenario saysARO
Three times a year3
Once a year1
Once every 2 years0.5
Once every 4 years0.25
Once every 5 years0.2
Once every 8 years0.125
Once every 10 years0.1
Once every 25 years0.04
Once every 100 years0.01

The ARO is a rate per year, not a number of years. If you find yourself multiplying an SLE by 8 because the event happens "every 8 years," stop: the ALE should shrink as events get rarer, not grow.

Is a CISSP safeguard worth it? The cost-benefit test

The standard comparison taught in CISSP prep (neither ISC2's outline nor NIST prints it as a formula):

Value of the safeguard = ALE before − ALE after − annual cost of the safeguard

A positive result means the control saves more each year than it costs. A negative result means that, on the numbers alone, it doesn't pay.

Continuing the database example, with two candidate controls:

Control A: encryption and data loss preventionControl B: a managed monitoring service
Annual cost$25,000$55,000
EffectBreach expected once every 40 years (ARO 0.025)Same effect as A
ALE after$480,000 × 0.025 = $12,000$12,000
Value$60,000 − $12,000 − $25,000 = $23,000$60,000 − $12,000 − $55,000 = −$7,000

Control A is justified; Control B costs more than the risk it removes. Notice that both controls reduce risk by the same amount. The question isn't which control is stronger but which one is worth its cost.

A control can also work on the exposure factor instead of the ARO. Suppose a separate risk to the same database, ransomware, has the same figures: 40% exposure, once every eight years, an ALE of $60,000. Immutable offsite backups costing $20,000 a year would cut the damage to 10% of the asset's value without changing how often attacks happen. SLE after = $1,200,000 × 0.10 = $120,000, ALE after = $120,000 × 0.125 = $15,000, and the value is $60,000 − $15,000 − $20,000 = $25,000.

One-time costs. If a control has a purchase price, convert it to a yearly figure before comparing it with an ALE. A simple approach (Passy's simplification): spread the purchase over its useful life and add yearly support. A $90,000 system used for three years with $5,000 a year of support costs $90,000 ÷ 3 + $5,000 = $35,000 a year.

Security and Risk Management, where this arithmetic sits, is the heaviest domain under the 2024 outline at 16%, and it carries the largest share of the planned CISSP question bank.

Residual risk and the risk responses NIST names

After a control is in place, some risk remains. NIST SP 800-30 Rev. 1 defines residual risk as the portion of risk remaining after security measures have been applied. In the example above, Control A leaves $12,000 a year of residual ALE, and someone with the authority to do so has to accept it.

NIST SP 800-39 lists the ways an organization can respond to risk:

ResponseWhen NIST says it fitsCISSP-style example
AcceptThe risk is within the organization's risk toleranceLeadership signs off on the $12,000 residual ALE
AvoidThe risk exceeds tolerance and the activity can be dropped or redesignedStop storing the data the business doesn't need
Mitigate (reduce)For the part of the risk that can't be accepted, avoided, shared or transferredEncryption and data loss prevention
Share or transferThe organization wants to shift liability or responsibility to another partyCybersecurity insurance, which the outline names as an example
A combinationSituations change over timeAccept briefly, then mitigate

NIST adds a point worth remembering for scenario items: transferring risk through insurance reduces neither the likelihood of the harmful event nor its consequences. It moves the financial liability, not the incident. Ignoring a risk isn't on NIST's list at all.

Quantitative, qualitative and semi-quantitative analysis

NIST SP 800-30 Rev. 1 describes three approaches:

  • Quantitative uses numbers whose meaning holds outside the assessment, like the dollar figures above. NIST says it best supports cost-benefit analysis, but warns that its rigor drops when subjective guesses hide inside the numbers.
  • Qualitative uses categories such as very low to very high. NIST says it helps communicate risk to decision makers but makes fine comparisons hard.
  • Semi-quantitative uses scales or bins, such as 1 to 10, that translate easily into qualitative terms while allowing relative comparisons.

A question that asks which approach supports a budget decision about a specific control points to quantitative analysis. A question about quickly ranking dozens of risks for executives points to qualitative or semi-quantitative.

Five traps in CISSP risk calculation items

These are common patterns in practice questions, not ISC2 findings:

  1. Answering with the SLE when the question asks for the ALE, or the reverse. Underline which one the stem wants.
  2. Using years instead of a rate for the ARO. Once every 5 years is 0.2, not 5.
  3. Comparing a one-time loss with a yearly cost. Compare ALE with annual cost, or SLE with a one-time figure, never across.
  4. Forgetting to subtract the control's cost. The biggest ALE reduction isn't automatically the best choice.
  5. Letting the numbers override everything. If a control protects human life or is legally required, a negative cost-benefit result doesn't settle the question, as the think like a manager guide explains.

When a calculation goes wrong in practice, the useful step is to find which link in the chain broke: AV, EF, ARO or the comparison. Fix It in the planned CISSP prep keeps every missed calculation for another try.

CISSP risk practice items written by Passy

These are original items, not ISC2 questions. Cover the reasoning and try each first.

1. A branch office's equipment is valued at $250,000. A fire would destroy 60% of it, and fires are expected about once every 25 years. What is the ALE?

Keyed answer: $6,000. SLE = $250,000 × 0.60 = $150,000. ARO = 1 ÷ 25 = 0.04. ALE = $150,000 × 0.04 = $6,000. A common wrong answer is $150,000, which is the SLE.

2. An upgraded sprinkler system for the same office costs $9,000 a year and would cut the fire's exposure factor to 20%. On the numbers alone, is it justified?

Keyed answer: no. SLE after = $250,000 × 0.20 = $50,000, ALE after = $50,000 × 0.04 = $2,000, and the value is $6,000 − $2,000 − $9,000 = −$5,000. But sprinklers protect people and may be required by fire codes, so a real decision wouldn't rest on this result alone.

3. A company buys a cyber insurance policy that pays for breach-response costs. Which risk response is this, and what doesn't it change?

Keyed answer: risk transfer. It shifts the financial liability to the insurer. It doesn't change how likely a breach is or the operational and reputational harm one causes.

Practicing CISSP risk math this week

Write the chain on one line, AV × EF = SLE, SLE × ARO = ALE, and solve three scenarios a day for a week, converting every "once every N years" before you multiply. The 20 free CISSP practice questions include an ALE item to check yourself against. For recovery-time math, which uses hours rather than dollars, continue with the CISSP BCP and disaster recovery guide, and if Domain 1 turns out to be your weakest area, planned CISSP prep's Weak Spot drill targets your lowest-accuracy domain five questions at a time.

Trust the source

Official sources

Exam policies can change. Use these primary sources for the most current details.