Log Analysis
What is Log Analysis?
Log AnalysisThe systematic review of system, application, and security logs to detect, investigate, and reconstruct security-relevant events.
Log analysis examines event records produced by operating systems, network devices, applications and security tools — Windows EVTX, Linux syslog/journald, web-server access logs, firewall flows, EDR telemetry and cloud audit trails such as AWS CloudTrail or the Microsoft 365 Unified Audit Log. Analysts collect, parse, normalise and correlate these sources, usually through a SIEM, to surface authentication anomalies, suspicious process execution, lateral movement and data exfiltration.
On Windows, a handful of event IDs carry disproportionate value: 4624/4625 (logon success/failure), 4688 (process creation with command line), 4769 (Kerberos service tickets — the signal for Kerberoasting), 4720 (account created) and 1102 (the Security log was cleared — itself an attack indicator). Detections are increasingly codified as vendor-neutral Sigma rules, and parsed with tools like Chainsaw, Hayabusa, EvtxECmd, Splunk and Elastic.
A recurring adversary countermeasure is log tampering — MITRE ATT&CK technique T1070, Indicator Removal — so mature programmes forward logs off-host in near real time and protect their integrity. Effective analysis ultimately depends on three fundamentals: accurate time synchronisation (NTP) across sources, sufficient retention, and a baseline of normal activity so deviations stand out.
flowchart LR
A["Sources: EVTX, syslog,<br/>CloudTrail, EDR, firewall"] --> B["Collect / forward"]
B --> C["Parse + normalise"]
C --> D["SIEM: correlate across sources"]
D --> E{"Match rule / anomaly?"}
E -- Yes --> F["Alert + investigate"]
E -- No --> G["Retain for hunting"]● Examples
- 01
Hunting for Kerberoasting by analysing Windows Event ID 4769 (Kerberos service-ticket requests) with RC4 encryption in Splunk.
- 02
Correlating AWS CloudTrail ConsoleLogin failures with a later success from a new IP and MFA disabled.
● Frequently asked questions
What is Log Analysis?
The systematic review of system, application, and security logs to detect, investigate, and reconstruct security-relevant events. It belongs to the Forensics & IR category of cybersecurity.
What does Log Analysis mean?
The systematic review of system, application, and security logs to detect, investigate, and reconstruct security-relevant events.
How do you defend against Log Analysis?
Defences for Log Analysis typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for Log Analysis?
Common alternative names include: Event log analysis, Security log review.