Security event 4722
A user account was enabled
Channel: Security. Category: User Account Management.
What it records
Records that a previously disabled user account (or, on a domain controller, computer account) was re-enabled, identifying who performed the operation and which account was affected.
Why it matters
Re-enabling a dormant, disabled, or off-boarded account is a way for an attacker to quietly restore access to a credential that defenders assumed was inert. It's also useful for spotting policy violations when an account that should stay disabled comes back to life.
What triggers it
Legitimately triggered by an admin re-enabling an account for a returning employee or after a temporary suspension; worth reviewing when it targets a former employee's account, a built-in account, or occurs outside a documented change window.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Account Name (Subject) | Who re-enabled the account: the operator to verify against expected admin activity. |
| Account Name (Target Account) | Which account was re-enabled. Check whether it belongs to a former employee, a built-in account, or another identity that should have stayed disabled. |
In practice
Account Name (Target Account) jsmith is re-enabled by CORP\itadmin after a returning employee's leave: routine. The same event firing for a former employee's account, or a built-in account, with Subject CORP\svc-web (a service account with no business reason to manage users), looks like an attacker quietly restoring access defenders assumed was inert.
Sample record
A user account was enabled. Subject: Security ID: S-1-5-21-3457937927-2839227994-823803824-1104 Account Name: jsmith Account Domain: CORP Logon ID: 0x2A9F31 Target Account: Security ID: S-1-5-21-3457937927-2839227994-823803824-1108 Account Name: jdoe Account Domain: CORP
Sources
Paste a record into Event XML or open a log in EVTX Reader.