The problem: Security is expected to keep the company safe, but it has no budget of its own. Each tool, each person, and each fix has to be asked for, one team at a time. The answer is often, “Not this year.”
Words used here: a budget is the money set aside for a purpose. A business case is a short note that explains why a spend is worth it, in terms of money, time, or risk.
Think of a house manager with an empty purse
A family asks one person to keep the house safe. That person has no money of their own. For a new lock, they must ask the parent who pays for the doors. For smoke alarms, they ask the one who pays for the kitchen. Each person has their own plans for the money, and each asks, “What do I get for this?” The new lock waits.
What it looks like at work
Security asks for a tool that would catch stolen logins. Leaders ask, “What do we get for it?” The answer is full of words about threats and technology. The sales team asks for a tool that will help win clients, and the answer is clear: more sales. The sales tool gets the money. A year later, there is a stolen login, and the same leaders ask, “Why did we not have protection?”
- 11. The askSecurity asks for a tool or a person
- 22. The question“What do we get for the money?”
- 33. The answerWords about threats and technology
- 44. The choiceSales or delivery gets the money
- 55. Next yearSame ask, same gap
Both sides are half right. Leaders are right that money is limited and each spend must show a gain. Security is right that the basics must be funded. What is missing is a way to show the gain in words and numbers that leaders already use.
You will notice it when:
- Every security need needs a new approval.
- Security’s asks are in technical words, not business words.
- The money comes from another team’s budget, so that team has a say.
- Basic protection is bought only after an incident.
- Security is asked to “do more with the same money” each year.
What exactly needs fixing
The first fix is not a bigger budget. It is a clear, short ask that leaders can say yes to. This card shows the whole problem on one page:
Every security need becomes a begging round, and basic needs stay unfunded.
The yearly budget talks, project plans, and each team's own budget.
Basic protection waits until after an incident, and then costs more.
- Unfunded basics
- Late tools
- Repeat audit finding
- Costly rush buy
- 11. Show the loss
- 22. Link to demands
- 33. Ask for little
Who fixes it: security lead and CFO
By when: before the next budget
A blank copy of this card is in the Tools section.
Why it happens
- Security does not make money. So it is seen as a cost, not as a gain.
- The benefit is a thing that does not happen. It is hard to show a loss that was avoided.
- Asks are in technical words. Leaders cannot compare them with a sales request.
- Asks are big and vague. “We need a full security programme” is easy to put off.
- Nobody links security to what the business already needs. Client demands and audits do not reach the budget talk.
- Security often asks only once a year. It misses the planning time.
What happens if you ignore it
The basics stay unfunded, and everything gets paid for later at a worse price.
- Basic protection arrives only after an incident, and costs more in a hurry.
- Audit findings repeat, because the money for the fix was not agreed.
- Security stays small, and the team has to say no to everyone.
- Leaders see security as a blocker, and not as a partner.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Very likely. It is one of the most common complaints of security teams. |
| Worst case? | A preventable incident, in a year when the money was refused. |
| What does it cost? | A rushed purchase after an incident, and lost trust. |
| What if we wait? | The same ask comes back next year, and the gap is bigger. |
| What does the fix cost? | A few days to prepare a short ask in business words. |
How to fix it, step by step
Make the ask small, clear, and tied to something leaders already care about.
- Describe a bad day in plain words. What happens if this goes wrong: how many hours stopped, which client affected, what it costs to put right. Use ranges and honest guesses, not exact numbers.
- Tie each ask to something already demanded. A client contract, an audit finding, a law, or an insurance question.
- Rank the asks. Pick the top three. Put the cheapest, most useful one first.
- Give each ask a price and a date. What it costs, what it needs, and when the benefit starts.
- Offer options. A full version, a smaller version, and a stop-gap.
- Ask in the planning window. Not after the budget is set.
- Report what the last spend gave. Show one clear before-and-after from last year’s money.
- Look for shared budgets. Some work can be paid together with IT or delivery, if it helps them too.
The picture shows the three moves that change the answer. Do them in this order.
Who to bring in: The head of security, the finance lead (or CFO), the head of IT, the head of delivery, and one leader who has seen a security incident.
Tools and templates
A one-page ask
| Field | Write here |
|---|---|
| What we want | One line, in plain words |
| What a bad day looks like | Hours stopped, clients affected, cost to fix |
| Why now | The client demand, audit finding, or law behind it |
| Cost | A number, with what it includes |
| Options | Full, smaller, stop-gap |
| What we get | What changes on day one, and in 3 months |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a leak, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to the finance lead
Subject: Three small security asks for the next budget
Hi [name]. Before the next budget is set, I would like 20 minutes to show you three small security asks. Each one is tied to something we already need: a client demand, an audit finding, or a risk we have seen. I will bring a one-page version, with the cost and the benefit for each. I would like your view on which one to do first.
Field tip
Do not ask for a big security budget. Ask for three small things, each with a price, a reason, and a date.
Words used in this chapter
- Budget: the money set aside for a purpose.
- Business case: a short note that explains why a spend is worth it.
- Stop-gap: a temporary protection until the real fix is done.
- Planning window: the weeks when next year’s budget is being set.