Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Are Windows Event Logs?

Windows event logs are the built-in record of authentication, process, service, and policy activity on every Windows system — and the first place any intrusion is reconstructed from.

Illustration for the cybersecurity term Windows Event Logs
Home / Blog / Cybersecurity Terms / What Are Windows Event Logs?
17 November 2026

What Are Windows Event Logs?

What Are Windows Event Logs?

Every Windows system keeps a structured record of what happens on it, stored as EVTX files under %SystemRoot%\System32\winevt\Logs and readable through the Event Viewer or the wevtutil and Get-WinEvent commands. For defenders this is the foundation layer: the first evidence consulted in almost every Windows investigation, available on every host without buying anything, and comprehensively misconfigured in most estates.

The logs are organised into channels. Security, System, and Application are the familiar three, but the detection value is spread much wider, across the Applications and Services channels where PowerShell, Sysmon, Task Scheduler, WMI activity, Terminal Services, and Windows Defender each write their own stream.

The Event IDs Worth Knowing

IDMeaningInvestigative use
4624Successful logonLogon type distinguishes interactive (2), network (3), service (5), RDP (10)
4625Failed logonPassword spraying appears as many accounts, few attempts each
4648Logon with explicit credentialsA strong indicator of credential reuse during lateral movement
4672Special privileges assignedMarks administrative logons
4688Process creationWith command line auditing enabled, the built-in equivalent of Sysmon Event ID 1
4698Scheduled task createdA common persistence mechanism
4719Audit policy changedAttackers disabling the logging you depend on
4720, 4728, 4732Account created, added to groupsPrivilege escalation and backdoor accounts
4768, 4769, 4771Kerberos ticket activityKerberoasting shows as many service ticket requests with weak encryption
5140, 5145Network share accessedData staging and tooling transferred over SMB
7045Service installed (System channel)Remote execution tools and persistence
1102Audit log clearedAnti-forensics; should always alert

Nothing Useful Is On by Default

Two configuration gaps account for most disappointment. The first is that advanced audit policy subcategories control what is recorded, and the defaults omit a good deal. Process creation auditing, detailed file share access, and several Kerberos subcategories all have to be enabled deliberately through Group Policy.

The second is specific and important: Event ID 4688 records only the process name unless the policy Include command line in process creation events is enabled. Without it you learn that powershell.exe ran and nothing about what it did, which is the difference between a usable log and a log that merely exists. Enable it alongside PowerShell script block logging, which records the code itself.

Channel sizes also need attention. The defaults are measured in tens of megabytes, which a domain controller or a busy file server overwrites within hours. Raising them buys time; forwarding the events off the host solves the problem properly.

Collecting Them Centrally

Logs that stay on the host are logs an attacker can delete, and logs nobody correlates. Windows Event Forwarding provides an agentless route — collector-initiated or source-initiated subscriptions, driven by Group Policy, with XPath filters that select only the events you want before they are sent. Most organisations instead use the agent their SIEM vendor supplies, which is simpler to operate and often filters more flexibly.

Either way, filter at the source. Forwarding the Security channel in full from every host is one of the quickest ways to exhaust a licence, and a handful of high-volume event IDs usually account for most of it. The decision about which to keep belongs in your use case catalogue, so the detections depending on each event ID are visible before anything is dropped.

When the Logs Have Been Tampered With

Clearing the Security log raises Event ID 1102, and clearing any other channel raises Event ID 104 in System — both of which should alert without exception, since there is no routine reason for either. More subtle interference exists: stopping the Event Log service, reducing a channel’s maximum size so it rolls over immediately, disabling audit subcategories, or selectively removing records from an EVTX file. Forensic techniques for spotting these are covered in finding traces of log deletion, and the reliable defence is the same in every case: get the events off the host as they occur, because an event already in the SIEM cannot be edited on the endpoint.

The NCSC’s logging and protective monitoring guidance makes the same point for UK organisations, and treats centralised, tamper-resistant collection as a baseline expectation rather than an advanced capability. Windows event logs combined with Sysmon cover complementary ground, and most mature Windows detection programmes run both. At Privia Security, we review audit configuration and collection coverage through our SOC maturation services.

FAQ – Frequently Asked Questions

How Long Are Windows Event Logs Kept Locally?

Only until the channel fills and starts overwriting, which on default sizes can be hours on a domain controller or a busy server and weeks on a quiet workstation. Local retention is never a reliable evidence strategy. Raise the channel sizes as a stopgap, and forward events to central storage where retention is a decision you control rather than a side effect of disk allocation.

What Is the Difference Between 4624 and 4648?

Event 4624 records a successful logon and its type, which covers normal interactive, network, and service authentication. Event 4648 records a logon performed with explicitly supplied credentials, meaning someone used a different account than the one they were logged in as. That is routine for administrators using runas and also a reliable marker of lateral movement with stolen credentials.

Do We Need Sysmon if We Collect Windows Event Logs?

They overlap less than people assume. Windows logs cover authentication, Kerberos, group changes, services, scheduled tasks, and policy changes that Sysmon does not record. Sysmon adds process hashes, parent command lines, network connections attributed to processes, image loads, and DNS queries. Collecting both gives materially better coverage than either alone.

Which Events Should We Alert On First?

Start with audit log cleared (1102 and 104), new service installation (7045), accounts added to privileged groups (4728 and 4732), and scheduled task creation (4698). All four are low volume, hard for an attacker to avoid, and rarely legitimate outside known change windows, which makes them realistic first rules for a team with limited tuning capacity.

Related Terms

You May Be Interested In These

What Is a Man-in-the-Browser Attack?

Cybersecurity Terms

17 November 2026

What Is a Man-in-the-Browser Attack?

Read More
What Is Detection Maturity?

Cybersecurity Terms

17 November 2026

What Is Detection Maturity?

Read More
What Is a Disaster Recovery Plan?

Cybersecurity Terms

17 November 2026

What Is a Disaster Recovery Plan?

Read More