CyberKit

Event IDs

Security event 4767

A user account was unlocked

Channel: Security. Category: User Account Management.

What it records

Records that a previously locked-out user account was unlocked, identifying who performed the unlock and which account was affected.

Why it matters

Correlating this with the preceding 4740 lockout events helps distinguish a routine help-desk unlock from an attacker unlocking an account they just brute-forced, or one they compromised via a help-desk social-engineering call.

What triggers it

Legitimately triggered by a help-desk technician or manager unlocking the account via Active Directory Users and Computers; worth reviewing when it follows a lockout that wasn't reported by the legitimate user.

Fields that carry the answer

Key fields
FieldWhat it tells you
Subject > Account NameThe account that performed the unlock. Verify it's a legitimate help-desk or admin action rather than an attacker unlocking an account they just brute-forced.
Target Account > Account NameThe account that was unlocked. Correlate with preceding 4740 lockout events to see whether the unlock was expected.

In practice

Help-desk technician CORP\jsmith unlocks CORP\jdoe's account after several failed logons; Subject > Account Name shows CORP\jsmith and Target Account > Account Name shows CORP\jdoe. Routine when it follows a 4740 lockout jdoe reported, but worth investigating if the preceding lockout wasn't reported by jdoe at all.

Sample record

A user account was unlocked.

Subject:
	Security ID:		S-1-5-21-3623811015-3361044348-30300820-500
	Account Name:		administrator
	Account Domain:		CORP
	Logon ID:		0x3E7

Target Account:
	Security ID:		S-1-5-21-3623811015-3361044348-30300820-1104
	Account Name:		jsmith
	Account Domain:		CORP

Sources

Paste a record into Event XML or open a log in EVTX Reader.