← Blog
// BLUE TEAM · DETECCIÓN

The Windows Event IDs every SOC should watch

Published Aug 18, 2026 · 9 min read
Blue TeamDetecciónWindows

Windows generates hundreds of event types and almost nobody reads them all. The good news: you don't have to. A handful of IDs tell, in order, the story of nearly any intrusion — from the first password attempt to the log clearing that covers the tracks. These are the ones that truly matter, grouped by what they reveal.

Prefer it as a visual story, phase by phase? Walk through the Anatomy of an attack: the same chain, from phishing to anti-forensics, with the tool that catches each step.

1. Authentication: an attack's first noise

2. Privileges and execution

3. Escalation and lateral movement

4. Persistence

5. Anti-forensics: when they try to erase the trail

6. PowerShell and Sysmon: real visibility

🪟 Investigating an ID you don't recognize? The Windows Event ID reference gives you, for each one, what it logs, its log source, the risk and what to hunt. And if you have suspicious logs, the log analyzer surfaces patterns and IOCs.

Turn the signal into detection

Watching the right event is half of it; the other half is writing the rule. With Sigma you write it once and convert it to KQL, SPL, Elastic or Wazuh. An example for point 3 (added to a privileged group):

Detection card · Sigma Tested on the bench

Addition to a privileged domain group

Problem
With stolen credentials, the attacker adds themselves to Domain Admins to keep control of the domain.
Goal
Alert on every addition to Domain Admins.
Telemetry
Windows Security, event 4728 (member added to a security-enabled global group).
Requirements
«Audit Security Group Management» subcategory with Success on the domain controllers.
ATT&CK
T1098.007 · Additional Local or Domain Groups
Level
High
title: Addition to a privileged domain group
logsource:
  product: windows
  service: security
detection:
  selection:
    EventID: 4728
    TargetUserName: 'Domain Admins'
  condition: selection
falsepositives:
  - Planned additions by the identity team
level: high
tags:
  - attack.persistence
  - attack.t1098.007

How it works. The domain controller logs 4728 when a member is added to a security-enabled global group. In that event TargetUserName is the group, not the person: who was added is in MemberName and MemberSid.

Matches · synthetic event
EventID: 4728
TargetUserName: Domain Admins
TargetSid: S-1-5-21-1004336348-1177238915-682003330-512
MemberName: CN=svc-backup,OU=Servicios,DC=contoso,DC=local
SubjectUserName: helpdesk02
Also matches
  • The same group written in lower case.
No match · negative cases
  • 4728 on another global group (Helpdesk).
  • A group whose name only starts with «Domain Admins».
  • 4729: removal from Domain Admins, not an addition.

Known false positives

  • Planned additions by the identity team.
  • Provisioning tools that manage the group.

Limits

  • It only sees global groups: additions to domain local groups (4732, such as Administrators) and universal groups (4756, such as Enterprise Admins) are other events.
  • It matches the English name. If the domain uses another language or the group was renamed, filter on a TargetSid ending in -512.

Sources: Microsoft Learn — Audit Security Group Management

Automated test: 2 positive and 3 negative synthetic cases, on every CI run. Reviewed: 23 October 2026. Test your variant on the bench →
⚒️ Go from event to rule with Sigma Forge (and export it to five SIEM dialects), and grade it with the detection linter before pushing it.

Before hunting: make sure you're logging

Many of these events are off by default: command-line auditing (4688), script block logging (4104) and Sysmon must be enabled. A detection on an event you don't log is a detection that never fires. Review your audit policy before writing rules.

Checklist

It's not about reading everything, but about watching what tells the story. With these IDs, an intruder leaves footprints at every phase — you just have to be looking.

Share: LinkedIn X
Sergio Belmonte Morales
Sergio Belmonte Morales
Cybersecurity Analyst · SOC · Sentinel/KQL specialist