How-to
How to Calculate ROI on Cybersecurity Investments
Last Updated: November 5, 2026
Quick Summary
ROI on cybersecurity investments is estimated by calculating the annualized loss expectancy without a control, the loss avoided once the control is in place, and the total cost of the solution. The formula is ROSI = (avoided loss − solution cost) ÷ solution cost. Using the article's worked example, a $24,000 avoided loss against a $15,000 cost yields a 60% return.
- Annualized loss expectancy equals single loss expectancy multiplied by annual rate of occurrence.
- Estimate the risk reduction percentage the control provides, then calculate the annual loss it avoids.
- Include first-year purchase, implementation labor, licensing and ongoing support in total solution cost.
- Test results with low, base and high input ranges before drawing conclusions from one figure.
- Measure post-rollout results against the predicted range and update the model before the next budget cycle.
Table of Contents
- What Cybersecurity ROI and ROSI Actually Measure
- Why Measuring Security Investment Value Is Hard
- Step 1 to 3: Estimate Risk Exposure, Likelihood and Loss
- Step 4 to 6: Estimate Risk Reduction and Total Solution Cost
- Cybersecurity Investment Examples with Worked Numbers
- Building a Cybersecurity ROI Calculator and Excel Template
- Testing Your Numbers with Ranges and Measuring Results After Rollout
- Start Your Own Security Investment Case with VegaMSP
- Frequently Asked Questions
Every security budget request eventually meets the same question from the finance team: what do we get for this money? Cybersecurity investments are hard to justify on return alone, because the best outcome of a security control is a breach that never happens. This guide walks through a transparent method for estimating that value, step by step, so you can make the case with numbers you can defend.
What Cybersecurity ROI and ROSI Actually Measure
Return on security investment (ROSI) estimates how much financial value a security control adds compared with what it costs. It asks a simple question: how much expected loss does this investment remove, relative to its price?
People often use "ROI" and "ROSI" interchangeably, but they are not the same. ROI is a general finance term. ROSI applies that logic to security, where the "return" is avoided loss rather than new revenue.
Because security produces avoided losses, not sales, the calculation depends on estimates. A good model makes those estimates visible so others can challenge them.
Why Measuring Security Investment Value Is Hard
Security spending pays off in events that do not occur. If a ransomware attack is stopped, nothing visible happens, and no one sees the loss that was avoided.
Several other factors make the math difficult:
- Breach probability is uncertain. Nobody knows the exact odds of an attack this year.
- Loss amounts vary. A breach can cost a little or a lot, depending on data, downtime, and response speed.
- Benefits are spread out. Compliance, reputation, and customer trust are real, but hard to price.
- Cost of the control is not always clear. Licenses, labor, and monitoring add up over time.
Accepting that difficulty up front is the first step toward a useful estimate.
Step 1 to 3: Estimate Risk Exposure, Likelihood and Loss
The calculation starts with three inputs that describe the risk itself.
Step 1: Estimate single loss expectancy (SLE). SLE is the cost of one incident. Add up recovery costs, lost revenue during downtime, and response expenses. Your own downtime cost per hour and recovery time will determine the figure.
Step 2: Estimate the annual rate of occurrence (ARO). ARO is how often you expect this incident per year. A rate of 0.2 means one incident every five years. Base this on past incidents, industry reports, or your threat assessment.
Step 3: Calculate annualized loss expectancy (ALE). Multiply the two:
ALE = SLE × ARO
Using the numbers above, ALE is $200,000 × 0.2 = $40,000 per year. This is the expected annual loss without the new control. It becomes the baseline you measure improvement against.
Step 4 to 6: Estimate Risk Reduction and Total Solution Cost
Next, estimate how much the control lowers that loss, and what the control costs.
Step 4: Estimate the risk reduction percentage. Ask how much the control reduces either the likelihood or the impact of an incident. A 60% reduction means the annual loss drops from $40,000 to $16,000.
Step 5: Calculate the annual benefit. Subtract the new expected loss from the baseline: $40,000 − $16,000 = $24,000 in avoided loss per year.
Step 6: Total the solution cost. Include the first-year purchase, implementation labor, licensing, and ongoing support. Total ownership cost often surprises teams, so add the recurring costs for the full period you are evaluating. If the solution costs $15,000 per year all in, the calculation is straightforward from here.
Then apply the ROSI formula:
ROSI = (Avoided loss − Solution cost) ÷ Solution cost
With $24,000 avoided and $15,000 spent, ROSI is ($24,000 − $15,000) ÷ $15,000 = 60%.
A high result from optimistic inputs is not proof of value. Your own numbers will differ, so test the range before drawing conclusions.
Cybersecurity Investment Examples with Worked Numbers
Consider a hypothetical 120-person professional services firm weighing an endpoint protection and monitoring service. Its ransomware loss estimate is based on a one-day outage affecting client billing and staff time.

| Input | Estimate |
|---|---|
| SLE (one incident) | $180,000 |
| ARO (incidents per year) | 0.15 |
| Baseline ALE | $27,000 |
| Risk reduction | 50% |
| Expected ALE after control | $13,500 |
| Annual avoided loss | $13,500 |
| Annual solution cost | $10,000 |
| ROSI | 35% |
The control pays for itself, but not by a wide margin. If the risk reduction estimate drops to 30%, the avoided loss falls to $8,100 and the solution no longer covers its cost. That sensitivity is exactly what decision-makers need to see.
Work through your own numbers with the downtime cost formula so the SLE input is grounded in real hourly figures. When you are ready to compare providers and build the cost side, a managed IT provider evaluation guide covers what to ask for.
Building a Cybersecurity ROI Calculator and Excel Template
Most guides tell you to "build a calculator" for your cybersecurity investments and stop there. A reproducible model is one a reader can rebuild from scratch and get the same number.
Sheet 1, Inputs. Put one input per row, with columns for the value, the low and high bounds, and the source. Keep the source column honest: "incident log 2023-2025," "vendor claim, unverified," or "team estimate." A reviewer who can see which numbers are soft will trust the hard ones more.
| Input | Value | Low | High | Source |
|---|---|---|---|---|
| Downtime cost per hour | $5,000 | $3,500 | $7,000 | Billing and payroll records |
| Hours to recover from one incident | 40 | 24 | 72 | Last two incident post-mortems |
| Response and forensics fees | $25,000 | $15,000 | $60,000 | Retainer agreement |
| ARO (incidents per year) | 0.20 | 0.10 | 0.40 | Two incidents in ten years, adjusted for growth |
| Risk reduction from control | 60% | 30% | 75% | Control testing and vendor documentation |
| Annual solution cost | $15,000 | $15,000 | $22,000 | Quote plus internal labor estimate |
Sheet 2, Calculation. Reference the Inputs sheet by cell so the math is live. The formulas are short enough to type directly:
- SLE:
=B2*B3+B4(downtime cost × hours + response fees) → $5,000 × 40 + $25,000 = $225,000 - Baseline ALE:
=B7*B5(SLE × ARO) → $225,000 × 0.20 = $45,000 - ALE after control:
=B9*(1-B8)→ $45,000 × (1 − 0.60) = $18,000 - Annual avoided loss:
=B9-B10→ $45,000 − $18,000 = $27,000 - ROSI:
=(B11-B6)/B6→ ($27,000 − $15,000) ÷ $15,000 = 80%
Sheet 3, Scenarios. Copy the Calculation sheet three times and point each copy at the Low, Value, or High column on the Inputs sheet. A single CHOOSE or INDEX formula can switch all inputs at once, but three static copies are easier for a non-technical reviewer to audit. The output is a range, for example, ROSI of −40% at the low end, 80% at the base case, and 260% at the high end, which is far more defensible than one optimistic number.
Sheet 4, Sensitivity. Rank the inputs by how much they move ROSI. A quick way is a one-way data table: hold every input at its base value, flex one input across its low-to-high range, and record the resulting ROSI.
Watch out: a calculator that hides its formulas behind a single output cell invites the accusation that the result was reverse-engineered to justify a purchase. Keep every formula visible and every assumption labeled, or the model will not survive a finance review.
Where you can, replace a guess with a record.
Testing Your Numbers with Ranges and Measuring Results After Rollout
A single ROSI figure hides uncertainty, and a model that is never checked against reality is just a persuasive guess.
Stress-test with three scenarios. Replace each input with a low, base, and high value and run the calculation three times. Use the low case for the downside a skeptic will raise, the base case for your planning number, and the high case only to show upside. If ROSI stays positive across the low and base cases, the case is strong. If it turns negative under reasonable pessimism, say so plainly and explain what would have to be true for the investment to pay off, decision-makers trust a model that admits its weak points.
Run a sensitivity ranking. Flex one input at a time across its range while holding the others at base.
Define the baseline before rollout. Record the metrics you will compare against, using the same definitions you will use later. Typical baselines include:
- Incident count per quarter, by category (phishing, ransomware, unauthorized access)
- Mean time to detect and mean time to recover, in hours
- Downtime hours attributable to security events
- Number of events escalated to response versus contained automatically
Pick a measurement window long enough to capture a realistic incident rate. If your ARO is 0.20, one incident every five years, a 90-day post-rollout window will almost certainly show zero incidents whether or not the control works.
Compare predicted with observed. After the measurement period, put the actuals next to the model.
Separate control effectiveness from luck. A quiet quarter is not proof of value, and a single incident is not proof of failure. Compare the observed rate against the predicted range rather than against zero.
Watch out: changing metric definitions between baseline and post-rollout measurement, for example, counting only confirmed breaches after counting all suspected incidents before, will make any control look effective. Lock the definitions in writing before deployment.
Over a few review cycles, this loop turns estimates into evidence. The first model is a hypothesis; the third is a track record, and a track record is what gets the next budget approved.
Start Your Own Security Investment Case with VegaMSP
Building a defensible ROSI estimate takes solid inputs, and the cost side is often the hardest to pin down. VegaMSP offers a fully managed "Secure-IT-In-The-Box" model that covers network services, endpoint security, VoIP, and unlimited helpdesk support. Pricing depends on your environment and scope, so contact VegaMSP for a quote tailored to your team size and risk profile. Start with the numbers in this guide, then bring them to the conversation.
Frequently Asked Questions
What is ROI in cybersecurity?
Cybersecurity ROI compares the financial value of losses a security investment is expected to prevent against what the investment costs. In practice, teams estimate annual loss exposure before and after a control is in place, subtract the cost of that control, and divide by the cost. Because most of the value is avoided loss rather than revenue, the result depends heavily on how carefully the risk inputs are estimated. Using ranges instead of single guesses makes the figure more defensible to finance leaders.
What is the difference between ROI and ROSI in cybersecurity?
ROI is the general return on investment formula, while return on security investment (ROSI) applies the same logic specifically to security spending. ROSI uses risk exposure, the percentage of risk a control is expected to mitigate, and the cost of the solution. The Safe Security example calculates ROSI as (risk exposure × risk mitigation percentage − cost of solution) ÷ cost of solution. The distinction matters because the inputs are estimates of avoided loss rather than measured sales.
How do you calculate cybersecurity ROI in Excel?
Build a sheet with input cells for risk exposure, annual rate of occurrence, mitigation percentage, and total solution cost, including implementation and operating costs. Calculate annualized loss expectancy as single loss expectancy multiplied by annual rate of occurrence, then compute ROSI with the standard formula. Add a second scenario column with lower and higher assumptions to show sensitivity. Pricing for any tools you use depends on your licensing and vendor, so confirm current costs directly with the vendor.
What costs should be included in a cybersecurity ROI calculation?
Include the full cost of the solution, not only the license fee. That means implementation labor, configuration, staff training, ongoing monitoring, support, and any tooling needed to keep the control effective. On the benefit side, count only the loss the control is expected to prevent, such as incident response, recovery, and downtime costs. Avoid counting the same benefit twice, for example reputational gains that are already reflected in the loss estimate.