08 Nov 2026 By CISO Consulting team 34 views 6 min read

Threat Intelligence NCA ECC Compliance Evidence: Control 2-12

Many teams subscribe to threat feeds but cannot show how intelligence changed a detection or a decision. This article explains how to grade sources, record actor tracking and produce a short briefing and detection update that serve as audit evidence.

A security analyst reviewing a threat intelligence briefing on a monitor in a dimly lit operations room.
In this article
  1. What the framework expects, in plain terms
  2. Signs it is time to formalize the work
  3. Step one: define requirements before collecting
  4. Step two: set source-grading rules
  5. Step three: record actor and campaign tracking
  6. Step four: produce a briefing and a detection update
  7. The briefing
  8. The detection update
  9. What a good outcome looks like
  10. Common mistakes to avoid
  11. How CISO Consulting supports this
  12. Next step

Most security teams in the Kingdom receive threat information every day. Far fewer can show a reviewer what they did with it. For threat intelligence NCA ECC compliance evidence, the question is rarely whether a feed exists. It is whether the organization can demonstrate that intelligence was collected on purpose, judged for reliability, and then changed a detection, a control or a decision.

This article is for SOC leads, threat analysts and compliance officers. It describes the evidence an NCA ECC review is likely to look for under the Essential Cybersecurity Controls issued by the National Cybersecurity Authority (NCA), and how to produce it with modest effort.

What the framework expects, in plain terms

NCA ECC includes requirements for cybersecurity event and incident management and for threat management, including the use of threat intelligence. We describe the intent here rather than quote clause wording, so confirm the exact control text and numbering in the current ECC document before mapping your records to it.

In practice, a reviewer wants to see three things: that the organization receives intelligence relevant to its sector and region, that someone evaluates it, and that the result reaches people who can act. Each of these leaves a record if the team works in a disciplined way.

Signs it is time to formalize the work

Several patterns suggest a team is collecting but not yet producing evidence:

  • Feeds are subscribed to, but nobody can say which requirement each one serves.
  • Indicators are loaded into tools without any record of where they came from or how reliable the source is.
  • Analysts follow threat actors informally, and the knowledge sits in individual notebooks or memory.
  • Executives receive long technical digests, or nothing at all.
  • A detection rule was changed after a threat report, but the link between the two was never written down.
  • Compliance staff and analysts describe the same activity in different terms, so audit preparation becomes a scramble.

If two or three of these sound familiar, the gap is usually process, not tooling.

Step one: define requirements before collecting

The intelligence cycle starts with requirements. Write down a short list of questions the business needs answered, for example which actors target your sector in the region, which technologies in your estate are being exploited, and which events would change your risk position. Review the list on a set schedule and keep the dated versions.

This list is your first piece of evidence. It shows that collection is purposeful and gives every later record something to refer to.

Step two: set source-grading rules

A source register is the simplest control a team can add. For each source, whether commercial, community, government or open-source, record:

  1. The owner inside your team.
  2. The requirement it supports.
  3. A reliability grade for the source and a separate credibility grade for each item.
  4. The date of the last review.

Keep the grading scale short and define each level in a sentence. Two analysts should reach the same grade for the same item. Separating the reliability of the source from the credibility of the information matters because a usually dependable source can still pass on an unconfirmed claim.

Open-source collection deserves the same discipline. Note what was searched, when, and what was discarded and why. Reviewers value a record of judgment more than a long list of indicators.

Step three: record actor and campaign tracking

Tracking actors that target the region does not require a large platform. A structured profile for each tracked actor or campaign is enough, provided it is kept current. Useful fields include:

  • Names and aliases used by different sources.
  • Targeted sectors and countries.
  • Observed techniques, mapped to a common technique framework.
  • Date of last relevant activity and the source of that information.
  • Relevance to your institution, stated as a judgment with a short reason.
  • Linked detections and controls.

The last field is the one most teams omit, and it is the one that turns a profile into evidence. It shows where intelligence touches your defenses.

Step four: produce a briefing and a detection update

Two short documents carry most of the evidential weight.

The briefing

Write one page for executives and a separate technical annex for analysts. The executive page should state what was observed, how confident you are, what it means for the institution, and what decision or action is requested. Date it, name the author, and record who received it. Writing for two audiences is a skill in its own right; a single document rarely serves both.

The detection update

Whenever intelligence leads to a change, record it in a short entry: the intelligence item and its grade, the detection or control affected, the change made, the person who approved it, the date, and how you tested that it works. If intelligence leads to a decision not to change anything, record that too, with the reason. A documented decision to do nothing is still evidence of judgment.

What a good outcome looks like

After a quarter of working this way, a team should be able to produce, on request:

  • The current requirements list and its history.
  • The source register with grades and review dates.
  • Actor and campaign profiles linked to detections.
  • A set of dated briefings with distribution records.
  • Detection update entries tied to specific intelligence items.

A reviewer can then follow a single thread from a requirement to a source, a judgment, a briefing and a change in a control. That thread is what turns activity into compliance evidence. It also helps the SOC, because analysts spend less time re-deriving why a rule exists.

Common mistakes to avoid

Do not treat the volume of indicators as a measure of maturity. Do not let grading drift, so that every source becomes "high". Do not write briefings that describe a threat without saying what the institution should do. And do not leave the mapping to compliance staff alone; analysts must own the links to detections, or the records will not reflect reality.

How CISO Consulting supports this

Our Cyber Threat Intelligence Training covers collecting and judging sources, tracking threat actors that target the region, and turning findings into detections and briefings. The content includes the intelligence cycle and defining requirements, source evaluation and open-source collection, threat actor and campaign tracking, mapping findings to detections and controls, and writing briefings for technical and executive readers. The training is mapped to NCA ECC and SAMA CSF.

We run it in four stages. We agree the audience, level, language and dates, then tailor examples and labs to your institution. Delivery is through instructor-led sessions on site or online, with self-paced lessons where offered. We then assess with quizzes or practical exercises, followed by certificates with CPE hours.

Participants receive course materials and exercises, an intelligence report template, a certificate with CPE hours, and results per learner. The training lasts one to five days, on site or online. Foundation suits people new to the topic, Intermediate suits those who do the work, and Advanced suits leads and specialists, and we can mix levels in one program after a short skills check.

Next step

If your team subscribes to intelligence but cannot yet show what it changed, begin with a short review of your requirements list and source register, then consider whether structured training would help analysts and compliance staff work to the same method. Our Cyber Threat Intelligence Training is designed to help turn threat information into decisions, and approved clients can order seats or a whole cohort in English or Arabic, or request a quote for an on-site session.

Tags: NCA ECC threat intelligence SOC compliance evidence threat management training
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