Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Detection maturity describes how far a security team has moved from spotting known bad indicators to recognising attacker behaviour and intent, and how reliably it can prove that it does.

What Is Detection Maturity?
Two organisations can run identical products and have completely different detection capability. Maturity is the word for that difference: whether detections are bought or built, whether they are tested or assumed, whether the team recognises a hash or recognises a behaviour, and whether any of it is demonstrable to someone who asks.
Ryan Stillions published the Detection Maturity Level model in 2014, and its central observation has aged well. It arranges what a detection can express on a ladder:
The practical use of the model is to ask where your detections sit. An estate whose content is overwhelmingly DML-1 and DML-2 has bought indicator feeds, not detection capability, and it will miss any adversary who rotates infrastructure, which is all of them. David Bianco’s Pyramid of Pain makes the same argument from the attacker’s side: the higher up you detect, the more expensive it is for them to adapt.
| Dimension | Early | Mature |
|---|---|---|
| Content source | Vendor defaults | Built to threat model, version controlled |
| Validation | Assumed to work | Tested on a schedule with recorded evidence |
| Telemetry | Whatever arrives | Driven by detection requirements |
| Coverage | Unknown | Mapped, dated, and evidence-backed |
| Feedback | Analysts close noise | Triage outcomes drive engineering |
| Hunting | None or ad hoc | Structured, and producing detections |
For hunting specifically, the Hunting Maturity Model developed by David Bianco at Sqrrl runs from HM0, where the organisation relies entirely on automated alerting, to HM4, where hunting is routine and the majority of successful hunts are automated into detections afterwards. The jump from HM0 to HM1 is simply having enough data to hunt in, which is a telemetry problem rather than a skills problem.
Maturity assessments invite optimism, so prefer questions with checkable answers. Can you name the last five detections you retired, and why? What proportion of your rules have fired in the past 90 days? When was each high-value detection last validated by executing the technique? How long does it take from a new technique being published to a tested rule in production? Can an analyst see, for any alert, what it means and what to do? How many incidents in the past year were found by your own detection rather than by a third party or a ransom note?
That last question is uncomfortable and informative. Discovery by an external party remains common, and it is the clearest evidence available that detection capability is lower than the internal assessment suggests.
The order that works is telemetry, then content, then validation, then automation. Collecting the right data is prerequisite to everything; buying automation before the data is right produces fast decisions based on nothing. Within content, prioritise by threat: the techniques used by groups targeting your industry, scored on a coverage map, not the whole matrix.
UK organisations have a ready-made external reference in the NCSC Cyber Assessment Framework. Its objective C covers the detection of security events, with principle C1 on security monitoring and C2 on proactive discovery, and the outcomes map closely onto the dimensions above. Using it gives you language a board and an auditor already accept.
At Privia Security, we assess detection maturity against evidence rather than self-reporting as part of our SOC maturation services, which usually begins by executing techniques and seeing what arrives.
Test rather than survey. Execute a representative set of techniques across the estate and record what was prevented, what generated telemetry, what alerted, and what an analyst did about it. Combine that with measurable facts: rule precision from triage outcomes, the proportion of rules that have fired recently, validation dates, and how incidents in the past year were first discovered.
Only up to a point, and usually a low one. Tools determine what telemetry is available and how fast you can query it; maturity is about what you do with that. Organisations frequently own capabilities they have not enabled, rules they have not tuned, and data they have not mapped to detections. Auditing what current tooling could deliver is almost always cheaper than buying more.
Validate what you already have. A fortnight of executing techniques against existing rules will identify broken collection, rules that never fire, and coverage claims that do not hold, and the fixes are usually configuration rather than new investment. After that, prioritise telemetry gaps over new rules, because content built on missing data cannot work regardless of how well it is written.
The NCSC Cyber Assessment Framework is the most widely used reference, and objective C addresses detection directly through principles on security monitoring and proactive event discovery. It is mandatory for some regulated sectors and useful voluntarily for everyone else, because it provides language that boards, auditors, and regulators already recognise and expects evidence rather than assertions.
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.