liveBook · Manning

Hypothesis

As explained in Cyber Threat Hunting

A hypothesis is a proposition consistent with known data that has not yet been verified or shown to be false.

A hypothesis is a proposition consistent with known data that has not yet been verified or shown false. In structured threat hunting, it states a threat that may exist in the environment and how evidence could identify it. A useful hypothesis is both relevant to the organization and testable with available data and tools. section 1.3 section 2.2.3

Build and run a hypothesis as a repeatable hunt:

  • Derive it from the local threat landscape: threat intelligence, threat modeling, red-team exercises, incident reviews, and relevant standards or frameworks. section 1.3.1 section 1.6
  • Specify the suspected threat, scope, techniques or indicators, required data, search activities, tools, data volume, and expected search time. section 2.2.3 section 1.6
  • Search for initial evidence, then let findings guide subsequent searches. Suspicious encoded commands, unsigned scripts, unusual arguments, and suspicious parent processes can test a PowerShell hypothesis. section 1.3.2
  • Classify the result as proved, disproved, or inconclusive. An inconclusive result can reflect insufficient data, unsuitable tools, or limited scope rather than the threat’s absence. section 1.3.2
  • Refine an unproven hypothesis and search again; when proved, expand to other systems, engage incident response, and share detection or threat-intelligence content. section 1.6 section 1.8

From suspected PowerShell use to a cloud-native hunt

A Windows-focused hypothesis can propose that an adversary accessed endpoints and used PowerShell for unauthorized activity. A cloud-native variant can propose that an attacker escaped a Kubernetes container and controls Kubernetes infrastructure, then scope searches to public and private cloud application infrastructure and techniques such as Escape to Host and Resource Hijacking. section 1.3 section 5.3.1

Figure 1.3 High-level threat-hunting process

Use the process diagram to trace the loop from formalizing a hypothesis through proof, refinement, expanded scoping, incident response, and new monitoring content. section 1.6

How Cyber Threat Hunting covers it

How deep it goes
Defines hypotheses, gives relevance and testability criteria, and details an iterative testing and response workflow.
Examples
Uses PowerShell activity, spearphishing through a malicious Word document, Kubernetes container escape, and public-facing API exploitation.
What it assumes
Assumes environment-specific domain knowledge and situational awareness while teaching a documentation format for new hunts.
What you can do after
Apply it in structured threat hunting to scope searches, assess evidence, refine inconclusive investigations, and escalate confirmed incidents.
How it connects
Connects threat intelligence, threat modeling, MITRE ATT&CK, indicators, incident response, detection rules, and situational awareness.

Also explained in

Compare how 9 books explain hypothesis →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Cyber Threat Hunting. The section links point to the parts of the book it draws on.