20 Nov 2026 By CISO Consulting team 6 views 6 min read

Threat Intelligence to Detection Rules for Your SOC

Most SOC teams receive threat reports and file them away. This article sets out a one-day workflow that turns a single report into one tested detection rule, recorded against NCA CSCC monitoring controls.

A SOC analyst reviewing a threat report beside a screen showing detection rule logic in a dimly lit operations room.
In this article
  1. Why indicators alone are not enough
  2. Signs it is time to formalise the process
  3. The workflow in five steps
  4. 1. Select one report and set a boundary (about one hour)
  5. 2. Extract the attacker behaviours (about two hours)
  6. 3. Check whether your logs can see it (about one hour)
  7. 4. Write and test the detection (about three hours)
  8. 5. Record it against the CSCC monitoring control (about one hour)
  9. What a good outcome looks like
  10. Building the skill inside the team
  11. Next step

Most security operations teams receive threat reports and read them with interest. Few convert them into something the monitoring platform can act on. The report is filed, the indicators are loaded into a feed, and the behaviours described in the narrative never reach a detection rule. This article describes a workflow for moving from threat intelligence to detection rules in a SOC, designed so that an analyst can take one report and produce one tested rule in a single working day.

The workflow suits critical infrastructure operators in Saudi Arabia that must align with the NCA Critical Systems Cybersecurity Controls (CSCC), issued by the National Cybersecurity Authority. It assumes you already collect logs and have a platform where rules can be written and tested.

Why indicators alone are not enough

Hashes, IP addresses and domains in a report age quickly. An attacker changes infrastructure between campaigns, but tends to repeat behaviour: how access is gained, how credentials are used, how the attacker moves between systems and how data leaves. A detection built on behaviour has a longer useful life than one built on a single indicator.

This is also what a reviewer wants to see. The NCA CSCC expects monitoring of critical systems to be effective, and a rule you can trace to a documented threat, a log source and a test result is easier to defend than a feed that nobody can explain.

Signs it is time to formalise the process

  • Threat reports are circulated by email but no one owns the follow-up.
  • Rules are written ad hoc, with no record of the threat that prompted them.
  • Analysts cannot say which attacker techniques the current rule set covers.
  • Nobody has checked whether the log sources needed for a given technique are actually collected.
  • Evidence of monitoring for an assessment is assembled by hand each time.

The workflow in five steps

1. Select one report and set a boundary (about one hour)

Choose a report that is relevant to your sector and your technology. Prefer one that describes behaviour in some detail over one that is mostly a list of indicators. Decide in advance that you will produce one rule from it. Trying to cover the whole report is the most common reason the exercise stalls.

2. Extract the attacker behaviours (about two hours)

Read the report and list each observable action the attacker takes. Write each as a plain sentence, for example: "the attacker creates a scheduled task to maintain access" or "the attacker uses a legitimate remote administration tool from an unusual host". Then map each sentence to a technique in a common attacker-technique framework so the behaviour has a stable name.

For each behaviour, note:

  • what the attacker does on the system
  • what trace that action should leave
  • which log source would hold that trace
  • how a legitimate administrator might produce similar activity

Rank the behaviours by two questions: how likely is it to occur in your environment, and how damaging would it be if missed. Pick the top one.

3. Check whether your logs can see it (about one hour)

This step is the one most often skipped, and it is where many rules fail. Before writing logic, confirm three things:

  1. The required log source is collected and reaches your platform.
  2. The fields you need are present and parsed correctly.
  3. The retention period lets you look back far enough to test against real history.

If the answer to any of these is no, you have found a visibility gap. Record it. A documented gap with an owner is a useful output in its own right, and you can choose a different behaviour for today's rule while the gap is raised.

4. Write and test the detection (about three hours)

Write the rule in plain logic first, then in your platform's query language. Keep the first version narrow. A rule that describes the behaviour precisely will produce fewer false alerts than one that matches a broad pattern.

Test in three passes:

  • Historical search: run the logic across past data to see how often it fires and whether the hits are legitimate.
  • Simulation: reproduce the behaviour in a controlled way, with approval, and confirm the alert fires.
  • Tuning: add exclusions for known legitimate activity, and record each exclusion and the reason for it.

Then define what the analyst does when the alert fires: what to check first, when to escalate and what evidence to preserve. A rule with no response note is likely to be ignored or mishandled.

5. Record it against the CSCC monitoring control (about one hour)

Create a short record for the rule. It should hold the source report, the extracted behaviour, the technique name, the log sources used, the test results, the known exclusions, the response note, the owner and the date. Link the record to the monitoring and event-management requirements of the NCA CSCC that the rule supports. Confirm the exact control reference against the current published text of the framework rather than from memory.

Stored consistently, these records become your evidence. When an assessor asks how the SOC detects threats relevant to critical systems, you can show the chain from report to rule to test.

What a good outcome looks like

After a first pass, a team should have one rule in production or staging with test evidence, a short list of visibility gaps, and a template it can repeat. After several passes, the team can see which techniques are covered and which are not, and can direct log onboarding and rule writing by priority instead of by whichever report arrived last.

Common pitfalls are worth stating plainly:

  • Writing the rule before confirming the logs exist.
  • Skipping the simulation and trusting the historical search alone.
  • Leaving exclusions undocumented, so that no one knows later why a rule is quiet.
  • Treating the record as paperwork to complete after the fact rather than as part of the work.

Building the skill inside the team

This workflow depends on analysts who can read a report critically, understand log sources and write precise logic. These skills are learned by doing, which is why practical training helps.

Our SOC Analyst Training is hands-on training at three levels: alert triage, detection engineering and threat hunting, built on the tools and regulations your team works with. The programme includes detection use cases mapped to attacker techniques and log analysis across endpoint, network and cloud sources. It lists NCA CSCC among its frameworks, alongside SAMA CSF and NCA ECC.

We run it in four stages: scope, prepare, deliver and assess. In scoping, we agree the audience, level, language and dates. In preparation, we tailor examples and labs to your institution. Delivery is instructor-led, on site or online, with self-paced lessons where offered. Assessment uses quizzes or practical exercises, followed by certificates with CPE hours.

Training lasts from one to five days. Foundation suits people new to the topic, Intermediate suits those who do the work, and Advanced suits leads and specialists. Levels can be mixed in one programme after a short skills check. Deliverables include course materials and lab exercises, practical assessment and scores per learner, a certificate with CPE hours, and a skills gap summary for the SOC manager.

Next step

If your team receives threat reports but struggles to turn them into tested detections, start with one report this week and follow the five steps. If you want your analysts to build this skill together, speak to us about SOC Analyst Training and we will scope a programme to your team's level and tools.

Tags: Threat Intelligence NCA CSCC Detection Engineering SOC Critical Infrastructure Saudi Arabia
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