CWCYBERWIKI.dev GitHub ↗

Tools & Labs · Beginner

Getting Started with Splunk Security Investigations

Learn a practical approach to reviewing indexes, time ranges, event fields, and potential security incidents.

Updated 2026-10-17

On this page

Verify telemetry first

Before searching for suspicious behavior, establish which indexes and sourcetypes exist, the relevant time window, and any ingestion delays.

| tstats count where index=* by index

Your results depend on access permissions and the environment’s indexing configuration.

Investigation checklist

  1. Confirm that the required log sources are searchable.
  2. Narrow the search using relevant user accounts, hosts, and IP addresses.
  3. Correlate events before and after the initial indicator.
  4. Record observed facts separately from hypotheses.

HTTP User-Agent

User-Agent field guide and detection lab

Incident Timelines · UTC, Clock Skew and Log Arrival

Normalize timestamps and preserve uncertainty in the timeline lab

Detection Validation · From Event Generation to Alert Delivery

Evidence and offline detection validation lab

Found an error or want to improve this article? Edit on GitHub ↗

Related articles

⌕
Ctrl K to search · Enter to open first result Full search ↗