Understanding Log Formats, Alerts, and Metadata
As a SOC analyst, you'll encounter various log formats daily. Understanding their structure helps you quickly extract the information you need during investigations.
Standard Unix/Linux logging format. Facility + Severity + Message.
Structured XML format with Event IDs, channels, and detailed metadata.
Connection decisions: permit/deny with 5-tuple, zone, and policy info.
Apache/Nginx combined format: IP, request, status, user agent.
Practice identifying and extracting fields from raw log data. Select a log format, then click "Parse" to see the fields extracted.
Standard structured logging format
<priority>version timestamp hostname app-name procid msgid [structured-data] message
ArcSight standard, pipe-delimited header with key=value extensions
CEF:version|vendor|product|version|signature|name|severity|extensions
Structured, self-describing, easy to parse programmatically
{"timestamp": "...", "source": "...", "event_type": "...", "details": {...}}
Security tools generate alerts with varying levels of detail and confidence. Understanding alert types helps you prioritize and investigate effectively.
Signature-based detection with rule ID, classification, and packet context.
Malware detection, behavioral indicators, file hashes, process trees.
Multi-source correlation, aggregated risk scores, linked events.
Behavioral anomalies, baseline deviation, risk scoring per entity.
When investigating alerts, extract these key data points:
| Field | Purpose | Next Step |
|---|---|---|
| Source IP | Identify attacker/victim | Lookup in asset inventory, threat intel |
| Signature/Rule ID | Understand detection logic | Review rule, check for false positives |
| Timestamp | Timeline reconstruction | Correlate with other events |
| File Hash | Unique malware identifier | Submit to VirusTotal, sandbox |
| User Account | Identify compromised credentials | Check login history, reset if needed |
Identify the correct information from these log samples.