Skip to content

7 · Hunting and detection basics for CTI

Time: 2–3 weeks

Six modules from the ATT&CK team: hunting fundamentals, developing hypotheses, data requirements, collection gaps, implementing and testing analytics, and running the hunt.

Free

For this step, focus on the first modules: hunting fundamentals, developing hypotheses and data requirements.

eCTHPv2 PrepNetriders

Threat hunting explained in Arabic: terminology, threat intelligence, IOCs and YARA, hunting hypotheses, then hunting on the network and the endpoint.

Arabic
Want more? (optional)

After a relevant report, you give the hunting team TTP-based hypotheses, and sometimes write the Sigma rule yourself. The useful part is the feedback loop: what fired, what was noise, and what that tells you about the threat.

Hypothesis-based, IOC-based, TTP-based, behavioural and anomaly-based hunting, and threat-informed defense.

Sigma, YARA and Suricata rules. Query languages: KQL, SPL, EQL and CrowdStrike FQL.

  • Windows: Sysmon, security logs, PowerShell logs, Defender logs, process creation, authentication events.
  • Network: DNS, proxy, firewall and Zeek logs, Suricata alerts, NetFlow.

Wazuh, Security Onion, Splunk, Microsoft Sentinel, CrowdStrike Falcon, Elastic Security.

Take one threat report and turn it into three hunting hypotheses. Example: the adversary may use PowerShell to execute encoded commands and establish persistence. For each one, name the log source it needs and write a simple query or Sigma rule. Write it as you would hand it to a SOC team.

  • You can turn a report’s TTPs into hypotheses a hunting team can use.
  • You can read a Sigma rule and explain what it detects and where it might be noisy.