On this page (6 sections)
The UK National Cyber Security Centre (NCSC) has published a blog post for company boards, Why threat hunting should matter to every board, dated 17 November 2026. Its central argument: monitoring is a foundation of defence, yet it will not catch everything, so organisations should also go looking for activity that their alerts never flagged.
This is guidance rather than a vulnerability disclosure, so there is nothing to patch. It matters to business owners, agencies and hosting administrators who depend on alerts from security tools or an outside provider and want to understand how much those alerts really cover.
What the NCSC is saying
According to the NCSC, most organisations already run a mix of security products, subscribe to threat intelligence and follow alerts from providers they trust, and many respond well to threats they know about. The catch is that none of this reveals how well you would spot an attack that nobody has written a rule for.
The NCSC offers a question to ask each time a new attacker technique becomes public: if this were used against us, would we detect it? A team that cannot answer probably has blind spots in what it can see or what it can detect. The NCSC also notes that attackers are using AI to work faster and at larger scale, which raises the stakes, and that defenders should aim to notice malicious activity early instead of waiting until the damage is visible.
What threat hunting is
The NCSC describes threat hunting as a proactive search for signs of intrusion that existing rules and alerts may have missed. Each hunt begins with a hypothesis or question, informed by how attackers behave or by threat intelligence, and then checks the security data the organisation already holds for evidence.
The NCSC is clear that hunting sits alongside monitoring and does not take its place. Monitoring applies established detections all the time; hunting poses fresh questions those detections were never built to answer.
Behaviours last longer than indicators
Defenders have traditionally leaned on indicators of compromise: bad IP addresses, domains, file hashes and malware signatures. The NCSC calls these useful but short-lived. It points instead to attacker behaviour, known as tactics, techniques and procedures (TTPs), which describes how an attacker works rather than the particular tools or infrastructure in use. An address can be swapped overnight, while a method of moving around a network can stay relevant for much longer, so behaviour is a sturdier basis for detection.
You cannot hunt what you cannot see
The NCSC ties hunting to observability, meaning a clear and detailed view of what happens across networks, systems and services. Systems have to record the relevant activity and defenders have to be able to reach that data. If either is missing, a team may be unable to say whether a technique was ever used.
One consequence the NCSC highlights is that a hunt is worth doing even if it turns up nothing malicious. It can show that the data needed to answer the question simply is not there, and that is useful for a board to know. The results should flow back into defences, for instance by collecting better security data, tightening detections or fixing other weaknesses the hunt uncovered.
What this means for website owners
The NCSC post is written for boards and gives no website-specific advice. What follows is our own interpretation of how the ideas apply to people who run sites and servers.
- Alerts only cover what someone wrote a rule for. A quiet dashboard does not prove that nothing happened.
- Logs are the raw material for any hunt. If web server, application, authentication and DNS logs are not kept, or are kept for only a few days, later investigation is not possible.
- If a provider monitors for you, ask what they log, how long they keep it and whether they hunt proactively or only react to alerts.
- When a new technique appears in the news, someone should own the question of whether you could have seen it.
What to do now
- List who is responsible for detection: your own team, a hosting provider or a managed security provider. Write down a name for each system.
- Check what you log today for web servers, admin logins, DNS and certificates, and how long each log is retained.
- Pick one recently reported attacker technique and ask the NCSC's question: could we detect this if it were used against us? Record the answer, including 'we do not know'.
- Turn each gap into an owned task with a name and a date, such as enabling a missing log source or extending retention.
- If you use a provider, ask how they handle activity that does not trigger an existing alert.
- Repeat the exercise on a schedule so new techniques are reviewed regularly rather than once.
Monitoring that supports hunting
Outside-in monitoring cannot replace internal logs, but it gives you an independent record of how your site looks from the internet. Tracking uptime, certificate changes, DNS records and response headers over time builds a baseline to compare against when something seems off. Webforta Monitor covers these areas, and the free security headers checker and SSL checker give one-off views. For the limits of this approach, see what outside-in malware detection can and cannot see.
If you suspect a site has already been compromised, start with our guides on checking whether a website is hacked and what to do if your website is hacked.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
