Growing regulatory demands and business dependence on technology are increasing pressure to strengthen cybersecurity. Yet the problem is rarely the number of specialists alone. More often, organisations lack clear ownership, processes and the ability to act effectively. For many, a well-designed operating model that combines internal and external expertise works better than building a large in-house department.
Cybersecurity is a system of capabilities, not a headcount
Mature cybersecurity spans several areas: governance, risk management, access control, vulnerability management, monitoring, incident response, protection of infrastructure and data, and business continuity.
It is hard to expect a small team to be expert in governance, IAM, cloud, SIEM, EDR/XDR, supplier security, regulation and disaster recovery at the same time. Keeping all these skills on the payroll is often disproportionate to a company’s needs.
Clear ownership matters most
Problems arise when an organisation has security tools but no process owners. The firewall runs, backups are made and EDR reports events, yet nobody knows who owns risk, priorities, incidents, suppliers or reporting to management.
The first question should therefore be not “how many people do we need?” but “which capabilities must we maintain, and who is responsible for them?”
Keep a small core within the organisation
A company should retain internal responsibility for decisions, priorities and risk acceptance. That does not mean every task must be performed by its own staff.
In practice, a small management core is often enough — for example, a person responsible for IT or a vCISO function — supported by specialist partners.

What is worth sourcing externally?
The easiest capabilities to scale are those needed periodically or requiring deep specialisation. Examples include audits, security testing, architecture, SOC/MDR, vulnerability analysis, compliance support, incident response and business continuity planning.
This gives the organisation access to experts when it needs them, without maintaining a full team throughout the year.
Swipe sideways to see all columns.
| Stays within the organisation | Can be delivered externally |
|---|---|
| Business decisions and risk acceptance | A vCISO function and security programme management |
| Setting security priorities and budgets | SOC/MDR, monitoring and event analysis |
| Ownership of processes, systems and data | Audits, security testing and architecture reviews |
| Approval of policies, exceptions and risk levels | Vulnerability management and specialist analysis |
| Management accountability and compliance oversight | NIS2/DORA support, incident response and BCP/DR |
NIS2 and DORA do not automatically require a large department
Regulation increases organisational accountability and calls for more formal risk, incident, supplier and operational resilience management. It does not necessarily require a large department.
The key is to demonstrate that appropriate mechanisms exist, work, are monitored and improve over time. That calls for effective management and control, not necessarily a large organisational structure.
A hybrid model is often the most practical
For many midsize companies, an effective model keeps accountability and decisions in house. A vCISO or security governance function leads the programme and roadmap, specialist partners provide selected skills, and managed services support security operations.
As a result, cybersecurity becomes an ongoing organisational capability rather than a collection of tools and one-off projects.
Do not start by asking how large the security department should be
A better question is: which security capabilities does our organisation need, and how can we provide them continuously, measurably and at a proportionate cost?
Only then should the organisation decide which skills to build internally, which to buy as a service and which to bring in periodically. A well-designed operating model can provide greater resilience than a large department with no clearly assigned responsibilities.



