Hunt Strategy & Objective
Identify telemetry consistent with the publicly reported event.
⏱️ Lookback: 30 days
Hunt Hypothesis
Publicly reported event-associated activity may be observable in relevant telemetry.
Target Platforms & Environment
Platform depends on affected technology
Publicly documented event indicators, named tools, products, and behaviors.
Required Telemetry & Data Sources
SIEM logs
EDR process and network telemetry
authentication and configuration-change logs
Procedural Hunting Sequence
- 1 Scope affected products, tools, and named infrastructure from the cited source.
- 2 Search SIEM and EDR telemetry for matching names, URLs, processes, authentication anomalies, and configuration changes.
- 3 Triage hits against approved administration and software deployment activity; contain only confirmed malicious activity under local procedures.
- 4 Preserve logs, process trees, network metadata, and configuration history for forensic validation.
Hunt Queries
Query Pattern 1
Tune the accompanying SPL query to local indexes and fields.
✓
True Positive Confirmation Evidence
●
Matching process, network, authentication, or configuration-change telemetry
!
Benign & False Positive Explanations
●
Authorized administration, testing, and security-tool activity
Validation Checklist
Confirm timestamp, host, user, parent process, destination, and source evidence linkage
Escalation Criteria
Correlated activity across host and network telemetry