Join our Newsletter — 33% off our NHI Course
Home› Guides› Security Business Case Template: Options, Costs, Risk Reduction…
Template Security Leadership & Governance

Security Business Case Template: Options, Costs, Risk Reduction and Approval

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 10 min read
On this page

Security investments are often rejected not because the risk is unconvincing but because the business case compares one option with nothing, hides the running cost and gives the approver no way to check the benefits later. This template sets out a reusable business case for any security investment, from a new detection capability to a network segmentation programme. It adapts the Five Case Model in the UK HM Treasury Green Book (strategic, economic, commercial, financial and management cases) to security, and links risk reduction to the organisation's risk register in the way NIST IR 8286 describes. It is written for CISOs, security architects and programme leads who need approval from finance, a change board or the executive committee. For identity programmes specifically, see the Business Case Guide.

How to use this template

  • Replace text in square brackets, such as [Organisation], [Sponsor], [Investment Name] and [currency], with your own names and values.
  • "Must" indicates content the approver should expect in every case; "should" indicates content that can be shortened for small investments below [threshold].
  • Write section 3 (options) before section 4 (economic case). The Green Book requires business as usual to be appraised as a benchmark even when it does not meet the objectives, and a do minimum option exposes gold plating.
  • Take risk figures from the [Risk Register] and its owners rather than estimating them inside the case, so the approver sees the same numbers the risk committee sees. See the Risk Register Template.
  • Use it with the Security Budget Template and Cost Model, which holds the run cost once the investment is delivered.

1. Executive summary

One page, written last. It must state: the problem in one sentence; the recommended option; whole-life cost over [three to five] years, split into one-off change cost and annual run cost; the risk reduction expected, with the risk register references; the main dependency; and the decision requested, by when and from whom.

ItemEntry
Investment[Investment Name]
Sponsor and owner[Sponsor, role]; [Delivery Owner, role]
Risks addressed[R-012 Ransomware spreading across flat network; R-031 Regulator finding on segregation]
Recommended option[Option C]
One-off cost / annual run cost[amount] / [amount]
Decision requested[Approve funding of [amount] for phase 1 at [Investment Board] on [date]]

2. Strategic case

  1. Case for change: describe the current state with evidence: incident data, assessment or audit findings, penetration test results, regulator or insurer requirements, or control gaps against [framework]. Avoid general threat statistics unless they come from a named primary source with an as-of year.
  2. Risks addressed: list each risk register entry with its current rating, risk owner and whether it is above appetite. See the Cyber Risk Appetite Statement Template.
  3. Objectives: state 3 to 5 SMART objectives, for example "[Reduce lateral movement paths from user VLANs to server networks to zero for Tier 0 assets by [date]]".
  4. Strategic fit: show the link to the [Security Strategy], the board's risk appetite and any obligations (for example NIST CSF 2.0 outcome ID.RA-06, risk responses are chosen, prioritised, planned, tracked and communicated).
  5. Business as usual: describe what happens if nothing changes, including rising run costs, end-of-support dates and the likely trend of the risk.

3. Options considered

The case must appraise a shortlist of around five options, following the Green Book pattern. Options that fail the objectives can be noted and discarded at long list stage, except business as usual.

OptionDescriptionMeets objectives?Indicative whole-life costResidual risk
A. Business as usual[Current controls continue][No][amount][High]
B. Do minimum[Meets objectives with least change, e.g. compensating controls for Tier 0 only][Partly][amount][Medium]
C. Preferred way forward[Proposed solution][Yes][amount][Low]
D. More ambitious[Wider scope or faster delivery][Yes][amount][Low]
E. Less ambitious[Reduced scope or phasing][Partly][amount][Medium]
  • Critical success factors: score each option against [4 to 6] factors agreed with the sponsor, such as risk reduction, fit with existing architecture, operational effort, time to value and supplier capacity.
  • Build, buy or service: where relevant, include a managed service option. See the Managed Security Service Provider Buyers Guide.

4. Economic case

The economic case compares costs and benefits of the shortlisted options over the same period.

ElementWhat to includeSource
One-off costsLicences in year one, implementation partner, internal staff time, hardware, migration, training, decommissioning old toolsQuotes, [Finance Business Partner]
Run costsSubscriptions, infrastructure and data growth, operating FTE (fully loaded), support, renewalsBudget template cost model
Risk reductionChange in expected annual loss or in risk rating for each referenced riskRisk register, risk owner, quantification where used
Cost avoidanceRetired tools, reduced audit findings, insurance conditions met, avoided headcountContracts, procurement data
Non-financial benefitsRegulatory compliance, faster onboarding, customer requirements metSponsor, legal, sales
  • Quantified risk (where used): expected annual loss = [frequency of loss events per year] x [average loss per event]. Show baseline and residual values for each option and the method used, for example FAIR. See the Cyber Risk Quantification Guide.
  • Return on security investment: ([reduction in expected annual loss] + [annual cost avoidance] - [annual cost of the option]) / [annual cost of the option]. Report it alongside, not instead of, the qualitative risk change.
  • Time value: for multi-year cases, discount future costs and benefits at the rate [Finance] specifies and report net present value per option.
  • Optimism bias: the Green Book describes the proven tendency for appraisals to be over-optimistic. Adjust by increasing costs and durations and decreasing benefits by [x]%, and say so.
  • Sensitivity and switching values: show which assumption, if wrong, would change the recommendation (for example "if loss frequency is below [0.1] a year, option B becomes better value").

Worked example (illustrative figures)

A case for privileged access management estimates, with the risk owner, that a credential-based compromise of administrator accounts happens about once every [five] years ([0.2] a year) with an average loss of [2,000,000], giving an expected annual loss of [400,000]. With the preferred option the frequency falls to an estimated [0.05] a year, so expected annual loss drops to [100,000], a reduction of [300,000]. The option costs [150,000] a year over three years once one-off costs are spread, and retires a legacy password vault worth [30,000] a year. Return on security investment is ([300,000] + [30,000] - [150,000]) / [150,000] = [1.2]. The switching value shows that if the baseline frequency were below roughly [0.1] a year, the do minimum option would offer better value, so the case states the evidence behind the [0.2] estimate: [two internal incidents and one penetration test finding in three years]. The point of the example is the structure, not the numbers: every figure must have an owner and a source.

5. Commercial case

  • Sourcing route: [existing framework agreement / competitive tender / extension of current contract], with the procurement timeline.
  • Contract terms: term, renewal and price uplift caps, exit and data return, right to audit, security obligations on the supplier and breach notification times. See the Supplier Security Policy Template.
  • Supplier risk: due diligence outcome, concentration risk and what happens if the supplier fails or is compromised.
  • Access granted to the supplier: integrations, API keys, service accounts and administrative access the product or service needs, with owners and review dates.

6. Financial case

LineYear 1Year 2Year 3Funding source
One-off change cost[amount][amount][0][Change budget]
Added run cost[amount][amount][amount][Security run budget]
Savings and retirements[-amount][-amount][-amount][Retired contract]
Net budget impact[amount][amount][amount]

The financial case must confirm affordability within approved envelopes, show capital and operating treatment agreed with [Finance], and state where future run cost will be funded. A case that relies on savings must name the contract to be ended and its notice date.

7. Management case

  1. Governance: sponsor, steering group, delivery owner, and the decision forum for scope changes.
  2. Plan: phases and milestones, starting with a pilot or audit mode where the control can disrupt operations, with the rollback approach for each phase.
  3. Benefits realisation: for each objective, a measure, baseline, target, owner and date, reported to [Investment Board].
  4. Delivery risks and dependencies: skills, supplier capacity, change freezes, dependent projects and how each is managed.
  5. Post-implementation review: at [6 to 12] months, compare actual cost, risk reduction and benefits with this case and update the risk register.

8. Decision and approval

Decision requested: [Approve / approve phase 1 only / defer]. Approved by: [Name, role]. Date: [DD/MM/YYYY]. Conditions: [any]. Risk owner acceptance of residual risk: [Name, role]. Case reference: [ID], version [1.0].

If the decision is to defer or reject, the risk owner must record in the [Risk Register] that the risk remains at its current rating, whether it is now accepted above appetite, and the date the case will be reconsidered. A rejected case is still a risk decision and should be visible as one.

Implementation guidance

  1. Agree thresholds: set with [Finance] which investment sizes need a full case, a short case (sections 1, 3, 6 and 7) or none.
  2. Start from the risk: confirm the risk register entries and their owners before any vendor discussion, so the case is not written around a product.
  3. Collect costs from actual quotes and the cost model: include internal staff time and run cost; approvers reject cases that later double in cost.
  4. Test the case with a sceptic: ask [Finance Business Partner] or internal audit to challenge assumptions and switching values before submission.
  5. Track benefits after approval: add the benefits measures to the [Security Metrics] report. See the Security Metrics and KPIs Programme Guide.
  6. Measure the process: track approval rate, time from submission to decision, and the share of approved cases whose post-implementation review confirmed the expected risk reduction.

Common reasons security cases are rejected

  • Only one option: the case compares the product with doing nothing, so the approver cannot see whether a cheaper route meets the objectives.
  • Hidden run cost: year one licence is shown, but operating staff, data growth and renewals are not, and the next budget round reveals them.
  • Fear instead of evidence: industry breach headlines replace the organisation's own findings, incidents and risk register ratings.
  • Benefits nobody owns: objectives have no baseline, owner or date, so the post-implementation review cannot confirm anything.
  • Product before problem: the case was written with one vendor's proposal, and the options are framed to favour it, which finance and procurement usually notice.

Framework anchors: NIST CSF 2.0 GV.RM-01 (risk management objectives agreed with stakeholders), ID.RA-06 (risk responses chosen, prioritised, planned, tracked and communicated) and GV.RR-03 (adequate resources); NIST SP 800-53 Rev. 5 PM-3 and SA-2; NIST IR 8286 Rev. 1 and IR 8286B on recording risk responses and their projected cost in the cybersecurity risk register; and Principle B of the UK Cyber Governance Code of Practice, under which boards gain assurance that resources are allocated effectively to manage agreed cyber risks.

Related NHI Mgmt Group resources: Business Case Guide · IAM Business Case and ROI Guide · Security Budget and Investment Planning Guide · FAIR Model and Open FAIR Standard Guide · NIST IR 8286 Cybersecurity and ERM Integration Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.