Security event 4740
A user account was locked out
Channel: Security. Category: User Account Management.
What it records
Records that a user account was locked out after exceeding the configured failed-logon threshold, including the account performing the lockout (almost always SYSTEM) and the Caller Computer Name the failed attempts originated from.
Why it matters
A wave of 4740 events across many accounts is a clear signal of a password-guessing, brute-force, or password-spraying attack in progress, and Caller Computer Name helps pinpoint the source host to isolate.
What triggers it
Legitimately triggered by a user mistyping their password repeatedly, or by a stale cached credential (phone, mapped drive, scheduled task) retrying an old password after a change; maliciously triggered by automated password-guessing tools against one or many accounts.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Account That Was Locked Out > Security ID | Identifies exactly which account was locked out: the target of the failed-logon activity that triggered the lockout. |
| Additional Information > Caller Computer Name | The computer the failed logon attempts originated from. Pivot point for isolating the source of a brute-force or password-spray attack. |
In practice
Account That Was Locked Out > Security ID resolves to CORP\jsmith, with Additional Information > Caller Computer Name showing WKSTN-0459. When dozens of 4740 events for different accounts all cite the same Caller Computer Name within a short window, that host is very likely running a password-spraying tool and should be isolated.
Sample record
A user account was locked out. Subject: Security ID: S-1-5-18 Account Name: WIN-DC01$ Account Domain: CORP Logon ID: 0x3E7 Account That Was Locked Out: Security ID: S-1-5-21-3457937927-2839227994-823803824-1142 Account Name: jsmith Additional Information: Caller Computer Name: WKSTN-0459
Sources
Paste a record into Event XML or open a log in EVTX Reader.