20 Nov 2026 By CISO Consulting team 13 views 4 min read

SOC Maturity Assessment SAMA CSF: Scoring Detection Coverage

A SOC is often judged by its tool list, but the regulator's real question is what you would actually see. This article shows how to map log sources to detection use cases, score the gaps and build a prioritized plan.

Security analysts reviewing detection dashboards in a dimly lit operations centre in the Kingdom.
In this article
  1. What the framework expects
  2. What changes when you assess coverage rather than tools
  3. A sensible order of work
  4. 1. Define the critical systems
  5. 2. Inventory log sources and test their quality
  6. 3. Build the use-case library against attacker techniques
  7. 4. Score the coverage
  8. 5. Test triage and escalation
  9. 6. Turn the gaps into a plan
  10. Usual gaps
  11. How we help
  12. Next step

A SOC maturity assessment SAMA CSF reviewers will accept starts from a different question than most teams expect. Supervisors and internal audit rarely stop at which SIEM, EDR or SOAR products you own. They want evidence that the monitoring you run would detect the attacks relevant to your institution. That depends less on tooling than on which critical systems send usable logs, and which attack techniques those logs let you see.

This article sets out a practical method: inventory log sources, map them to detection use cases, score the gaps, and turn the result into an improvement plan tied to the operations and monitoring expectations of the SAMA Cyber Security Framework (CSF).

What the framework expects

The SAMA CSF, issued by the Saudi Central Bank for banks, insurers and finance companies, expects member organizations to monitor and manage cyber security events, and to respond to incidents in a defined and tested way. In practice this means logging that is sufficient, reviewed and retained, use cases that reflect real threats, and escalation that works when an alert is genuine.

The framework does not ask for a particular product. It asks whether the capability operates effectively. A tool list shows what you bought; coverage shows what you can see.

What changes when you assess coverage rather than tools

Judging a SOC by its tools produces comfortable answers: the platform is deployed, the provider is contracted, the dashboards are green. Judging it by coverage produces uncomfortable but useful ones:

  • A core banking or policy administration system may be on the log source list but send only authentication events.
  • A log source may be connected but parsed badly, so detections never fire.
  • Cloud and SaaS platforms may sit outside the SIEM entirely.
  • Detection rules may exist for techniques that no connected source could ever reveal.

Each of these is invisible in a tool inventory and obvious in a coverage map.

A sensible order of work

1. Define the critical systems

Start with the systems whose compromise would matter most: payment and transaction platforms, identity infrastructure, internet-facing services, privileged access tooling, customer data stores and key third-party connections. Use your existing asset classification so the scope is defensible and consistent with your risk register.

2. Inventory log sources and test their quality

For each critical system, record whether it sends logs, which event types, how completely, with what delay and how long they are retained. Then check usability: are the fields parsed, is time synchronized, can an analyst actually search the events? A source that is connected but unusable should be scored as a gap, not a success.

3. Build the use-case library against attacker techniques

List the detection use cases you operate and map each to the attacker technique it addresses, using a recognized technique catalogue. For each use case, note which log sources it depends on. This is where mismatches surface: a use case with no supporting source is a paper control.

4. Score the coverage

Use a simple, repeatable scale for each technique and each critical system, for example:

  • Not covered: no source, no detection.
  • Partial: source present but incomplete, or detection untested.
  • Covered: usable source, working detection, evidence of testing.
  • Proven: covered, and validated through sampled alerts or exercises.

Weight the scores by the criticality of the system and the likelihood of the technique against your sector. The aim is a ranking, not a single headline number.

5. Test triage and escalation

Coverage means little if alerts are not handled well. Sample real alerts and trace them: how quickly were they triaged, who decided, how were they escalated, and what was recorded? If part of the service is outsourced, compare actual performance against the agreed service levels in the provider contract.

6. Turn the gaps into a plan

Group findings into a backlog: log sources to onboard or repair, use cases to build or tune, process fixes, and staffing or provider changes. Prioritize by risk reduction and effort, and link each item to the relevant SAMA CSF monitoring or incident management expectation so that progress can be shown to the regulator and the board.

Usual gaps

Several gaps recur in this kind of review:

  • Log onboarding driven by what was easy to connect, not by what is critical.
  • Use cases copied from vendor content and never tuned to the environment.
  • No record of which techniques each use case covers.
  • Escalation paths that exist on paper but have never been exercised.
  • Provider reports that measure ticket volume rather than detection quality.

How we help

Our Security Operations (SOC) Maturity Assessment looks at security operations, in-house or outsourced, across people, process, technology, detection coverage and response. The output is a prioritized improvement plan. The work is designed to show what your SOC actually detects and what it misses.

The assessment follows four steps: interview the SOC team, management and provider; map log sources and detections against techniques; test sample alerts and escalation paths; and plan through maturity scoring and a roadmap. The review covers people, process and technology, log source and detection coverage mapping, use-case and alert quality, triage and escalation testing, and a provider SLA review.

You receive a SOC maturity report, a detection coverage map, a use-case improvement backlog and a target operating model. The assessment takes 3–5 weeks, and it is aligned to SAMA CSF and NCA ECC.

Next step

If you need to show your regulator, auditors or board that your SOC works, begin with the coverage question rather than the tool list. Our Security Operations (SOC) Maturity Assessment gives you a scored map of what you can see today and a plan for what to fix first. Contact CISO Consulting to scope it for your environment.

Tags: SAMA CSF SOC Detection coverage Log sources Security operations Regulatory guides MITRE ATT&CK
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