Name a leader, a spending level, and a staffing level before your budget review. Each is a short record you can write in an afternoon and read aloud in one line. Together they answer who owns security, what it costs, and who does the work.
- Leader (OC.5.1): one named person in a leadership role, with their role and the decisions they can make without asking again
- Spending (OC.5.2): IT and security spend as raw numbers and as a percent of total expenditures, with the 4 to 7 percent band of your IT budget stated on its own
- Staffing (OC.5.3): IT and security headcount as raw numbers and as a percent of total staff, with internal staff and contracted work made clear
- Keep all three in one file so a reviewer can see your position at a glance
- Name any gap yourself first — a gap with a plan attached beats a defended number
Why this post exists
A budget review on IT security goes badly when nobody can answer three simple questions. Who owns security here? What do we spend on it? Who does the work? You should be able to name all three before the meeting starts, in writing, from one page.
A baseline for small and medium organizations puts those questions in a single place. The Canadian Centre for Cyber Security publishes them as separate controls you can satisfy with a short set of records. Each one is a document you already have or can write in an afternoon.
Three records matter more than the rest for a revenue leader walking into a budget meeting. A named leader. A spending level. A staffing level. This post tells you what each record contains, where it lives, and what to say when someone challenges it.
Two facts shape the meeting. Cybercrime is the cyber threat most likely to affect Canadian small and medium organizations. And industry analysis says organizations typically spend up to 13 percent of their IT budget on cyber security, while recommending that organizations expend 4 to 7 percent of their IT budget on it. That gap is where your budget conversation starts.
The three records to name before the review
You are not building a security program from scratch. You are producing three short records that let a reviewer see your position at a glance. Together they answer ownership, money, and people.
Record 1: the named leader
A named leader record is a one-line assignment. It says who in a leadership role is specifically responsible for IT security in your firm. The control is plain: identify someone in a leadership role who is specifically responsible for your IT security. That is control OC.5.1.
The title matters less than the responsibility. In a small firm the name might be the managing partner or the operations lead. What must not happen is a name like "everyone" or "the team." A shared name is not a name.
Write the record with three fields: the person, the role they hold, and what decisions they can make without asking again. The last field is the one that matters in a review. If the named leader can approve a tool, set a password policy, and accept a vendor's terms, then the budget has a decision-maker attached to it.
Bring the record to the meeting as a single line you can read out loud. A reviewer who hears a name and a responsibility immediately knows where follow-up questions go.
Record 2: the spending level
A spending level record shows what your firm spends on IT as a whole and on IT security specifically. The control asks you to identify those financial spending levels as raw numbers and as a percent of total expenditures. That is control OC.5.2.
Raw numbers alone will not survive a review. A percentage alone hides the size of the base. Carry both. If your total expenditure figure is drawn from your annual accounts, say so. If the security slice is an allocation rather than a separate cost center, say that too. Reviewers accept an honest allocation; they do not accept a number that cannot be rebuilt.
The useful comparison comes from the same page. Industry analysis indicates that organizations typically spend up to 13 percent of their IT budget on cyber security, and recommends that organizations expend 4 to 7 percent of your IT budget on cyber security. So your security figure sits against a band, not against zero.
Here is how that reads in a meeting. If your security spend is inside the recommended band, you say so and you move on. If it sits below the band, you say what you are buying with the difference before you ask for more. If it sits above, you say which risk you chose to fund.
One caution: the spending record's percent uses total expenditures as its base, while the 4 to 7 percent band uses your IT budget. Mixing the two bases is the fastest way to lose a room. State the base every time you state the figure.
Record 3: the staffing level
A staffing level record shows how many people work on IT and how many of them work on IT security. The control asks you to identify your internal staffing levels for IT and IT security, as raw numbers and as a percent of total staff. That is control OC.5.3.
Again, carry both figures. In a small firm the raw numbers might be one person, or one person who also runs the phones. That is a fine answer. The percent figure puts it in context for a reviewer who is comparing across firms.
The record should also name whether those people are internal staff or a contracted service. A managed provider can cover a lot of ground, but it does not remove the leadership assignment in your first record. Someone in your firm still owns the outcome.
When you present staffing, pair it with the spending record. A reviewer will read them together and ask why one moved and the other did not. Have that answer ready.
Here are the three records side by side:
| Record | What it shows | Form it must take |
|---|---|---|
| Leader (OC.5.1) | Who is responsible for IT security | A named person in a leadership role |
| Spending (OC.5.2) | What you spend on IT and on IT security | Raw numbers and percent of total expenditures |
| Staffing (OC.5.3) | Who does IT and security work | Raw numbers and percent of total staff |
How to write each record so it survives questions
A record survives a review when someone who did not write it can answer three follow-ups. Where did this come from? Who owns it now? What would change it? Build each record with those three answers in mind.
For the leader record, attach the source of the assignment. It might be a board minute, an email the partner approved, or a line in the employment description. The point is that the name came from a decision, not from a guess. Also write down what happens if that person leaves. A record with no successor path breaks the moment the person changes roles.
For the spending record, attach the base. Write the period the figure covers and where the totals come from. If you split IT security out of a general IT line, show the split logic in one sentence. If some security costs sit in another department's budget, list them so the total is complete. A reviewer who cannot rebuild your number will ask you to rebuild it in the room.
For the staffing record, define the unit. Does one person part-time on security count as one person, or as a fraction? Pick a convention, write it down, and use it for every figure in the record. Consistency matters more than the specific convention you pick.
Keep all three records in one file. When the review is scheduled, you should be able to open one document and read the three answers without searching.
What to say when the numbers are uncomfortable
Most budget reviews on IT security turn on a gap. Your spend sits outside the recommended band, or your staffing figure is thin, or the named leader is also the person with the least time. The review goes better when you name the gap yourself first.
If your security spend is below the recommended 4 to 7 percent of your IT budget, do not defend the number as correct. Say where it sits, say what you are funding at that level, and say what the next increment would buy. A reviewer can work with a gap that has a plan attached.
If your spend sits above the band, explain the risk you chose to fund. Maybe your systems hold data that would hurt if it leaked. Maybe a client or insurer required it. The reviewer's real question is not "why so much" but "what did we get."
If staffing is one person, say what that person cannot do. A single person can own the leader record and still not cover every control. Naming the limits is stronger than pretending coverage.
The threat picture gives you a shared starting point. The Canadian Centre for Cyber Security notes that the National Cyber Threat Assessment 2018 judges cybercrime to be the cyber threat most likely to affect Canadian small and medium organizations. You can say plainly that the most likely event on the board's mind is the one your budget line is meant to reduce.
If the sources leave a question open, such as what your firm's own correct percentage should be, ask your named leader and your finance lead to set it together.
A short walk-through of a completed set
Take a small professional services firm with three records ready for review.
The leader record names the managing partner. It says the partner can approve security tools, set access policy, and sign vendor terms. It names the operations lead as the standing backup.
The spending record shows IT spend and security spend as raw numbers and as a percent of total expenditures for the last financial period. The security figure, restated as a percent of your IT budget, sits inside the 4 to 7 percent band drawn from the same baseline page. The split logic sits in one sentence underneath.
The staffing record shows one full-time person responsible for IT and a named security service engaged under contract. The raw figures sit next to the percent of total staff. The convention for part-time security work is written in the footnote.
In the room, the partner reads the three lines in order: who owns it, what it costs, who does the work. Every follow-up question lands on a field that already exists. The review becomes a discussion of the next increment, not a search for missing facts.
What to bring, and what to leave out
Bring the three records, one page, in that order. Bring the base figures behind the spending record so you can rebuild the number if asked. Bring the assignment source for the leader record.
Leave out the tool list. A product tour answers a different question, and it pulls the meeting away from ownership and money. If a reviewer asks what you use, answer briefly and return to the three records.
Leave out the incident history unless asked. It belongs in a separate conversation with its own prep.
Leave out any promise you have not funded. A commitment made in a budget review becomes a number next year.
Device posture can come up, and it should be answered from a record rather than from memory. The NCSC device security guidance exists to help organisations choose, configure and use devices securely. If a reviewer asks how you handle laptops, point to the guidance you follow and the person who owns it. That is your leader record doing its job.
Similarly, if someone raises the risk of old machines on the network, answer from your assessment rather than from a headline. The Duo guide puts the exposure plainly: vulnerable laptops or desktops accessing corporate resources exposes organizations to potential attacks, financial damage and compliance issues. Connect that sentence to the leader who decides when a device is replaced.
Related guides
Quick FAQ
What if we have no separate security budget line? Show the security costs inside the IT total and state that they are allocated rather than separated. The control asks for spending levels as raw numbers and as a percent of total expenditures. Note the allocation method in one sentence so the figure can be rebuilt.
What if the named leader also runs sales? That is fine. The control asks for someone in a leadership role with specific responsibility for IT security, not for a dedicated security role. What matters is that the assignment is written, the decisions are named, and the backup is clear.
Do the three records have to live in one document? They should be kept in one file, as the rest of this post recommends. A reviewer who asks for all three in one sitting should not wait while you open four systems.
How often should we update them? Update the leader record whenever the person or role changes. Update the spending and staffing records whenever the underlying figures change, and always before a budget review. A record that is right but stale still reads as missing.
Who should sign off on the set? The named leader signs the set. If your firm has a finance lead who owns the base figures, have them confirm the spending record before the meeting. Two signatures are cheaper than one correction in the room.
What if our spend sits below the recommended band? State where it sits, state what it funds, and state what the next increment would buy. The band comes from industry analysis recommending that organizations expend 4 to 7 percent of their IT budget on cyber security, so a gap with a plan is a normal starting point for a discussion, not a failure.
Can a contracted service be the named leader? The control asks for someone in a leadership role who is specifically responsible for your IT security. A service provider can do the work, but your firm still needs a person who owns the outcome and makes the calls.
Closing note for the person walking into the room
You are not being asked to prove the firm is secure. You are being asked to show that three things exist on paper: a name, a number, and a headcount. Get those three right, put them on one page, and the budget review becomes a conversation about what to fund next.
Start with the leader. Everything else attaches to that name.