Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A defensible security budget starts from the risk register and regulatory deadlines, splits spending between people, tooling, and services, and shows what each pound buys.

How Do You Plan a Security Budget?
Security budgets fail at the same point every year: the moment a finance director asks what happens if a line is removed, and the answer is a shrug. A budget built from last year’s renewals plus whatever the team has been promised cannot answer that question. A budget built from the risk register can.
The planning job is not to maximise the number. It is to produce a ranked set of commitments where each one connects to something the organisation already agreed matters.
Every credible line item traces back to one of these:
In most mid-sized UK organisations the split looks roughly like this:
| Category | Share | Notes |
|---|---|---|
| People | 40–60% | Salaries, recruitment, retention; the largest and least compressible line |
| Tooling and licences | 20–35% | Rising with data volumes; SIEM ingestion is frequently the surprise |
| External services | 10–25% | Penetration testing, managed detection, audit, incident response retainer |
| Training and certification | 3–8% | Cheapest retention mechanism available to most teams |
| Contingency | 5–10% | Incident surge costs and emergency remediation |
Industry benchmarks put security at somewhere between 5% and 15% of total IT spend, with regulated sectors at the upper end. Benchmarks are useful for sanity-checking a proposal and dangerous as a target: they say nothing about your threat exposure, your technical debt, or how much of your estate is already end of life.
Scare-driven budgeting works once. After that, a board that approved a seven-figure programme on the strength of a headline breach will ask what changed, and the honest measure is usually a set of risks moved inside tolerance. Present each proposal with the risk it treats, the expected change in exposure, and what happens if it is deferred by a year. Where a credible estimate exists, a return on security investment figure with its assumptions visible helps compare options against each other.
Revenue arguments are stronger than loss arguments and routinely underused. Certification that unblocks enterprise deals, security questionnaires answered without emergency work, and insurance terms improved by evidenced controls are all measurable in the finance system already.
Annual budgeting pushes teams towards tools, which can be bought in a quarter, and away from capability, which cannot. A three-year outline alongside the annual ask fixes some of that: year one builds visibility and fixes identity, year two automates response, year three matures detection engineering. It also exposes the running cost of this year’s purchase in next year’s figures, which is the number most teams discover too late.
Consider too whether a function should be built or bought at all. The economics of round-the-clock coverage usually favour a provider, as the outsourcing decision shows, and that choice changes the shape of the budget more than any single tool.
Plan the cut before you are asked. Decide in advance what survives at 80% and at 70% of the request, and be explicit about what the reduction buys in risk terms rather than protesting in general. The things worth protecting last are rarely the exciting ones: multi-factor authentication coverage, tested backups, log retention long enough to investigate, and patch management. Those four carry most incidents.
If external testing is one of the lines you need to size realistically, our penetration test services are scoped to a defined estate so the cost can be planned rather than estimated.
Published benchmarks cluster between 5% and 15% of total IT spend, with financial services and healthcare at the upper end. Treat that as a sanity check rather than a target. A company with an ageing estate, heavy regulatory exposure, or a recent incident may justifiably spend more, while a small cloud-native business with few data obligations may reasonably spend less.
Connect each request to a risk the board has already accepted as outside appetite, and show what deferring it costs in exposure. Pair that with the commercial arguments: deals that require certification, customer security reviews, and insurance terms. Avoid relying on breach statistics from other organisations, which boards discount quickly when nothing has happened to them.
A separate line with its own owner is preferable, because security spending buried in IT is the first thing cut when infrastructure costs rise, and it becomes impossible to report on. Many organisations keep a central security budget while charging project-specific security work to the projects that create the need, which keeps delivery teams accountable for the risk they introduce.
Multi-factor authentication coverage, tested and immutable backups, sufficient log retention to investigate an incident, and timely patching of internet-facing systems. These four address the attack paths behind most real intrusions and cost relatively little compared with advanced detection platforms. Cut depth in newer capabilities before cutting any of them.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.