Network Threat Hunting
Hunt for anomalous communication, tunneling, beaconing, lateral movement, and data movement.
On this page · 4 sections
Operating context
Network hunts rely on direction, role, protocol, timing, volume, destination novelty, and corroborating host or identity evidence.
- Define the security decision that network threat hunting must support.
- Assign accountable owners, escalation paths, service levels, and privacy boundaries.
- Measure signal quality, response consistency, operational cost, and improvement over time.
Operational workflow
- 01
Establish scope, dependencies, normal behavior, and a documented baseline.
- 02
Collect the minimum telemetry and context needed for network threat hunting.
- 03
Correlate independent signals and state confidence before taking disruptive action.
- 04
Document the decision, evidence, containment or control action, and responsible owner.
- 05
Review the outcome, tune the process, and validate the improvement with a safe test.
Signals, evidence & decisions
| Signal or artifact | Decision it supports |
|---|---|
| flow and protocol metadata | Establish event sequence and affected scope. |
| DNS, TLS, proxy, and IDS context | Confirm identity, asset, or control context. |
| asset role and historical baseline | Support containment, recovery, or tuning. |
Record source, timestamp, collection method, confidence, owner, and disposition. Preserve the smallest useful evidence set and document any uncertainty.
Implementation & improvement
- Separate internet, east-west, and management traffic.
- Account for shared infrastructure and CDNs.
- Validate anomalies with endpoint or service context.