Most security budgets are last year's spreadsheet plus inflation, so nobody can say which risk a line item reduces or what would break if it were cut. This template gives a reusable cost model for a security function: a line item structure covering people, tools, services and projects, a split between run (keeping current capability operating) and change (new capability), and a link from every line to the risk or obligation it serves. It follows the UK Cyber Governance Code of Practice expectation that boards gain assurance that resources are allocated effectively to manage agreed cyber risks, and NIST CSF 2.0 outcome GV.RR-03 on adequate resources. It is written for CISOs, security finance partners and heads of security operations preparing an annual budget. For the strategic side of investment planning, see the Security Budget and Investment Planning Guide.
How to use this template
- Replace text in square brackets, such as [Organisation], [CISO], [Finance Business Partner] and [currency], with your own names and values.
- "Must" indicates a mandatory requirement; "should" indicates a recommended practice where a documented exception may be justified.
- Build the line item register in section 5 first from last year's actual spend, not last year's budget. Actuals expose shelfware, unplanned contractor spend and services bought outside the security cost centre.
- Tag every line with a risk or obligation reference (section 6) before arguing about totals. A line with no reference is the first candidate for review.
- Figures in the worked examples are illustrative only. This template contains no industry benchmark ratios: if you use one, cite its source and as-of year in your submission.
- Use it with the Security Business Case Template for individual change investments and the Risk Register Template for the risk references.
1. Purpose and scope
This template sets out how [Organisation] plans, approves, tracks and reports the security budget for the financial year [FY YYYY]. It covers all spend whose primary purpose is information or cyber security, wherever it sits in the chart of accounts, including security tooling paid for by IT, cloud security services billed through platform accounts, and security work done by suppliers under wider IT contracts. Physical security, fraud operations and insurance premiums are [in scope / out of scope and reported separately by [Owner]].
2. Budget principles
- Risk linked: every line item must reference at least one risk in the [Risk Register], a legal or contractual obligation, or a named service the business depends on.
- Run and change separated: run costs keep existing capability at its agreed level; change costs create new capability or retire old. They are approved and reported separately.
- Fully loaded: tool costs must include the staff time to operate them; people costs must include on-costs, training and certification.
- Whole life: change items show at least [three] years of cost, including the run cost they add once delivered.
- Single view: security spend held in other cost centres is shown in the register with its owning budget, so the total is visible even where control is shared.
3. Roles and approval
| Role | Responsibilities |
|---|---|
| [CISO] | Owns the security budget, proposes the run and change envelopes, accountable for variance explanations. |
| [Finance Business Partner] | Owns the chart of accounts mapping, capex and opex treatment, forecasting cycle and accruals. |
| [Security Leads] | Own line items for their area (operations, identity, engineering, GRC), supply forecasts and renewal dates. |
| [Procurement] | Holds contract terms, renewal notice periods and supplier spend data. |
| [CIO / COO] | Approves the budget within their delegated authority and resolves shared cost disputes with IT. |
| [Executive Committee / Board] | Approves the envelope and receives the report in section 8, linked to risk appetite. |
4. Cost model structure
Every line item must be assigned one cost category, one type (run or change) and one capability area. The categories below are the standard set; add sub-categories rather than new top-level ones so years remain comparable.
| Cost category | Typical line items | Usual treatment | Run or change |
|---|---|---|---|
| People: permanent | Salaries, employer on-costs, bonuses, training, certification fees and renewals | Opex | Run (new roles start as change in year one) |
| People: contingent | Contractors, interim leaders, staff augmentation | Opex | Run or change by purpose |
| Tools: licences and subscriptions | SaaS security platforms, endpoint agents, identity, secrets and privileged access tools, threat intelligence feeds | Opex (subscriptions) | Run once live |
| Tools: infrastructure | Log storage and ingest, cloud compute for security tooling, hardware security modules, on-premises appliances | Opex or capex by asset policy | Run |
| Managed and professional services | MDR or MSSP, incident response retainer, penetration testing, red teaming, audit and certification fees | Opex | Run (recurring) or change (one-off) |
| Projects | Implementation partners, internal project staff time, migration and decommissioning | Capex where it creates an asset, otherwise opex | Change |
| Awareness and culture | Training platform, phishing simulation, campaigns, events | Opex | Run |
| Contingency | Unplanned incident costs, emergency remediation, price rises | Opex | Held centrally at [x]% of run |
- Capability areas: use the six NIST CSF 2.0 functions (Govern, Identify, Protect, Detect, Respond, Recover) so the report in section 8 shows where money sits against the framework the board already recognises.
- Fully loaded people cost: [base salary] x (1 + [on-cost rate]) + [training and certification allowance] + [equipment and overhead allowance].
- Tool cost of ownership per year: [licence or subscription] + [infrastructure and data ingest] + ([operating FTE] x [fully loaded cost]) + [support and integration services].
- Machine identity and data growth: licences priced per identity, endpoint or gigabyte grow with the estate. Forecast the driver (number of workloads, service accounts or log volume), not just the price. See the Non-Human Identity (NHI) Guide.
Worked example (illustrative figures)
A SIEM line shows a subscription of [120,000] a year. Adding log ingest and storage of [60,000], 1.5 operating FTE at a fully loaded [90,000] each ([135,000]) and an integration retainer of [15,000] gives a true annual cost of ownership of [330,000], nearly three times the licence. Recording the driver (for example [800] GB a day of ingest, growing [25]% a year as cloud workloads are onboarded) lets [Finance Business Partner] forecast next year's run cost before the renewal, and shows leadership that a cheaper licence with higher operating effort may not save money. Apply the same arithmetic to every tool above [threshold] before comparing options or proposing a cut.
5. Line item register
The register is the single source for the budget. It must hold one row per line item with at least these fields.
| Field | Description | Example (illustrative) |
|---|---|---|
| ID | Unique reference | SEC-TL-014 |
| Name | Plain description | Endpoint detection and response subscription |
| Category and type | From section 4 | Tools: licences; Run |
| Capability area | CSF 2.0 function | Detect |
| Owner | Named budget holder | [Head of Security Operations] |
| Risk or obligation reference | Register ID, law, contract or service | [R-023 Ransomware on endpoints]; [Cyber insurance condition] |
| Cost driver and unit | What makes the cost change | [Number of endpoints] x [unit price] |
| Budget, forecast, actual | By month or quarter | [Values] |
| Contract end and notice period | For renewals | [DD/MM/YYYY]; [90 days] |
| Consequence if cut | One sentence | [No endpoint telemetry for 3,000 devices; insurance condition breached] |
| Overlap flag | Other tools covering the same need | [Partly overlaps SEC-TL-022] |
6. Allocating spend to risk and obligations
- Each line item must be linked to the risk it reduces, the obligation it meets or the service it supports. Lines linked only to "best practice" must be reviewed by [CISO] before approval.
- For each top [10] risk in the [Risk Register], the register must show total run and change spend against it, so under-funded risks above appetite are visible. See the Cyber Risk Appetite Statement Template.
- Change items above [threshold] must have an approved business case using the [Security Business Case Template] that states the risk reduction expected and the run cost added.
- Where a risk treatment plan commits funding, the line item must cite the treatment plan reference. See the Risk Treatment Plan Template.
7. Forecasting, variance and in-year change
- Forecast cycle: line owners must update forecasts [monthly / quarterly] with [Finance Business Partner].
- Variance threshold: any line varying by more than [10]% or [amount] from budget must have a written explanation in the next report.
- Renewals: contracts must be reviewed at least [120] days before the notice date, checking usage, overlap and whether the risk reference still applies.
- Reallocation: moving funds between run and change, or between capability areas, above [amount] requires [CIO / COO] approval.
- Incident costs: spend on a declared incident is coded to [incident code] and drawn first from contingency, so post-incident reviews can report the full cost.
8. Reporting
[CISO] must report to [Executive Committee] at least [quarterly], consistent with the Cyber Governance Code of Practice expectation of formal reporting at least quarterly with tracked metrics. The report must include:
| Measure | What it shows |
|---|---|
| Budget vs forecast vs actual, run and change | Financial control |
| Spend by CSF 2.0 function | Balance across prevention, detection and recovery |
| Spend against top risks above appetite | Whether money follows risk |
| Change portfolio delivery (milestones met) | Whether approved investment is turning into capability |
| Tool utilisation (deployed coverage vs licensed units) | Shelfware and over-licensing |
| Run cost added by completed projects | Future budget pressure |
9. Review and approval
This template and the cost model are reviewed annually by [CISO] and [Finance Business Partner] before the budget round, and after any major incident, merger or change in regulation. Version: [1.0]. Approved by: [Name, role]. Date: [DD/MM/YYYY]. Next review: [DD/MM/YYYY].
Implementation guidance
- Collect actuals (weeks 1 to 3): pull 12 months of security-related spend from finance, procurement and cloud billing, including items outside the security cost centre.
- Classify (weeks 3 to 5): assign each item a category, run or change type, CSF function and owner; flag items nobody claims.
- Link to risk (weeks 5 to 7): add risk and obligation references with the risk owner; record the consequence if cut in one sentence.
- Find savings first: compare licensed units with deployed coverage and look for overlapping tools before asking for growth. Savings found here fund part of the change envelope.
- Build the change portfolio: rank change items by risk reduced against whole-life cost, each backed by a business case above threshold.
- Pilot the report: run one quarter's report on actuals before the budget is approved, so leadership sees the format and the gaps.
- Roll back safely: if the new structure cannot be mapped to finance codes in time, keep the old cost centres for approval and run this model as a parallel view for one year.
Framework anchors: NIST CSF 2.0 GV.RR-03 (adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities and policies), NIST SP 800-53 Rev. 5 PM-3 Information Security and Privacy Resources and SA-2 Allocation of Resources, and Principle B of the UK Cyber Governance Code of Practice. The idea of feeding known weaknesses into investment decisions also appears in NIST SP 800-65, which NIST withdrew in 2018, so use it as background only. For measures, NIST SP 800-55 Vol. 1 explains how to select and prioritise them. See the Security Metrics and KPIs Programme Guide.
Related NHI Mgmt Group resources: Security Budget and Investment Planning Guide · Security Business Case Template · Security Strategy and Roadmap Guide · Security Operating Model and Organisation Design Guide · Risk Register Template