Skip to content

Security budget justification

One row per budget line: run or change spend, the risk it reduces, the business outcome it protects, the evidence behind it, and what happens if it is cut.

v1.0CSVCurrent as of November 18, 2026No signup, generated in your browser

A budget request described by what it buys reads as optional. This file describes each line by the risk it reduces, the outcome the business recognizes, and the consequence of cutting it, which is the trade a finance team is actually being asked to make. Spend is split into run, which keeps current controls operating, and change, which adds, expands, or retires something. Keeping the two apart shows what the current posture costs before anyone discusses what improving it costs.

Preview

The first 4 of 6 rows, rendered from the same data the download is built from.

Line itemSpend type (Run or Change)Annual cost (USD)Risk reducedBusiness outcomeEvidence the risk is realMeasure of successOwnerIf cut
blankblankblankblankblankblankblankblankblank
Example: Identity governance renewalRun120000Leavers keeping access to finance systems after their last dayClean access review evidence for the annual auditPrior-year audit finding on terminated user accessLeaver access removed within the policy windowIdentity leadReviews revert to spreadsheets and the audit finding is likely to repeat
Example: Just-in-time privileged access for productionChange85000A stolen engineer session reaching production with standing administrator rightsPassing enterprise customer security reviews that ask about privileged accessCustomer questionnaires asking for privileged access controls this yearShare of production administrator access granted just in timeInfrastructure leadStanding access remains and questionnaire answers stay qualified
Example: Retire standalone CSPMChange-48000None added; coverage moves to the existing cloud platformLower run cost from the next renewalOverlap register row and retirement reviewNotice given before the deadlineSecOps leadSpend continues for duplicated coverage

Formulas: The two TOTAL rows arrive empty. Set TOTAL RUN to SUMIF over the spend type column for Run, and TOTAL CHANGE to the same for Change. Present both figures side by side rather than a single grand total.

How to use it

  1. Fill the If cut column first. A line whose removal changes nothing observable is the first one finance will remove, and it should be.
  2. Classify every line as Run or Change, never both. A renewal with an expansion is two lines: the renewal at current scope is Run, the expansion is Change.
  3. Write Risk reduced as a scenario, not a category. Ransomware is a category; a contractor's reused VPN password reaching a file server is a scenario someone can picture.
  4. Every Evidence cell names something with a date: an audit finding, an incident, a customer requirement, a regulatory deadline, or a contract expiry. Lines with no evidence go to the bottom of the list.
  5. Record retirements and consolidations as Change lines with a negative cost, and link each to its overlap register row or retirement review.

A security budget a CFO cannot cut

Changelog

v1.0 (November 18, 2026):
First release. Nine columns, run and change totals, three worked example rows.

Common questions

What is the difference between run and change spend in a security budget?
Run spend keeps existing controls operating at their current level: renewals, staff, managed services, and maintenance. Change spend alters the program by adding a capability, expanding one, or retiring one. Separating the two lets finance see what the current posture costs before discussing what improving it costs, which is the order most budget reviews want.
Why does the budget template ask what happens if a line is cut?
Because the consequence of removal is the argument finance weighs. A line described only by what it buys reads as optional. A line stating which audit finding repeats, which customer requirement goes unmet, or which control lapses gives the CFO a concrete trade to accept or decline, and puts that decision on the record.
Should a security budget justification include savings?
Yes, as Change lines with a negative cost. Retirements and consolidations listed next to new requests show the program funding part of its own growth, and they keep the net figure honest. Link each saving to the overlap register row or retirement review behind it, so every number has a recorded decision.

Filed under Budget & Board.