Festival Season OfferUp to 25% off on all our programmes — claim it before you enrol
← All Career InsightsSOC Analyst

Which Windows Event IDs should a SOC analyst know?

A SOC analyst should know the Windows Event IDs that record logons, account changes, new processes, services and log tampering. The core set is 4624 and 4625 (successful and failed logon), 4672 (admin rights assigned), 4688 (new process), 4720 and 4732 (account created and added to a group), 4740 (account locked out), 7045 (new service) and 1102 (security log cleared).

Why Event IDs are the first thing a SOC analyst reads

Windows writes almost everything security-relevant to its event logs, and every type of event has a number. When a SIEM raises an alert on a Windows machine, the Event ID is usually the first clue to what actually happened: a login, a new program starting, a new administrator, or someone wiping the evidence.

Knowing the common IDs by heart lets you read an alert in seconds instead of searching documentation, and it is one of the most common topics in SOC analyst interviews.

The Security log Event IDs to learn first

These live in the Windows Security log. Learn what each one means and what makes it suspicious.

4624 – Successful logon

Someone signed in. Check the logon type, the account and the source address. A logon at 3 a.m. from an unusual machine is worth a look.

4625 – Failed logon

A sign-in failed. Many failures for one account suggest password guessing; failures across many accounts from one source suggest password spraying.

4672 – Special privileges assigned

An account with administrator-level rights logged on. Expected for admins, suspicious for ordinary users or service accounts used interactively.

4688 – New process created

A program started. With command-line logging enabled, this shows exactly what ran, for example PowerShell with an encoded command.

4720 – User account created

A new local or domain account appeared. Attackers create accounts to keep access, so every unexpected one needs an owner.

4728 / 4732 – Added to a security group

An account was added to a group such as Domain Admins or local Administrators. One of the highest-value events to alert on.

4740 – Account locked out

Too many failed logons locked an account. Often a user's forgotten password, sometimes the visible end of a guessing attack.

4769 / 4776 – Kerberos and NTLM checks

Domain controllers record ticket requests and credential validation. Unusual volumes can point to attacks such as Kerberoasting.

1102 – Security log cleared

Someone erased the Security log. Legitimate admins rarely do this; attackers do it to hide their tracks. Treat it as high priority.

Logon types that change what a 4624 means

Every logon event carries a logon type number. The same Event ID can be harmless or alarming depending on it:

  • Type 2 – Interactive: someone typed a password at the keyboard of that machine.
  • Type 3 – Network: access over the network, such as opening a shared folder.
  • Type 4 and 5 – Batch and Service: scheduled tasks and Windows services starting.
  • Type 7 – Unlock: a user unlocked a locked screen.
  • Type 10 – RemoteInteractive: a Remote Desktop (RDP) session. RDP from the internet or between workstations deserves attention.
  • Type 11 – Cached: a laptop signed in with saved credentials while away from the network.

Event IDs outside the Security log worth knowing

Some of the most useful evidence sits in other Windows logs.

7045 – New service installed (System log)

A new Windows service was registered. Many attack tools install themselves as a service to run with high privileges.

4698 – Scheduled task created

A task was set to run later or repeatedly, a common way for malware to survive a reboot.

4104 – PowerShell script block

With script block logging on, Windows records the PowerShell code that actually ran, even if it was obfuscated when launched.

How to investigate a burst of failed logons

A typical first-level SOC task, using only the Event IDs above.

  1. Group the 4625 events

    Count failures by target account and by source IP or workstation over the alert window.

  2. Decide the pattern

    One account with many failures looks like guessing. Many accounts with one or two failures each from one source looks like spraying.

  3. Look for a 4624 after the failures

    A successful logon from the same source right after the failures is the key question: did the attacker get in?

  4. Follow the account

    If they did, check 4672, 4688 and 4720 or 4732 for that account to see what happened next.

  5. Write the handoff

    Record the timeline, the accounts, the source, what you checked and your recommendation, so the next analyst can act without repeating your work.

Quick answers about Windows Event IDs

Short answers to the questions SOC learners search for most.

What is Event ID 4624?

Event ID 4624 records a successful logon to a Windows computer. It includes the account name, the logon type, the source machine or IP address and the logon process used.

What is the difference between Event ID 4624 and 4625?

4624 is a successful logon and 4625 is a failed logon. Analysts compare the two to spot password guessing followed by a successful break-in.

Where can I see Windows Event IDs?

On a single machine, open Event Viewer and look under Windows Logs > Security. In a SOC, the same events are collected centrally into a SIEM such as Splunk or Microsoft Sentinel and searched there.

Why is Event ID 1102 important?

1102 means the Security log was cleared. Attackers clear logs to hide what they did, so an unexpected 1102 is treated as a strong sign of compromise.

Do I need to memorise every Windows Event ID?

No. Learn the fifteen or so covered here well, understand logon types, and know how to look up the rest. Interviewers care more about what you would do with an event than about the number alone.

Go further with Windows log analysis

See where log analysis sits in the syllabus, or read the guides that build on it.

See the SOC Analyst programmeSee the SIEM Platforms & Security Monitoring moduleRead: writing a clear incident handoffRead: what a SIEM is and why it mattersRead: MITRE ATT&CK for SOC analystsBrowse all Career Insights

Read real logs, not just lists

Turn on auditing in a practice Windows machine, sign in, fail a few passwords, create a user and add it to a group, then find each event in Event Viewer. Seeing the events you caused yourself makes every ID stick.

Train for a SOC Analyst role

The same programme, duration and fees, with the learning path built around one job role.

SOC AnalystIncident Response AnalystThreat HunterSIEM EngineerSecurity Monitoring AnalystThreat Intelligence Analyst

Learn Windows log analysis with a mentor

Ask our team how the SOC Analyst programme in Madhapur, Hyderabad covers Event Viewer, Windows Event IDs and SIEM searches.

Our admissions team will call you back within 90 minutes.
AddressHouse No. 3-535, 3rd Floor A Section, LR Towers, 100 Feet Road, Ayyappa Society, Madhapur, Hyderabad, Telangana 500081