Security budgets get cut the same way every year. A finance partner takes the total, compares it with last year and with a benchmark, and asks for a percentage back. The security leader argues for the total. Somebody splits the difference.

The problem is that the total is the only thing on the table. A single number can only be argued about as a single number, and a percentage cut applied evenly across a budget lands hardest on the lines with the least visible consequence, which are usually the ones that matter most.

The fix is structural, not rhetorical. Present the budget so that every line has a consequence a non-specialist can see, and so that cutting it becomes a decision someone records rather than a trim nobody owns.

The context finance is reading

Know the numbers your CFO has probably already seen. The IANS Research and Artico Search budget benchmark, from 587 CISOs, found security fell from 11.9% to 10.9% of IT spend, with average budget growth slowing to 4% from 8% the year before and more than half of respondents reporting flat or shrinking budgets.

Two readings matter. First, the ratio argument is getting weaker: benchmarking to a share of IT works when the share is rising, and it fell. Second, a falling share does not mean a cut. When IT spend rises faster than security spend, for example because of a large AI infrastructure program, the share falls even if security's absolute budget grew. If your CFO quotes the benchmark, agree with it as context and move the conversation to your own risks. The benchmark card has the detail and its limits.

The three tiers

Tier 1: Obligations

Spend the business already owes. Regulatory requirements, audit commitments, contractual security terms in customer agreements, insurance conditions, and certifications that sales depends on. Each line names the obligation it serves.

Cutting a tier 1 line does not save money in any real sense; it converts a known cost into a breach of a commitment. Finance teams understand this immediately when it is written down, because they deal with contractual obligations daily. They do not understand it when the line is labelled "GRC tooling".

Tier 2: Run cost

The cost of operating controls already in place: licences, staff, managed services, and maintenance. Each line names the control it keeps running and what degrades if it stops.

Tier 2 is where rationalization savings live. If two tools do the same job, cutting one is a good decision, and offering it before being asked buys credibility for everything else. The tool rationalization playbook on the buying desk is the method.

Tier 3: Risk reduction

New spend tied to a named risk that is currently outside the tolerance the board agreed. Each line names the risk, its current exposure, the tolerance, and when the spend brings it back inside.

This is where the budget meets the board's own decisions. NIST CSF 2.0 frames resourcing as a governance outcome: adequate resources allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies (GV.RR-03). The UK Cyber Governance Code of Practice asks boards to gain assurance that resources are allocated effectively against the agreed risk appetite. A tier 3 line is simply the cost of the appetite the board already set.

Why the obvious answer is wrong

The obvious answer is to argue harder: better threat briefings, more alarming peer incidents, a bigger total with room to concede. It works once. The second year, finance discounts the threat briefing, and the padding is found.

The second obvious answer is to anchor to a benchmark. That fails for the reason above: benchmarks describe other companies, and the current one is moving the wrong way for you.

The tiered structure works because it moves the argument away from the security leader. A cut to tier 3 is no longer the CFO overruling the CISO. It is the business choosing to leave a named risk outside the tolerance the board itself set, which is a decision that has to go back to the board, with a name next to it.

The discriminating variables

Can every line be placed in a tier?

The test: take your current budget and assign every line. Lines that fit nowhere are the first candidates to cut, and offering them is cheaper than defending them.

Does every tier 1 line name an obligation?

The test: for each line, write the regulation, contract, or audit commitment it serves. If you cannot name one, it is tier 2 or tier 3 and has to be argued there.

Is there an agreed tolerance behind each tier 3 line?

The test: each tier 3 line should point to a risk the quarterly board report already shows as outside tolerance. If the board has never seen the risk, the budget meeting is the wrong place to introduce it.

Has the risk acceptance been written down?

The test: if a tier 3 line is cut, is there a process to record that the risk was accepted, by whom, and until when? If not, the cut will be forgotten and the risk will be yours alone. The Record desk covers how to write that down.

Decision table

If finance asks forOfferWhy
A percentage across the boardTier 2 rationalization savings firstReal savings, offered before being taken
A cut to a tier 1 lineThe named obligation and who signs it awayConverts a trim into a commitment decision
A cut to a tier 3 lineA written risk acceptance for the named riskPuts the decision with the right owner
A comparison with a benchmarkYour own risks against toleranceBenchmarks describe other companies
A flat budgetTier 1 and 2 held, tier 3 resequenced with datesShows which risks wait, and how long

What a good budget page looks like

TierLineServesIf cut
1Annual SOC 2 auditCustomer contract terms, enterprise salesReport lapses, deals stall at security review
2Endpoint detection licencesDetection on corporate devicesDetection gap on laptops
2Overlapping email security toolDuplicate of existing controlNothing, offered as saving
3Immutable backup for order systemRecovery time risk, outside toleranceRisk stays outside appetite, acceptance required

One page, every line placed, every consequence written in words a director would use.

What changes the answer

A regulated sector. Tier 1 is larger and harder to argue with, which helps. Make sure each line still names the specific requirement, because "compliance" as a label invites the question of which one.

No board-approved appetite. Tier 3 has nothing to point at. Present tier 3 as candidate risks with a proposed tolerance, and ask for both the tolerance and the funding in the same paper.

A mid-year cut. Offer tier 2 first, then resequence tier 3 with explicit dates. Never let a mid-year cut land without a recorded acceptance for whatever it delays.

A new budget line for one event. That is a different conversation, about timing a single request to an event with a date, and it is covered in what actually triggers a security budget line.

Next steps

  1. Take this year's budget and place every line in a tier. Write the "if cut" column in plain words.
  2. Identify the tier 2 savings you would offer first, before anyone asks.
  3. Map each tier 3 line to a risk the board has already seen outside tolerance.
  4. Set up the written acceptance process for any tier 3 cut.
  5. For the agent-security angle on next year's budget, see the 2027 budget memo, and to lay out the three tiers start from the security budget justification template.