Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Building a security team means sequencing hires against the risks you actually carry, deciding what to outsource, and designing roles people will stay in rather than burn out of.

How Do You Build a Security Team?
The first security hire in most organisations is made after something went wrong. That is a poor moment to design an operating model, and it explains why so many teams end up shaped around the previous incident rather than the current risk. A better approach starts with two questions: what would hurt this business most, and which of those jobs genuinely has to sit inside the company.
What follows is a sequencing problem. Headcount arrives slowly, and each hire should close the largest remaining gap rather than reproduce a textbook org chart.
For a mid-sized UK organisation of a few hundred staff, a workable order looks like this.
Governance, risk, and compliance work often arrives as a fifth hire, earlier in regulated sectors. Resist the temptation to hire a specialist for a technology you have not yet deployed.
Three functions are routinely outsourced, with good reason. Round-the-clock monitoring is expensive to staff and easy to buy. Offensive testing benefits from independence and from testers who see many environments. Digital forensics is needed rarely and badly when it is needed, so a retainer beats a dormant internal skill.
Three functions resist outsourcing. Risk ownership cannot leave the organisation. Architecture and engineering decisions need people who know your systems and your politics. And incident coordination, as distinct from technical analysis, has to be led by someone with the authority to stop a production deployment at two in the morning.
A blended model is normal: an internal lead directing an external managed detection and response service, with internal engineers handling containment on systems they own.
Below roughly fifteen people, a flat team reporting to the security lead works and anything else creates overhead. Above that, most organisations split along three lines: a build function covering engineering and architecture, a run function covering detection, response, and vulnerability management, and a govern function covering risk, compliance, and assurance. Embedding security engineers in product teams works where engineering culture already supports it; a central team with named partners for each product area works almost everywhere else.
Whatever the shape, write down who decides. The most common structural failure is not a missing box on the chart but an unclear answer to “who can accept this risk”.
The UK pipeline is wider than job adverts suggest. NCSC-certified degrees and the cybersecurity technologist and technical professional apprenticeship standards produce capable juniors; the CyberFirst programme reaches students earlier. Chartered status through the UK Cyber Security Council gives experienced staff a progression route that is not management.
Certifications help you filter, not select. A CISSP signals breadth and five years of experience, GIAC certifications signal tested hands-on skill in a narrow area, and CREST or Cyber Scheme registration matters for testers working under UK schemes. None of them tells you whether someone will work well at three in the morning with incomplete information.
Retention is mostly a design problem. On-call rotations thinner than one in four burn people out, incident work without recovery time produces attrition within eighteen months, and a team whose only progression is into management loses its best engineers. Budget training time as a line item, not as goodwill, and rotate people through detection, testing, and engineering so the work stays interesting.
If you need capability before headcount, external specialists can carry the technical load while you hire; our professional offensive services are often used exactly that way.
Ratios vary far too much by sector to be useful on their own, but a common starting point for a regulated mid-sized organisation is one security person per 100 to 200 staff, plus outsourced monitoring. Regulated financial firms and software companies run considerably higher. Size the team against the services you must deliver internally, then check the ratio as a sanity test.
Strategic, in most cases. The first hire spends their time setting policy, owning risk, answering client security questionnaires, and arguing for budget, and a deeply technical specialist often finds that work frustrating. Buy technical capability through managed services and consultancies until the volume of internal engineering work justifies a dedicated engineer, which is usually the second hire.
Rarely. Genuine 24/7 coverage needs around six to eight analysts once holidays, sickness, and attrition are counted, before tooling and engineering. Below that, in-house monitoring means alerts going unread overnight and at weekends, which is when ransomware operators prefer to act. A managed service with clear escalation to your internal team is the usual answer.
Use them to shortlist, never to decide. CISSP suggests breadth and several years of experience; GIAC certifications test practical skill in a defined area; CREST and Cyber Scheme registration matter for penetration testers working under UK schemes. Pair the shortlist with a practical exercise drawn from your real environment, and weight demonstrated judgement over the acronym list.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.