HuntBeta Threat hunting console: Find the attacker in a week of company logs.

Hunt is a training SIEM with synthetic Sysmon, Windows, Zeek, proxy and firewall logs from realistic fictional companies. Search them with a pipe query language, follow one odd event to the next, and answer the case.

Hunt workspace overview with event counts and events over time stacked by log source

The workspace overview: every number and chart is a search you can open.

Alerts find what someone wrote a rule for. Hunting finds the rest.

An intrusion that triggered nothing still leaves traces: a process with an odd parent, a host that talks to one address at night, an account that logs on where it never has. Finding them is a habit, and a habit needs real-looking logs and room to be wrong.

01

Start from a hypothesis, not an alert

Pick a technique, write the search that would show it, and learn to read an empty result as an answer too.

02

Stack until something stands out

Count by host, user and parent process. The rare end of a list is where an intrusion hides inside normal traffic.

03

Follow the thread without losing it

From one event to the process that started it, the host it ran on and every account that touched it.

A search language you can take to work

HuntQL is a pipe language in the family of Splunk SPL and Microsoft KQL: search, where, stats, top, rare, timechart. Every click in the console writes visible query text, so the syntax is learned by watching.

  • Examples when you are stuck. Click into an empty search box for searches grouped by technique.
  • Charts from any count. Turn a stats result into ranked bars and click a bar to filter on it.
  • Fields with their real names. The reference shows what each field is called in Splunk, Sentinel and the raw log.
Hunt search console with a HuntQL query, a timeline and Sysmon process events

Investigate a host, a user or an IP

Open any value and see its whole story: when it first and last appeared, how busy it was, and which users, programs and addresses it is connected to. Open any process event to see what started it and what it started.

  • Process trees. Parents and children of any process event, from Sysmon process GUIDs.
  • Entity panels. Activity over time and connected values for any host, user or IP.
  • Back to the search. Every panel shows the query behind it, one click away.
Hunt investigate panel for a host: activity over time and connected users and programs

What you will find inside

Each workspace is one fictional company over a fixed window of synthetic logs.

Real log sources

Sysmon, Windows Security, PowerShell, Zeek, proxy and firewall logs, normalised to common field names.

Realistic noise

Days of ordinary business activity around the intrusion, so the signal has to be found rather than handed over.

Workspace overview

Hosts, users, programs and log sources at a glance, before the first search.

Field reference

Every field with its meaning and its name in Splunk CIM, Microsoft Sentinel ASIM and the raw log.

Saved searches and history

Keep the searches that worked and pick the hunt up where you left it.

Fully synthetic

Every company, user and log line is generated for training. Nothing touches a real network.

Where Hunt fits in the learning paths

It pairs with the Network Threat Hunting and Windows Forensics paths, and it feeds the investigation work in missions.

BEFORE

You learn the techniques

What attackers leave behind in process, network and logon logs, and how hunters go looking for it.

HERE

You run the hunt

Search, stack and pivot through a company’s logs until the intrusion has a timeline.

AFTER

You prove what you found

Hosts, accounts and indicators go into a mission answer, a detection idea or an intelligence report.

Questions

Is Hunt finished?

Hunt is in beta. The console and its workspaces work today, and we are still adding datasets and features and fixing rough edges. If something looks wrong, tell us through the contact page and we will look at it.

Are these real company logs?

No. Every company, user and event in Hunt is generated for training. The logs follow the shape of real Sysmon, Windows, Zeek, proxy and firewall data, but nothing in them comes from a real network.

Do I need to know Splunk or KQL first?

No. HuntQL is introduced from the first search: example searches, a field reference, and query text written for you as you click. If you already know SPL or KQL, the pipe syntax will feel familiar.

What do I need to run it?

A browser and your CTI Academy account. Hunt runs at hunt.ctiacademy.io with single sign-on. There is nothing to install and no VPN to connect.

How does it connect to the rest of the platform?

Learning paths teach the techniques, Hunt is where you practise them on logs, and missions open straight into the right workspace and ask you to prove what you found.

Practise the hunt before the real one.

Create an account, work the paths that lead into it, and hunt through a company's logs where a wrong turn costs nothing.

Hunt is included with a Premium plan. The Cyber Threat Intelligence path, the first modules of every other path, daily simulator runs and 30 minutes a day on the lab network are free, so you can judge the platform before deciding. Compare what each plan includes.

Hunt is a controlled training environment. All companies, users and log data are synthetic and intended for educational use only.