CISO Org Chart Playbook: Security Team Structures
There is no single correct security org chart. The right shape depends on the size of the company, how regulated it is, how mature its security already is and how much it buys in. This playbook gives typical structures for a startup, a mid-size company and an enterprise, the trade-offs between reporting lines, and when to hire each core function.
To build a structure for your own company, with headcount, a budget split and job descriptions, use the Org Designer. Part of the CISO Resource Bundle. We give no headcount statistics here because we found no primary source we could verify.
Updated 22 November 2026
Org structures by company size
Startup or small company
One security leader, often a hands-on head of security rather than a full CISO, sitting under the CTO or CEO. Most specialist work is bought in.
- Head of security: identity, cloud configuration, endpoint basics, policies and customer security questionnaires.
- Bought in: managed detection and response, penetration testing, compliance automation and an external auditor for SOC 2 or ISO 27001.
- Borrowed: engineers who own security fixes in their own services, and IT for device management.
Focus: the controls customers ask about, and not losing the crown jewels.
Mid-size company
A CISO with a small leadership layer. Functions become distinct teams, each with a lead, and the managed service shrinks to out-of-hours cover.
- CISO, reporting to the CEO, CIO or CTO.
- Security operations: detection, triage and incident response, often with a managed partner for nights and weekends.
- Governance, risk and compliance: policies, risk register, audits, third-party risk.
- Security engineering and architecture: cloud security, network, secure design reviews.
- Identity and access: joiners, movers and leavers, privileged access, single sign-on.
- Application or product security: if you build software, threat modelling and secure development support.
Enterprise
A CISO with an office of their own, functions run as departments, and security leaders placed inside business units or regions.
- CISO office: deputy CISO or chief of staff, programme management, budget, metrics and board reporting.
- Business information security officers (BISOs): one per major business unit or region, with a line to the CISO.
- Security operations centre, incident response, threat intelligence and detection engineering as separate teams.
- GRC split into policy, risk, compliance and audit liaison, plus a third-party risk team.
- Identity and access management, cloud security, application security and, where relevant, OT security.
- Security awareness and culture.
Adjacent functions often sit elsewhere with a dotted line to the CISO: privacy (data protection officer), physical security, fraud, and business continuity.
Reporting lines: CEO, CIO or CRO
NIST CSF 2.0 says organisational leadership is responsible and accountable for cybersecurity risk (GV.RR-01). Who the CISO reports to decides how easily that accountability reaches them. Each line has trade-offs:
| CISO reports to | Strengths | Watch out for |
|---|---|---|
| CEO | Most authority; security is treated as a business risk; direct route to the board. | CEO time is scarce; the CISO must be ready to run at executive level. |
| CIO or CTO | Close to the technology and the people who fix things; faster delivery of technical controls. | Conflict of interest when security must challenge IT priorities or spending; risk can be filtered before it reaches the board. |
| Chief risk officer | Cyber is managed with other enterprise risks; strong fit in regulated sectors; independence from IT. | Distance from engineering; risk of becoming a reporting function without operational reach. |
| COO, CFO or general counsel | Ties security to operations, money or legal exposure; can give independence from IT. | The executive may lack technical context; priorities can tilt to cost or legal defensibility. |
Whatever the line, agree these in writing: direct access to the board or its committee, budget ownership, the authority to stop or escalate a risky change, and independence from the teams whose controls security assesses. The CISO role builder helps you write it down.
Core functions and when to hire each
| Function | What it does | Signs you need it in-house |
|---|---|---|
| Security leadership | Strategy, risk reporting, budget, board. | Customers ask for security reviews, you hold sensitive or regulated data, or you are raising money or preparing for a sale. |
| Governance, risk and compliance | Policies, risk register, audits, certifications, regulator contact. | Audits or certifications take more than a fraction of the leader's time; several regulations apply. |
| Identity and access | Accounts, single sign-on, multi-factor, privileged access, access reviews. | Joiner and leaver errors, many applications, admin rights spread widely. |
| Security engineering and cloud | Secure configuration, network design, cloud guardrails, tooling. | Several cloud accounts or a growing estate that changes daily. |
| Security operations and incident response | Monitoring, triage, investigation, response. | A managed service escalates more than the leader can handle, or you need people who know your environment during an incident. |
| Application or product security | Threat modelling, secure code review, developer support. | You ship software customers depend on, or security findings in code keep recurring. |
| Third-party risk | Assessing and monitoring suppliers. | Many suppliers hold your data or reach your systems; customers or regulators ask about your supply chain. |
| Threat intelligence and detection engineering | Tracking threats to you and turning them into detections. | A mature operations team that wants fewer, better alerts tailored to your threats. |
| Awareness and culture | Training, phishing exercises, security champions. | Many staff, repeated human-driven incidents, or a regulator or insurer expects a programme. |
The NICE Framework (NIST SP 800-181) describes cybersecurity work roles in detail if you need to write job descriptions for these functions.
Build your own org chart
The Org Designer turns five facts about your company (size, industry, maturity, regulatory pressure and budget) into functions, headcount per function, roles with KPIs, a first-year hiring plan and job descriptions you can edit. Its numbers are planning heuristics, labelled as such.
Then check the budget behind it with the Security Budget Benchmark, and present the plan with the CISO Board Deck Template.
Frequently asked questions
How should a security team be structured?
Most security teams group work into a handful of functions under the CISO: governance, risk and compliance; security operations (detection and response); security engineering and architecture; identity and access; and application or product security. How many people each function has, and how much is bought in from managed services, depends on company size, industry, regulation and maturity.
Who should the CISO report to?
No rule fixes it. Reporting to the CEO gives the most authority and board visibility. Reporting to the CIO keeps security close to the technology it protects but can create a conflict when security has to challenge IT. Reporting to a chief risk officer suits regulated firms that manage cyber as an enterprise risk, but can pull the CISO away from engineering. Whatever the line, agree board access, budget authority and the right to escalate in writing.
When should a company hire its first security person?
Common triggers are customers asking for security reviews or a SOC 2 report, handling regulated or sensitive data, raising money or preparing for an acquisition, or a first serious incident. The first hire is usually a hands-on head of security who covers identity, cloud and compliance and buys in monitoring and testing.
What is a BISO?
A business information security officer is a security leader embedded in a business unit or region. They translate the unit's plans into security requirements and carry its risks back to the CISO. They are common in large, decentralised organisations where one central team cannot know every business well.
Should security operations be in-house or outsourced?
Many smaller organisations buy managed detection and response first, because round-the-clock monitoring needs more people than a small team has. As the organisation grows, teams often keep incident response leadership, detection engineering and threat intelligence in-house and keep a managed service for out-of-hours coverage. The Org Designer lets you model the mix.