Skip to main content

Could We Detect This? The NCSC's Threat Hunting Questions for Boards

5 min read
CISO Daily
Could We Detect This? The NCSC's Threat Hunting Questions for Boards

Bottom line: On 17 November 2026 the UK National Cyber Security Centre (NCSC) published a blog titled “Why threat hunting should matter to every board”. Its core test is simple: when a new attacker technique is identified, can your organisation say whether it could detect that technique if it were used against you? If the answer is unclear, the NCSC says there may be gaps in visibility or detection. Our reading: this is a blog for boards, not regulation, and we did not see it assert any legal duty.

What the NCSC Says

The blog is aimed at boards of organisations that monitor their systems for cyber threats, either themselves or through a third-party provider. Its argument is that monitoring is fundamental but cannot see everything. Not every threat will trigger an existing alert.

The NCSC defines threat hunting as the proactive search for signs of threats or intrusion that existing security rules and alerts may have missed. A hunt starts with a question or hypothesis, based on factors such as attacker behaviour or threat intelligence, and uses available security data to look for evidence. The NCSC states that hunting complements monitoring and does not replace it.

The blog links the topic to the pace of attacks. It says that as attackers use AI to operate at greater speed and scale, closing detection gaps becomes more important, and that organisations should identify malicious activity early rather than relying solely on detecting an attack once its effects become apparent.

Why It Matters to Executives

Two ideas in the post are useful outside the security team.

Behaviour over indicators. The NCSC notes that defenders have long relied on indicators of compromise such as malicious IP addresses, domains and file hashes. These are useful but can change quickly. Attacker behaviours, described as tactics, techniques and procedures, can be more enduring. The NCSC puts it this way: “An IP address may change overnight. A technique for moving through a network may remain relevant for much longer.”

A hunt that finds nothing still teaches something. Hunting depends on observability, meaning a clear and detailed view of activity across networks, systems and services. If the right data is not recorded, or defenders cannot get to it, they cannot tell whether a technique has been used. The NCSC says a hunt can therefore expose gaps in visibility and detection even when it finds no malicious activity. For boards, the NCSC says, that is valuable information.

The Six Questions

The NCSC says boards do not need to understand the technical details of threat hunting or conduct hunts themselves. It proposes these questions:

  1. Which attacker techniques are most relevant to our organisation?
  2. Can our defenders detect or investigate those techniques in our environment?
  3. Do our defenders have the security data and visibility they need to investigate them?
  4. When they identify gaps in visibility or detection, who is responsible for addressing them?
  5. How do we know whether those gaps are being addressed and our ability to detect threats is improving?
  6. Are our defenders learning from and collaborating with other organisations facing similar threats?

Evidence, Not Reassurance

The NCSC tells boards to look for evidence rather than rely on reassurance alone. It says this could include four kinds: examples of relevant attacker techniques the organisation has tested its visibility and detection against, the gaps those investigations found, who owns them, and what has been done about them. Over time, it says, boards should be able to see whether gaps are closing.

The blog also says effective hunting does not necessarily need a new team. Existing people, data and security functions may provide much of the capability. It suggests starting by asking whether defenders have the data they need, whether they can use it to investigate attacker techniques across the estate, and whether there is a clear process for acting on gaps. Where skills are limited, it points to existing security providers and practitioner communities. It also encourages learning from defender communities, sector Information Sharing and Analysis Centres (ISACs) and industry forums, and names commercial threat intelligence providers as another source of information.

Our Assessment

The points below are our own judgement, not the NCSC’s.

  • A natural fit for existing board reporting. Most board packs report alerts, incidents and patching. Fewer may report detection coverage. The six questions give a CISO a way to add a coverage view without changing the whole dashboard.
  • Outsourced monitoring does not outsource the question. The NCSC addresses organisations that monitor through a third party. If your managed provider runs detection, ask for the same evidence: techniques tested, gaps found, owners, fixes.
  • Treat “we found nothing” as incomplete. A clean hunt result is only meaningful if the data needed to see the technique existed. Ask whether the result reflects absence of activity or absence of visibility.

Suggested Next Steps

These are our suggestions, not NCSC advice.

  1. Put the six questions to your head of security operations and, where relevant, your managed detection provider, and ask for written answers.
  2. Agree three to five attacker techniques most relevant to your sector and ask for a coverage test against each.
  3. Record gaps in the risk register with a named owner and a date for review.

This article is a summary of public guidance and is not legal advice.

Sources