Blog
A CFO's Guide to the Security Budget
Security spending is hard to budget for. The benefit is something that doesn't happen, vendors all claim their product is essential, and the requests from IT tend to arrive one at a time, each sounding urgent. For a CFO at a company of 50 to 250 people, it can feel like a cost with no bottom.
It doesn't have to. When I ran IT at a company of about 200 people, the security conversations with finance that went best weren't about fear or products. They were about a short list of controls, what each one protects, what it costs per person per month, and how we'd know it was working. This post gives you that structure.
Start with what you already pay for
Before approving anything new, find out what you already own. Security features are often bundled into licenses the company already pays for and then never fully switched on.
- Your Microsoft 365 or Google Workspace license may already include MFA enforcement, better email filtering, device management and, at some tiers, endpoint protection (EDR, software that watches computers for suspicious behavior). Microsoft 365 Business Premium, for example, includes Microsoft Defender for Business.
- Your IT provider's contract may include services like patching, backup monitoring or phishing training that aren't being fully delivered or reported.
- Your cyber-insurance policy may include access to discounted or free services from the carrier's partners, such as training platforms or scanning.
A one-hour review of existing licenses and contracts often finds real savings, or real capability already paid for.
A simple framework: the carrier list
You don't need to invent priorities. Cyber-insurance carriers have already done it, based on what they see in claims. In our review of 13 public carrier applications (November 2026), the controls asked about most often were:
- Regular backups (13 of 13), and especially isolated backups (10 of 13) and restore testing (9 of 13).
- Multi-factor authentication (12 of 13), especially for remote access (11) and email (10).
- Security training and phishing tests (12 of 13).
- A written incident-response or continuity plan (11 of 13).
- Encryption of sensitive data (11 of 13).
- EDR by name (9 of 13).
- Patching on a stated timetable (8 of 13), email filtering (8 of 13), and vendor management (8 of 13).
If your budget covers these well, you're in a strong position with carriers, with customers' security questionnaires and, more importantly, against the most common real-world attacks. Anything outside this list should face a higher bar.
How costs usually work
Most security spending for a company your size falls into a few shapes:
Per user or per device, per month. MFA (often already included), EDR, managed detection and response (MDR, people watching alerts around the clock), email security and training platforms. These scale with headcount, which makes them predictable.
Per amount of data. Backup services are usually priced by storage. Isolated or immutable copies (backups that can't be changed or deleted) may cost somewhat more.
Projects. Replacing an out-of-support firewall, cleaning up old systems, rolling out DMARC (email authentication) or setting up network segmentation. These are one-time and can be scheduled.
People and time. Your IT provider's hours, an internal person's time, and periodic outside reviews.
Ask for each line in per-user-per-month terms where possible. It makes comparison easy and makes the total understandable to the rest of the leadership team.
Questions to ask before approving any security spend
- Which risk does this reduce, and which item on the carrier list does it map to? If it doesn't map to anything, why is it a priority?
- Do we already own something that does this?
- Who will operate it? A tool nobody watches is an expense, not a control.
- How will we know it's working? Ask for one or two numbers you'll see monthly: percentage of devices covered, last restore-test date, phishing report rate.
- What happens if we don't do it this year? Sometimes the honest answer is "not much," and that's useful to know.
Questions to ask your IT provider about cost
Your managed-service provider (MSP) is usually your biggest security line, whether it's labeled that way or not. Ask:
- What security services are included in our current monthly fee, and what's extra?
- What reports do we get, and how often? If the answer is "none," ask for a simple monthly summary.
- What would you recommend we add, in priority order, and what does each cost per user per month?
- What would it cost to fix each gap our insurance application or a customer questionnaire uncovered?
Our post on outsourced IT has a fuller questionnaire you can send.
Frame it as downtime, not fear
The best way I've found to make security spending make sense to a leadership team is to stop talking about hackers and start talking about downtime. Ask a simple question: if we couldn't use email, files or the accounting system for a week, what would that cost us in revenue, overtime, missed deadlines and customer goodwill?
You don't need a precise number. A rough estimate, made by the people who run the business, puts security spending in proportion. If a week of downtime would be very costly, a modest monthly spend that shortens recovery from weeks to days is easy to justify. If it wouldn't be, you've learned something too.
Insurance is part of the budget, not a substitute
Cyber insurance helps pay for recovery, legal help, notification and some losses. It doesn't prevent an incident, doesn't restore your systems and doesn't recover your customers' trust. And as other posts in this library explain, coverage depends on the controls you described on your application actually being in place.
Treat the premium and the controls as one budget. Better controls can improve your terms at renewal; weaker controls can raise premiums, reduce limits or make coverage harder to get.
A sensible annual rhythm
- Quarter one: review licenses and contracts, and agree on the year's priorities against the carrier list.
- Before renewal: gather evidence for each control and fix gaps.
- Every month: a one-page report from IT with a few numbers that show controls are working.
- Once a year: an outside review, a tabletop exercise and a refresh of the incident plan.
What to do Monday morning
- Ask IT for a list of every security-related license and service you currently pay for, with what's switched on and what isn't.
- Map current spending to the carrier list above, and mark the gaps.
- Ask your IT provider for prioritized recommendations with per-user-per-month costs.
- Estimate, roughly, what a week without email and files would cost the business, and use that to set the scale of the budget.
- Agree on three or four monthly numbers IT will report, so you can see the spending working.
Shorehelm's readiness assessment ends with a prioritized gap list a CFO can budget against.