Skip to content

Event Log Analysis ​

FieldValue
Module ID387
DifficultyHard
TierTier I
CategoryDefensive
Estimated Time4 hours
Cubes Earned10
Experience Points2180
Creatorsletsdefendio
Last Updated2026-06-24T18:46:29.000000Z
URLhttps://academy.hackthebox.com/app/module/387

Module Includes ​

  • 11 Sections
  • 9 Interactive Exercises
  • 0 Assessments
  • 10 Cubes

Module Description ​

This module will teach you the structure of Windows event logs and how you can detect persistence, manipulation, execution, etc. in a hands-on way. You'll do lots of practice during the module.

Module Summary ​

The Event Log Analysis module is designed for incident Responders and Incident Responder candidates. Throughout this module, students will develop an understanding of Event Log structure, detection attacks with Event Logs, and important Event Logs for investigation.

  • General understanding of cybersecurity concepts

Sections ​

11 sections - 9 Interactive

#GroupTypeTitle
1NonetheoryIntroduction to Event Logs
2interactiveEvent Log Analysis
3interactiveAuthentication Event Logs
4interactiveWindows Scheduled Tasks Event Logs
5interactiveWindows Services Event Logs
6interactiveAccount Management Events
7interactiveEvent Log Manipulation
8interactiveWindows Firewall Event Logs
9interactiveWindows Defender Event Logs
10interactivePowershell Command Execution Event logs
11theoryDetailed Event Log Quiz

Conclusion ​

In this module, we covered Windows event log structure, analysis tooling, and hands-on detection of attacker techniques across authentication, persistence, execution, and defense evasion — using Event Viewer, wevtutil, and PowerShell to investigate real log data.

Module key takeaways:

  • Windows event logs are stored in binary .evtx format at C:\Windows\System32\Winevt\Logs and are organized into Application, Security, System, and Setup categories; specialized tools like Event Viewer are required to parse them into human-readable format
  • Key Event IDs for authentication analysis include 4624 (successful logon) and 4625 (failed logon); Logon Type 2 indicates interactive local login, Type 3 is network authentication, and Type 10 is RDP/Remote Desktop — used to identify post-brute-force access patterns
  • Scheduled task abuse (Event IDs 4698 — task created, 4702 — task modified) is a common attacker persistence technique; these events are not logged by default and must be enabled via Group Policy; importantly, task creation events persist even after the task is deleted
  • Windows Services event logs reveal malicious service creation and modification (Event ID 7045 — new service installed) used for persistence and privilege escalation; services can be configured to execute arbitrary code as SYSTEM
  • Account management events (Event ID 4720 — user created, 4732 — user added to group) indicate attacker persistence via backdoor accounts; these events are also not logged by default and require GPO enablement
  • PowerShell activity is logged under Applications and Services Logs > Microsoft > Windows > PowerShell > Operational; because PowerShell is widely abused for execution, lateral movement, and persistence, monitoring these logs provides critical visibility into endpoint activity
  • Windows Firewall logs reveal rule additions and modifications (attackers add rules to permit C2 traffic), and Windows Defender logs (Event ID 1116 — malware detected) provide historical malware detection data; attackers frequently disable Defender as a first post-compromise step, generating detectable events
  • Event log manipulation (clearing logs via Event Viewer or wevtutil.exe cl) is itself a detectable attacker behavior captured in Event ID 1102 (Security log cleared)