Skip to content

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

TechniqueTacticWhat this event shows
T1136.001 Local AccountPersistenceCreation of a local backdoor account
T1136.002 Domain AccountPersistenceCreation of a domain backdoor account
T1036.010 Masquerade Account NameStealthNames 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.

RuleTypeSeverity
Hidden Local User CreationSigmaHigh
Suspicious Windows ANONYMOUS LOGON Local Account CreatedSigmaHigh
Fake computer account createdSentinel analytics ruleMedium
New or Renamed User Account with ‘$’ CharacterSigmaMedium
User account created and deleted within 10 minsSentinel analytics ruleMedium
Local User CreationSigmaLow
New user created and added to the built-in administrators groupSentinel analytics ruleLow
Long lookback User Account Created and Deleted within 10minsSentinel hunting query-
Tracking Privileged Account Rare ActivitySentinel hunting query-
User created by unauthorized userSentinel 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

FieldMeaning
New Account\Account NameThe created account name
Subject\Account NameThe subject that created the account
SAM Account Name / attributesThe initially set attributes

References