Windows Security 4720 — User account created

Source and collection

Windows Event Log: Security; archived .evtx is binary, while this fixture is an XML event export.

Configure Audit User Account Management. Read with Get-WinEvent and preserve provider, event ID, version, computer and record ID.

Native example and provenance

publisher documentation example. Published example; no independent capture provenance claimed.

Original publisher / pinned upstream fixture — preformatted example 1

Removed Event Viewer tree expansion markers before XML tags; field values unchanged.

Download the exact sample · Offline research kit

SHA-256: 673f8413d30a0332087f3fa17c1bf443f74bbf1c14af10e30ca9870e81e1167b

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> 
 <EventID>4720</EventID> 
 <Version>0</Version> 
 <Level>0</Level> 
 <Task>13824</Task> 
 <Opcode>0</Opcode> 
 <Keywords>0x8020000000000000</Keywords> 
 <TimeCreated SystemTime="2015-08-20T16:22:02.759912000Z" /> 
 <EventRecordID>175408</EventRecordID> 
 <Correlation /> 
 <Execution ProcessID="520" ThreadID="1508" /> 
 <Channel>Security</Channel> 
 <Computer>DC01.contoso.local</Computer> 
 <Security /> 
 </System>
<EventData>
 <Data Name="TargetUserName">ksmith</Data> 
 <Data Name="TargetDomainName">CONTOSO</Data> 
 <Data Name="TargetSid">S-1-5-21-3457937927-2839227994-823803824-6609</Data> 
 <Data Name="SubjectUserSid">S-1-5-21-3457937927-2839227994-823803824-1104</Data> 
 <Data Name="SubjectUserName">dadmin</Data> 
 <Data Name="SubjectDomainName">CONTOSO</Data> 
 <Data Name="SubjectLogonId">0x30dc2</Data> 
 <Data Name="PrivilegeList">-</Data> 
 <Data Name="SamAccountName">ksmith</Data> 
 <Data Name="DisplayName">Ken Smith</Data> 
 <Data Name="UserPrincipalName">ksmith@contoso.local</Data> 
 <Data Name="HomeDirectory">-</Data> 
 <Data Name="HomePath">-</Data> 
 <Data Name="ScriptPath">-</Data> 
 <Data Name="ProfilePath">-</Data> 
 <Data Name="UserWorkstations">-</Data> 
 <Data Name="PasswordLastSet">%%1794</Data> 
 <Data Name="AccountExpires">%%1794</Data> 
 <Data Name="PrimaryGroupId">513</Data> 
 <Data Name="AllowedToDelegateTo">-</Data> 
 <Data Name="OldUacValue">0x0</Data> 
 <Data Name="NewUacValue">0x15</Data> 
 <Data Name="UserAccountControl">%%2080 %%2082 %%2084</Data> 
 <Data Name="UserParameters">-</Data> 
 <Data Name="SidHistory">-</Data> 
 <Data Name="LogonHours">%%1793</Data> 
 </EventData>
 </Event>

Structure and field interpretation

System/EventID

Event identifier within the named provider.

System/Version

Version of this event layout.

System/TimeCreated/@SystemTime

Event timestamp in UTC.

EventData

Named fields; use names, not positional array indices.

Relevant fields

TargetUserName, TargetSid, SubjectUserName

Investigation uses

• Correlate the acting account, change record and subsequent group membership or authentication.
• Compare event time with ingestion time and retain the original XML for a reviewable evidence trail.

Validation boundaries

Local and domain accounts differ; the event does not establish authorization or successful account use. This sample uses event version 0.

This sample passed byte-integrity and JSON/XML parsing checks, including the catalogue’s specified event discriminators. This is not a complete vendor-schema validation or a tested detection.

For a simulation, first parse this fixture offline, then create a separately labelled synthetic variant and test it against the intended collector in an isolated lab. Never replay public example identities or destinations into production.

Related sources

• Windows Security 4624 — Successful logon
• Windows Security 4625 — Failed logon
• Windows Security 4688 — Process creation
• Windows Security 4698 — Scheduled task created
• Windows Security 4732 — Member added to local security group
• Windows Security 4740 — Account locked out

Ecosystem connections

• Telemetry Library — ATT&CK data components
• Detection Rules — candidate detection content
• Threat hunting — from intelligence to validated defense
• Practical security learning paths
• AdversaryGraph — evidence-led investigation

References

• 4720(S) A user account was created. - Windows 10 | Microsoft Learn

Sample provenance is linked above. Field availability and product behavior must be checked against the deployed version.