Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A security maturity model scores how consistently and deliberately an organisation performs security activities, turning a vague sense of progress into a measurable improvement roadmap.

What Are Security Maturity Models?
A maturity model measures how an organisation does something, not whether it does it at all. Two companies can both say they perform vulnerability management: one because a diligent engineer runs a scan when he remembers, the other because scanning is scheduled, triaged against asset criticality, tracked to closure, and reported monthly. A compliance checklist scores them the same. A maturity model does not.
That distinction is the reason maturity models have become the standard way to describe a security programme to a board. Progress from level 1 to level 2 across eight practices is a sentence an audit committee understands.
Most models descend from the Capability Maturity Model Integration scale, with five levels that recur in slightly different wording everywhere:
| Level | Name | What it looks like |
|---|---|---|
| 1 | Initial | Work happens through individual effort; results depend on who is on shift |
| 2 | Repeatable | A documented process exists and is usually followed |
| 3 | Defined | The process is standard across the organisation and people are trained in it |
| 4 | Managed | The process is measured, with metrics driving decisions |
| 5 | Optimising | Measurement feeds deliberate, continuous improvement |
The jump that matters most in practice is 1 to 3. Getting from “a talented person does this” to “the organisation does this” survives resignations, which is the real test of a security function.
Three choices decide whether the exercise produces change or a chart:
Independent assessment is worth buying at least occasionally. Self-assessment drifts upwards over time, particularly when scores are reported to a board that rewards improvement.
Certification against ISO 27001 proves a management system exists and meets requirements; it says little about how well individual practices are performed. Organisations frequently hold a valid certificate while sitting at level 2 on detection and response, which is exactly the combination that produces a surprised board after an incident.
The converse also happens. A high maturity score in a model nobody else recognises will not satisfy a customer who asked for a certificate. Treat the two as answering different questions and present both when the audience is external.
Maturity theatre is easy to spot in hindsight: an assessment run annually by the same team, scores that rise by a tenth of a point each year, and no corresponding change in how incidents actually go. The antidote is to tie each target level to a dated, owned piece of work, then test the claim independently. If detection maturity went from 2 to 3, a purple team exercise should show more techniques generating alerts than it did last year. When the score moves and the evidence does not, the score is wrong.
If you want a maturity baseline grounded in operational evidence rather than interviews, our SOC maturation services assess capability against tested detection coverage.
Level 3, meaning defined and consistently applied, is a realistic target for most core practices in a mid-sized organisation. Levels 4 and 5 require measurement infrastructure and dedicated improvement effort that only pays off where the risk justifies it, typically in detection, identity, and vulnerability management. Setting a uniform target across all practices wastes budget on areas that do not need it.
Annually for a full assessment, with lighter quarterly reviews of practices undergoing active improvement. Reassessing more often rarely shows meaningful movement, because maturity changes through sustained process change rather than purchases. After a major incident or acquisition, an out-of-cycle assessment of the affected areas is usually worthwhile.
Not formally. The CAF is outcome-based: each contributing outcome is assessed as achieved, partially achieved, or not achieved against indicators of good practice. In practice organisations use it much as they would a maturity model, tracking movement between those states over time. For UK operators in scope of the NIS Regulations it is the framework competent authorities expect.
No. Customers, insurers, and procurement teams ask for certificates because they are independently verified against a published standard. A maturity model is an internal management tool that tells you where to improve and how far you have come. Most organisations run both: certification to satisfy external parties and a maturity model to plan the work behind it.
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.