Skip to main content

Telemetry Data Sources

Premium

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.

Common fieldsWhat to look for
Username, source IP, timestampMultiple failed logins followed by a success
Login type (interactive, network, remote)New or suspicious login method
Geo-location or device IDLogins from unusual regions or devices
MFA statusDisabled, missing, or bypassed MFA

Endpoint logs

Endpoint telemetry reveals what processes, scripts, and binaries run on a host. Common tools include EDR agents, Sysmon, and OS audit logs.

Key cluesWhy it matters
New processes (e.g., PowerShell, cmd.exe)May indicate script execution or abuse
Parent-child process relationshipsHelp identify malicious chains
File creation or modificationDetect persistence or lateral movement
Command-line argumentsReveal intent, even if obfuscated

Network logs

Network telemetry covers communication between systems which are vital for identifying exfiltration or lateral movement.

Common sourcesWhat they reveal
Firewall or proxy logsBlocked connections, unusual destinations
DNS logsSuspicious domains or tunneling attempts
NetFlow or packet capturesBandwidth anomalies, persistence beacons

Cloud logs

Cloud telemetry tracks activity in platforms like AWS, GCP, and Azure. Modern interviews often include cloud scenarios to test your adaptability.

Log sourceExample eventWhy it matters
AWS CloudTrailCreateUser, AttachRolePolicyPrivilege escalation or IAM abuse
Azure Activity LogsResource creation or VM accessUnauthorized deployments
GCP Audit LogsService account key creationCredential misuse

Connecting data sources

Analysts rarely rely on a single log. Strong candidates show they can pivot intelligently.

Example correlation flow:

  1. Auth logs: Multiple failed logins for one user.
  2. Endpoint logs: PowerShell launched by that user’s process.
  3. Network logs: Outbound connection to unknown IP.
  4. Cloud logs: Privilege escalation from the same account.

Explaining this chain during interviews shows real-world investigation skill.