Security event 4624
An account was successfully logged on
Channel: Security. Category: Logon/Logoff (Audit Logon).
What it records
Records that a logon session was created on the computer being accessed. Captures the account (Subject and New Logon), the Logon Type (Interactive, Network, RemoteInteractive/RDP, Service, Batch, Unlock, NewCredentials, etc.), the process that requested the logon, and the source workstation/IP.
Why it matters
The foundational record of successful authentication on a host. It is the starting point for reconstructing who logged on where and how, correlating lateral movement across a network, and building an authentication timeline during an investigation. The Logon ID field ties it to related events like 4634, 4647, 4672, 4627, and to 4769 on a domain controller via the Logon GUID.
What triggers it
Generated by every successful interactive, network, RDP, service, batch, or workstation-unlock logon: both routine legitimate activity and attacker activity such as RDP lateral movement, PsExec-style remote execution, pass-the-hash, or use of stolen credentials.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Logon Type | Numeric code for how the logon happened (2=Interactive, 3=Network, 4=Batch, 5=Service, 7=Unlock, 8=NetworkCleartext, 9=NewCredentials, 10=RemoteInteractive/RDP, 11=CachedInteractive): the fastest way to separate a console logon from RDP lateral movement, a service start, or a share access. |
| Account Name (New Logon) | The account the session was actually created for: the identity to pivot on when tracing what a session did. |
| Source Network Address | IP address the logon originated from: the primary pivot point for tracing lateral movement or a remote brute-force/spray source. |
| Workstation Name | Hostname the logon came from, useful when Kerberos logons leave Source Network Address blank. |
| Logon ID | Hex session identifier unique between reboots: the correlation key tying this logon to its later 4634/4647 (logoff), 4672 (privileges), and 4688 (processes run in the session). |
| Process Name | Full path of the process that requested the logon (e.g. svchost.exe, winlogon.exe), which flags an unexpected process performing authentication. |
In practice
Logged on a domain controller when CORP\jsmith successfully authenticates with Logon Type 10 (RemoteInteractive) from Source Network Address 203.0.113.25, indicating an interactive RDP session. The Logon ID assigned in the New Logon fields ties together every later action in that session, such as 4688 process creations or 4663 file accesses.
Sample record
An account was successfully logged on.
Subject:
Security ID: S-1-5-18
Account Name: WORKSTATION01$
Account Domain: CORP
Logon ID: 0x3E7
Logon Information:
Logon Type: 3
Restricted Admin Mode: -
Virtual Account: No
Elevated Token: No
Impersonation Level: Impersonation
New Logon:
Security ID: S-1-5-21-3623811015-3361044348-30300820-1104
Account Name: jsmith
Account Domain: CORP
Logon ID: 0x3E7F2A1
Linked Logon ID: 0x0
Network Account Name: -
Network Account Domain: -
Logon GUID: {00000000-0000-0000-0000-000000000000}
Process Information:
Process ID: 0x0
Process Name: -
Network Information:
Workstation Name: WORKSTATION01
Source Network Address: 203.0.113.10
Source Port: 49234
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): NTLM V2
Key Length: 128ATT&CK techniques
- T1078: Valid Accounts
Sources
Paste a record into Event XML or open a log in EVTX Reader.