06 Nov 2026 By CISO Consulting team 35 views 5 min read

SAMA CSF SOC Maturity Assessment: Five Coverage Gaps

Most SOC reviews count tools and analysts, but SAMA CSF Domain 5 expects demonstrable detection coverage. This article sets out the five dimensions we measure and how the assessment proceeds, phase by phase.

Security analysts reviewing a detection coverage map on a large wall display in a dimly lit operations room.
In this article
  1. Why tool counts mislead
  2. The five dimensions we measure
  3. The use-case inventory method
  4. How the assessment is delivered
  5. Phase 1: Interview
  6. Phase 2: Map
  7. Phase 3: Test
  8. Phase 4: Plan
  9. Evidence format for the board
  10. Deliverables
  11. Next step

A SAMA CSF SOC maturity assessment is often reduced to a headcount and a tool list. Those numbers are easy to report, but they say little about whether the SOC would detect the scenarios that matter to your institution. SAMA's Cyber Security Framework expects security monitoring and detection that can be demonstrated, and a board asked to fund more technology is entitled to evidence of where the gap actually lies.

This article explains the five dimensions we measure, the use-case inventory that separates a technology gap from a playbook gap, and how the assessment is delivered phase by phase.

Why tool counts mislead

A SOC can own a modern SIEM, an EDR platform and a threat intelligence feed and still miss a common attack path. The reason is usually not the product. A log source may not be onboarded, a detection may never have been written for a technique, an alert may fire but be closed without investigation, or an escalation may stall at a handover. Buying another tool treats none of these.

The assessment therefore asks a different question: for each threat scenario relevant to the institution, what is the evidence that it would be detected, triaged and escalated?

The five dimensions we measure

We assess security operations, in-house or outsourced, across people, process, technology, detection coverage and response. Within that, five coverage gaps deserve explicit measurement before any investment decision:

  1. Log source gaps: systems that should feed the SOC but do not, or feed it incompletely.
  2. Detection gaps: techniques with a log source available but no working detection written against them.
  3. Alert quality gaps: detections that exist but produce noise, or are tuned so far down that they no longer catch the behavior.
  4. Triage and escalation gaps: alerts that are generated but are not investigated consistently or reach decision-makers too late.
  5. Provider and ownership gaps: responsibilities that fall between the institution and its managed provider, including service levels that do not match the institution's expectations.

The first is mostly a technology and integration question. The second and third are use-case development questions. The fourth and fifth are process and governance questions. Separating them is what turns a vague sense of weakness into a defensible investment case.

The use-case inventory method

The inventory lists every detection use case the SOC claims to run, then ties each to a threat scenario, the log sources it depends on, its owner and its response playbook. Each entry is classified into one of three outcomes:

  • Missing technology: the required data or capability does not exist, so no amount of tuning will help.
  • Missing use case: the data exists, but no detection has been built or maintained.
  • Immature process: the detection exists, but triage, escalation or provider handling does not turn it into action.

Counting entries in each category shows where money should go. If most gaps are in the second and third categories, a new platform is unlikely to help.

How the assessment is delivered

The assessment takes 3–5 weeks and follows four phases: interview, map, test and plan.

Phase 1: Interview

We interview the SOC team, management and the provider. The aim is to understand how monitoring really works day to day, as opposed to how it is described in policy. Analysts explain how they triage; management explains priorities and reporting; the provider explains what it monitors and under what service terms.

On the client side, participants typically include SOC analysts and leads, the security operations manager, the CISO and the person who manages the provider relationship. Where the SOC is outsourced, the provider takes part directly.

At the end of this phase the client holds an agreed picture of the current operating model, with the people, process and technology review taking shape and the provider SLA review under way.

Phase 2: Map

We map log sources and detections against techniques. This is where the use-case inventory is built and where the first three dimensions become visible. Each technique relevant to your threat scenarios is checked for a log source, a detection and a response path.

Client participation is mainly from the engineers and detection owners who can confirm what is onboarded and what rules are active. Infrastructure and application owners may be asked to clarify which systems are in scope.

At the end of this phase the client holds a draft detection coverage map showing covered, partially covered and uncovered techniques, along with a review of use-case and alert quality.

Phase 3: Test

Mapping shows what should work; testing shows what does. We sample alerts and test escalation paths, checking whether alerts are handled consistently, whether the right people are notified and whether the provider's service levels are met in practice.

The client side includes analysts who handle the sampled alerts, incident managers and the business or technology contacts who sit on escalation paths. The effort asked of them is modest, but their candor matters.

At the end of this phase the client holds findings on triage and escalation that are grounded in observed handling rather than documentation.

Where the institution wants to go further and test detection against a live, objective-driven attack, that is a separate exercise. Red teaming and adversary simulation tests people, processes and technology end to end, and penetration testing identifies exploitable weaknesses. Neither is a substitute for the coverage mapping described here, but both can follow it.

Phase 4: Plan

We score maturity and build the roadmap. Findings from the previous phases are consolidated into scores across the assessed dimensions, and each gap is classified as technology, use case or process. Priorities follow from that classification, which is also what makes the budget request credible.

The CISO and security operations manager review the scoring and sequence the roadmap with us. Finance or risk stakeholders may join where the roadmap carries funding implications.

At the end of this phase the client holds the full set of deliverables and a clear basis for a board paper.

Evidence format for the board

A board request is stronger when it shows evidence rather than assertion. We suggest a one-page structure:

  • The threat scenarios in scope and the share of techniques covered, taken from the coverage map.
  • The gaps grouped by cause: technology, use case or process.
  • The improvement backlog, ordered by risk reduction and effort.
  • The target operating model the funding would support.

This lets directors see why a given sum is being requested and what it will change, and it keeps the conversation anchored in detection coverage rather than product names.

Deliverables

The assessment concludes with four deliverables:

  • SOC maturity report
  • Detection coverage map
  • Use-case improvement backlog
  • Target operating model

The assessment is aligned to SAMA CSF and NCA ECC.

Next step

If you are weighing further SOC investment, a structured assessment will show whether the gap is technology, use cases or process before the budget is committed. Our Security Operations (SOC) Maturity Assessment shows what your SOC actually detects, and what it misses. Contact us to discuss scope and timing.

Tags: SAMA CSF SOC maturity detection coverage use-case inventory security operations board reporting
Readiness self-check

How ready are you? Find out in two minutes

Answer a few questions for your framework. You get a score, your biggest gaps and — if you want it — a detailed assessment from our team.

Ready to talk about your compliance?

Tell us where you stand. We will show you the shortest path to what your regulator expects.

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment