Skip to content

Windows Event Log

A section that explains Windows security audit events (Event IDs) one by one in Japanese and English. The source is Windows Security Auditing Events on Microsoft Learn, to which we add notes from an operations / SIEM / incident-response perspective (how the event is triggered, security checkpoints, things to watch for during log review, and MITRE ATT&CK mappings).

Rather than translating the official descriptions verbatim, each article reworks them, focusing on practical content such as attack techniques (pass-the-hash, Kerberoasting, DCSync, lateral movement, and so on), detection points, and how to handle noise. Technical terms are accompanied by notes for newcomers.

Structure

  • The scope is all 244 Event ID pages in the auditing section of Microsoft Learn, plus 7 related events that have no dedicated page there (4609, 4727–4730, 4754, 4756) — 251 articles in total.
  • Each event has a Japanese and an English version (switch with the language selector at the top).
  • The sidebar is ordered by ascending Event ID.

Main categories and tags

  • Logon / logoff (4624, 4625, 4634, 4647, 4648, 4672, 4768, 4769, 4771, 4776, etc.)
  • Account management (4720, 4722, 4724, 4726, 4732, 4738, 4740, 4741, 4742, etc.)
  • Policy change (4719, 4739, 4713, 4715, 4906, etc.)
  • Process tracking (4688, 4689, 4696)
  • Object access / shares (4656, 4660, 4663, 5140, 5142, 5145, etc.)
  • Directory service (4662, 5136, 5137, 5141, 4928, etc.)
  • Firewall / filtering (4946, 4950, 5025, 5031, 5156, 5157, etc.)
  • Crypto / code integrity / device (5058, 5061, 5038, 6410, 6416, 6423, etc.)

MITRE ATT&CK mapping

Each article’s “MITRE ATT&CK mapping” section lists, in a table, the techniques the event can reveal. To find events from a technique, use the ATT&CK reverse lookup.

  • Technique names and tactics come from MITRE’s published ATT&CK v19.2 data (attack-stix-data).
  • ATT&CK v19 split Defense Evasion into Stealth (TA0005) and Defense Impairment (TA0112). Techniques under T1562 (Impair Defenses) moved to T1685, T1686, and others. Tactic names follow the v19 structure.
  • When an ATT&CK detection strategy lists the event ID as a log source, the article links to that DET entry.
  • For events with no direct technique, the section says so and names the techniques relevant to an investigation.

Detection rules

Each article’s “Detection rules” section lists public detection rules that use the event ID as a condition (only for events that have such rules).

  • Sources are SigmaHQ rules with a windows / security logsource, and Microsoft Sentinel analytics rules and hunting queries that query the SecurityEvent or WindowsEvent table.
  • For 4688 and 4657, the section also gives the number of category-based Sigma rules (process_creation and registry_*) that pySigma can convert for that event.
  • Check each rule’s content at the link. Some need false-positive tuning or values for your environment.

Note

For the most accurate, up-to-date information, always check the Microsoft Learn source link at the end of each article (and the primary sources referenced). This section is a curated, annotated version.