4767 Security log · Account Management low severity low volume

Windows Event ID 4767 — A user account was unlocked

A locked account was unlocked. SubjectUserName=who unlocked, TargetUserName=account unlocked.

Why event 4767 matters

Attacker with admin access may unlock their own backdoor account or unlock accounts to remove lockout indicators.

How to detect it

Alert: unlocked outside business hours. Correlate with 4625/4740 to understand lockout cause. Unlock without a help-desk ticket is suspicious.

Log source
Security
Advanced Audit Policy — enable the 'Account Management' subcategory (Success and/or Failure).
Fields to pivot on
SubjectUserNameTargetUserNameLogonTypeIpAddressWorkstationName

Detection queries

Starting points — adapt the log source, projected fields and thresholds for your environment.

Sentinel / Defender KQL
SecurityEvent
| where EventID == 4767   // A user account was unlocked
| project TimeGenerated, Computer, SubjectUserName, TargetUserName, LogonType, IpAddress, WorkstationName
| sort by TimeGenerated desc
Splunk SPL
index=* sourcetype="WinEventLog:Security" EventCode=4767
| stats count earliest(_time) as first_seen latest(_time) as last_seen by ComputerName
| sort - count   `# A user account was unlocked — add EventData fields: SubjectUserName, TargetUserName, LogonType, IpAddress`
Hunt event 4767 in Sentinel/Defender →
Build a KQL query for this event in the KQL Query Builder.
Search all event IDs →
Open the interactive Windows Event ID lookup.

Related Account Management events

4720 A user account was created 4722 A user account was enabled 4723 An attempt was made to change an account's password 4724 An attempt was made to reset an account's password 4725 A user account was disabled 4726 A user account was deleted 4728 A member was added to a security-enabled global group 4729 A member was removed from a security-enabled global group 4730 A security-enabled global group was deleted 4731 A security-enabled local group was created 4732 A member was added to a security-enabled local group 4733 A member was removed from a security-enabled local group

Frequently asked questions

What is Windows Event ID 4767?

A user account was unlocked. A locked account was unlocked. SubjectUserName=who unlocked, TargetUserName=account unlocked.

Which log records event 4767?

Event 4767 is written to the Security channel by Microsoft-Windows-Security-Auditing. Advanced Audit Policy — enable the 'Account Management' subcategory (Success and/or Failure).

How do you detect activity around event 4767?

Alert: unlocked outside business hours. Correlate with 4625/4740 to understand lockout cause. Unlock without a help-desk ticket is suspicious.