Windows Event ID 4720: A user account was created
Written when a new user account is created. It is a core account-management monitoring event for catching an attacker creating a rogue account (persistence/backdoor).
Overview
The subcategory is Audit User Account Management. It is generated when a new user object is created, recorded on domain controllers, member servers, and workstations alike. It includes the created account name, the creator, and initial attributes.
How it is triggered
- Account creation via
net user /add, AD user creation,New-LocalUser/New-ADUser, APIs, and so on.
Security review points
- After a breach, an attacker may create their own account as a backdoor for re-entry (persistence). Be especially wary if addition to an administrator-level group (4732) follows right after.
- Watch for deviations in the creating subject, time, and naming convention (outside business hours, names that do not follow convention). Also be alert to names that masquerade as service accounts or administrators.
- Together with the following enable 4722, password set, and group addition 4732, track the full sequence of account preparation.
Notes for log review
- It also occurs during legitimate onboarding and operations. Match against the creating subject (HR-system integration vs manual), target OU, and naming convention.
- Creation on a domain controller affects the whole domain. Monitor 4720 on DCs with particular focus.
MITRE ATT&CK mapping
| Technique | Tactic | What this event shows |
|---|---|---|
| T1136.001 Local Account | Persistence | Creation of a local backdoor account |
| T1136.002 Domain Account | Persistence | Creation of a domain backdoor account |
| T1036.010 Masquerade Account Name | Stealth | Names posing as service or admin accounts |
Mapping as of ATT&CK v19.2. ATT&CK detection strategies DET0447 (T1136.001), DET0003 (T1136.002), DET0383 (T1036.010) also list this event ID as a log source. To search by technique, see the ATT&CK reverse lookup.
Detection rules
SigmaHQ has 4 and Microsoft Sentinel has 6 public detection rules that use this event ID as a condition.
| Rule | Type | Severity |
|---|---|---|
| Hidden Local User Creation | Sigma | High |
| Suspicious Windows ANONYMOUS LOGON Local Account Created | Sigma | High |
| Fake computer account created | Sentinel analytics rule | Medium |
| New or Renamed User Account with ‘$’ Character | Sigma | Medium |
| User account created and deleted within 10 mins | Sentinel analytics rule | Medium |
| Local User Creation | Sigma | Low |
| New user created and added to the built-in administrators group | Sentinel analytics rule | Low |
| Long lookback User Account Created and Deleted within 10mins | Sentinel hunting query | - |
| Tracking Privileged Account Rare Activity | Sentinel hunting query | - |
| User created by unauthorized user | Sentinel hunting query | - |
Rules are collected from SigmaHQ r2026-07-01 and from Azure-Sentinel as of 2026-10-09, limited to those whose conditions include this event ID. Sentinel rules are limited to those that query the SecurityEvent or WindowsEvent table. “Threat-specific” rules target a particular threat group or malware, and “needs setup” rules require values for your environment. Severity is the value each rule’s author assigned.
Key fields
| Field | Meaning |
|---|---|
New Account\Account Name | The created account name |
Subject\Account Name | The subject that created the account |
SAM Account Name / attributes | The initially set attributes |