Framework

How to Build and Defend a Cybersecurity Budget

Build a cybersecurity budget by pricing the work needed to meet your commitments and address the risks your company has prioritized. Give leadership a choice between funded plans, with the work and exposure each option leaves open.

By Nick Shevelyov 6 min read

How do you size a cybersecurity budget that the board will actually fund?

Separate the work you need to keep operating from decisions about new investment. Baseline costs might include staff time, renewals, and services the business relies on today. Upcoming decisions might include a customer assurance commitment, a migration, or a recovery gap. Keep the cost of operating a control visible after the initial purchase.

Use the risk register to pull the issues that need funding, a decision, or more evidence. Ask the business owner what changes if the issue waits and the delivery team what work can fit. NIST IR 8286B describes prioritizing risk based on enterprise objectives and recording information about the chosen response and its cost.

Estimate the whole cost

Category Include in the estimate
People and capacity Staff time to implement, run, review, and troubleshoot the control. Identify which work moves if the same team takes this on.
Tools and services Quoted scope, licenses, onboarding, integration, ongoing support, and renewal or exit cost.
Testing and assurance Testing access, evidence preparation, specialist or practitioner fees when applicable, and follow-up work.
Transition Migration time, temporary overlap, training, and the time needed to verify the replacement works.

If you compare internal delivery with a provider, ask who covers the same systems and hours in each option. Use the fractional CISO scope template when a quote includes leadership or follow-up responsibilities.

How to allocate by threat and risk posture

Use the same decision criteria for competing requests. Record the obligation or business scenario, current safeguards, proposed result, cost and capacity, and remaining exposure. If your team can defend a financial estimate, record the inputs and show how the result changes under different assumptions. The annual loss expectancy calculator can help estimate average annual loss for a defined scenario. When evidence is thin, give leadership the specific consequence and the test that would narrow the uncertainty.

Worked budget request

A fictional software company restored its database during a recovery exercise, but the application still depended on configuration that the team could only reach in production. The sponsor needs to decide how much engineering capacity to reserve before the next major release.

Option What it costs the team What it addresses What remains
Test the current workaround One scheduled test window and the platform team’s time. Measures how long the existing recovery path takes and where it fails. Manual dependencies remain. A failed test still requires a response.
Repair the dependency and retest Engineering capacity to make approved configuration recoverable, plus a separate test window. Can demonstrate whether the team can restore a usable service within the agreed target. The result applies to the tested service and conditions. Other services need their own evidence.
Defer to the next planning cycle Preserves capacity for the current release. Maintains the current operating plan. The recovery gap stays open. The authorized risk owner needs a review date and a trigger for earlier action.

The request is to fund the second option with named engineering capacity. The acceptance test is a timed recovery of the application and a sample transaction within the agreed data loss and downtime limits. The sponsor can compare that result with the cost and tradeoff at the next board or executive review.

Sizing for growth and exits

Reopen the estimate when the company adds a service, changes its dependencies, enters a new customer commitment, or materially changes the operating team. Ask which costs scale with volume, which need a step up in staffing or coverage, and which fall away after a migration. Keep recurring costs and one-time project costs separate so leaders can see the future baseline.

Common budget mistakes

Check for costs counted twice, savings that depend on work nobody has capacity to do, and a recovery or compliance commitment left uncovered after a cut. When a lower-cost option transfers work to another team, get that owner’s estimate and agreement before presenting the saving. Keep the request tied to an outcome and track it in the remediation tracker.

If the team needs a clearer baseline for its investment choices, vCSO.ai’s scoped assessment and fractional leadership service can help review evidence, prioritize actions, and support executive decisions.

Questions & answers

How do I size a cybersecurity budget from scratch?

List the controls and services you must keep operating, upcoming obligations, and the highest-priority risk decisions. Estimate staff time, one-time expense, recurring expense, and dependencies for the options. Use those estimates to build an operating baseline and a set of investment choices.

What should a cybersecurity budget proposal include?

Describe the business exposure or requirement, the decision needed, the available options, the full cost and staff capacity, and what remains exposed. Name the owner and the evidence that will show whether the investment worked.

How do you decide what to cut?

Check contractual and operating commitments, renewal terms, and whether the work can be restarted. Show what risk or workload each proposed cut shifts to another team and who has authority to accept it.

Ready to turn this into a working plan?

Our team helps growth-stage companies, PE/VC sponsors, and cybersecurity product teams translate security questions into board-ready decisions. First call is strategy, not vendor pitch.

Scope an assessment