Telemetry Data Sources
Every SOC investigation begins with telemetry, i.e. the logs, alerts, and signals that describe what’s happening across systems. Your proficiency with telemetry determines how quickly and accurately you can detect, investigate, and respond to threats.
To demonstrate this in interviews, focus on your ability to:
- Identify where to find relevant evidence (e.g. authentication logs, endpoint events, network flow data).
- Interpret what each log tells you (e.g. what was done, by whom, when, and how).
- Correlate multiple data sources into one coherent story that explains the incident from start to finish.
Strong answers show that you know how telemetry fits together, not just what tools produce it.
Authentication logs (Auth logs)
Authentication logs show who accessed what, when, and from where. They’re the foundation of most identity and access investigations.
Endpoint logs
Endpoint telemetry reveals what processes, scripts, and binaries run on a host. Common tools include EDR agents, Sysmon, and OS audit logs.
Network logs
Network telemetry covers communication between systems which are vital for identifying exfiltration or lateral movement.
Cloud logs
Cloud telemetry tracks activity in platforms like AWS, GCP, and Azure. Modern interviews often include cloud scenarios to test your adaptability.
Connecting data sources
Analysts rarely rely on a single log. Strong candidates show they can pivot intelligently.
Example correlation flow:
- Auth logs: Multiple failed logins for one user.
- Endpoint logs: PowerShell launched by that user’s process.
- Network logs: Outbound connection to unknown IP.
- Cloud logs: Privilege escalation from the same account.
Explaining this chain during interviews shows real-world investigation skill.
Asked at