CyberKit

Windows Event Log

Also called EVTX, Event Logs.

Windows' record of logons, process starts, and system activity.

What it is

Windows Event Logs (.evtx) record security, system, and application events such as logons, privilege use, service installs, and process creation.

Where it lives

C:\Windows\System32\winevt\Logs\*.evtx

Why it matters

They are central to intrusion timelines: tracking lateral movement via logon types, new-service persistence, and (with auditing on) command-line process creation. Attackers often clear them, which is itself a logged event.

In practice

Event ID 4624 logon events mapping an attacker's hop from a beachhead host to a domain controller.

What to look for

  • Logon events 4624 and 4625 with their logon type.
  • Process creation 4688 with the command line, where auditing is on.
  • Event log cleared (1102) or the service stopped.

Common mistake

Assuming the events you need were recorded. Many useful events are off by default; check the audit policy before concluding nothing happened.

Use it in CyberKit

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Splunk Enterprise Security Commercial

    A SIEM where these logs are searched with SPL and turned into correlation searches.

  • Microsoft Sentinel Commercial

    Microsoft's cloud SIEM, queried with KQL and fed by connectors for these log sources.

  • Elastic Security Commercial

    A SIEM built on Elasticsearch, with a detection rules library and timeline investigations.

  • Wazuh Open source

    An open source platform that collects, decodes and alerts on host and log data.

Tools practitioners use

Read next

  • Lateral Movement: Spreading from the first foothold to other systems.
  • Prefetch: A Windows artifact proving a program ran, and when.
  • Persistence: Mechanisms that keep attacker access across reboots.

Sources