Security event 4625
An account failed to log on
Channel: Security. Category: Logon/Logoff (Audit Logon / Audit Account Lockout).
What it records
Logged for any failed logon attempt, regardless of the reason, on the computer where the attempt was made. Captures the target account, the Logon Type attempted, the source workstation/IP, and a Status/Sub Status code identifying the specific failure reason.
Why it matters
The central event for detecting brute-force attacks, password-spraying, account enumeration, and account lockouts. The Status/Sub Status codes let an analyst distinguish a simple mistyped password from a disabled, locked-out, or expired account, or a logon-hours/authorized-workstation violation.
What triggers it
A wrong password; a disabled, expired, or locked-out account; logon-hours or workstation restrictions being violated; or an automated brute-force/password-spray tool. Also fires repeatedly when a service or scheduled task is running with stale cached credentials after a password change.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Status / Sub Status | Hex NTSTATUS codes for exactly why the logon failed (e.g. 0xC000006A bad password, 0xC0000234 account locked out, 0xC0000072 disabled account): the single most useful field for triage. |
| Logon Type | Same logon-type table as 4624: scopes a brute-force/spray attempt to a specific vector (RDP, network, service, etc.). |
| Account Name (Account For Which Logon Failed) | The targeted account: repeated failures against the same (especially privileged or nonexistent) name signal enumeration or a targeted attack. |
| Source Network Address / Workstation Name | Origin of the failed attempt. Pivot point for spotting one source hammering many accounts (spray) or many sources hammering one account (distributed brute-force). |
| Caller Process Name | Process that attempted the logon, which can expose the tool behind an automated brute-force/spray attempt. |
In practice
Logged when CORP\jsmith fails to authenticate with Logon Type 3 (Network) from Source Network Address 198.51.100.10 and Status 0xC000006A (bad password). A burst of 4625 events for many different account names from the same source address in a short window is a classic password-spraying or brute-force indicator.
Sample record
An account failed to log on. Subject: Security ID: S-1-0-0 Account Name: - Account Domain: - Logon ID: 0x0 Logon Type: 3 Account For Which Logon Failed: Security ID: S-1-0-0 Account Name: jsmith Account Domain: CORP Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xC000006D Sub Status: 0xC000006A Process Information: Caller Process ID: 0x0 Caller Process Name: - Network Information: Workstation Name: WORKSTATION01 Source Network Address: 203.0.113.15 Source Port: 49523 Detailed Authentication Information: Logon Process: NtLmSsp Authentication Package: NTLM Transited Services: - Package Name (NTLM only): - Key Length: 0
ATT&CK techniques
- T1110: Brute Force
Sources
Paste a record into Event XML or open a log in EVTX Reader.