
For CFOs: Tying Security Spending to Specific Risks
Security budgets are hard for CFOs to evaluate. The line items are technical, the vendors all claim to stop the same threats, and the costs keep rising. When IT asks for a new tool, it is difficult to judge whether it is essential or just appealing. When nothing bad happens, it is hard to know whether that was the spending working or simple luck.
A better approach is to require that every security line item point to a specific risk it reduces. That turns a list of products into a set of decisions you can actually evaluate. This guide shows how.
The framework behind it
The NIST Cybersecurity Framework 2.0 organizes cybersecurity around six functions, and the first one, Govern, is aimed squarely at leadership. Within it, GV.RM covers risk management strategy: establishing risk appetite and tolerance, and making sure cybersecurity risk management is part of how the enterprise manages risk overall. Under the Identify function, ID.RA covers risk assessment: understanding the threats, vulnerabilities, likelihoods, and impacts the organization faces.
Put simply, the framework says you should know your risks, decide how much of each you are willing to carry, and spend to bring the ones you cannot accept down to a tolerable level. That is a language finance already speaks.
Start with a short risk register
A risk register is a list of the things that could go wrong, how likely each is, and how bad it would be. It does not need to be elaborate. For a small or midsize business, ten to twenty entries is usually enough to start.
Write each risk as a business event, not a technical one:
- Ransomware stops operations for several days.
- A fraudulent wire transfer is sent after an email account is compromised.
- Customer or patient data is stolen and must be reported.
- A key system, such as the ERP or EHR, is unavailable and cannot be restored quickly.
- A former employee or vendor still has access and misuses it.
- A regulator or customer asks for evidence of a control we cannot produce.
For each, estimate likelihood and impact in simple terms, such as low, medium, and high. The impact estimate should involve finance, because finance understands what a week of downtime or a delayed shipment really costs the business.
Map every line item to a risk
Now take the security budget and ask, for each line, which risk on the register it reduces and how. For example:
- Backup and recovery service: reduces the impact of ransomware and system failure by allowing restoration.
- Email security and MFA: reduces the likelihood of account compromise, which drives wire fraud and data theft.
- Endpoint detection and response: reduces the likelihood that ransomware spreads and the time it takes to detect.
- Security awareness training: reduces the likelihood of successful phishing and payment fraud.
- Vulnerability scanning and patching: reduces the likelihood of attackers exploiting known weaknesses.
- Vendor access controls: reduces the likelihood of compromise through a third party. Our vendor management policy guide covers that side.
If a line item cannot be tied to a risk on the register, either the register is missing something or the spending is not necessary. Both are worth knowing.
Look for the gaps the other way
Now reverse the exercise. Go down the risk register and ask which line items address each risk. Some risks will have several controls. Others will have none.
A high likelihood, high impact risk with no controls is where the next dollar should go. A low risk with three overlapping tools may be a place to consolidate.
Ask better questions about new requests
When IT or a vendor proposes a new tool or service, ask:
- Which risk on our register does this reduce?
- Does it reduce likelihood, impact, or both?
- What do we have today that addresses the same risk, and why is it not enough?
- What would we stop doing or stop paying for if we adopt this?
- How will we know it is working?
- What does it take to operate, including staff time?
Good answers to those questions make a strong case. Vague answers usually mean the request needs more thought.
Fold compliance in
Some spending is driven by requirements rather than pure risk reduction. The FTC Safeguards Rule, HIPAA, and contract requirements such as DFARS 252.204-7012 all require specific controls. That spending still fits the model: the risk is failing to meet an obligation, with consequences that range from lost contracts to enforcement. Put those obligations on the register and tie the related spending to them.
In many cases, the controls that satisfy a regulation also reduce real business risk. MFA required by the Safeguards Rule also reduces wire fraud. Backups required by HIPAA's contingency plan standard also reduce ransomware impact. Showing those connections helps the spending make sense to everyone.
Decide what you will accept
Not every risk can or should be reduced to near zero. Part of risk management is deciding which risks the business will accept. That is a leadership decision, not an IT one, and it should be written down.
For each accepted risk, record why, who decided, and when it will be revisited. Insurance can transfer some residual risk, but cyber insurance applications often ask about specific controls, so acceptance and transfer need to be considered together. Our guide to the cyber insurance application walks through the questions carriers commonly ask.
Review it on a schedule
Risks change. New systems, acquisitions, new customers with security requirements, and changes in how attackers operate all shift the picture. Review the register at least annually and whenever there is a significant change to the business. Tie the review to budget planning so the two stay connected.
The outcome
When every dollar points to a risk, the CFO can explain security spending to the owner or board, IT can make its case in business terms, and the company can see where it is overspending and where it is exposed. It also makes conversations about cuts much more productive, because everyone can see which risks would rise as a result.
Our vCISO service works with leadership teams on this kind of risk planning, and our NIST framework page explains how CSF 2.0 is organized. If your IT team wants to see how controls line up across frameworks, our CIO guide to mapping controls to frameworks is a good companion. If you want to walk through your current security budget against your risks, book your free risk review.