Windows Security 4624 — Successful logon

Source and collection

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

Configure Audit Logon. 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

One complete record selected; values unchanged.

Download the exact sample · Offline research kit

SHA-256: bb50c59c7ad1c1bca2fb442534bb3dd3a3388274f58a1824cd1ff77d14a95b50

<?xml version="1.0"?>
<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>4624</EventID>
        <Version>2</Version>
        <Level>0</Level>
        <Task>12544</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8020000000000000</Keywords>
        <TimeCreated SystemTime="2015-11-12T00:24:35.079785200Z"/>
        <EventRecordID>211</EventRecordID>
        <Correlation ActivityID="{00D66690-1CDF-0000-AC66-D600DF1CD101}"/>
        <Execution ProcessID="716" ThreadID="760"/>
        <Channel>Security</Channel>
        <Computer>WIN-GG82ULGC9GO</Computer>
        <Security/>
    </System>
    <EventData>
        <Data Name="SubjectUserSid">S-1-5-18</Data>
        <Data Name="SubjectUserName">WIN-GG82ULGC9GO$</Data>
        <Data Name="SubjectDomainName">WORKGROUP</Data>
        <Data Name="SubjectLogonId">0x3e7</Data>
        <Data Name="TargetUserSid">S-1-5-21-1377283216-344919071-3415362939-500</Data>
        <Data Name="TargetUserName">Administrator</Data>
        <Data Name="TargetDomainName">WIN-GG82ULGC9GO</Data>
        <Data Name="TargetLogonId">0x8dcdc</Data>
        <Data Name="LogonType">2</Data>
        <Data Name="LogonProcessName">User32</Data>
        <Data Name="AuthenticationPackageName">Negotiate</Data>
        <Data Name="WorkstationName">WIN-GG82ULGC9GO</Data>
        <Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
        <Data Name="TransmittedServices">-</Data>
        <Data Name="LmPackageName">-</Data>
        <Data Name="KeyLength">0</Data>
        <Data Name="ProcessId">0x44c</Data>
        <Data Name="ProcessName">C:\\Windows\\System32\\svchost.exe</Data>
        <Data Name="IpAddress">127.0.0.1</Data>
        <Data Name="IpPort">0</Data>
        <Data Name="ImpersonationLevel">%%1833</Data>
        <Data Name="RestrictedAdminMode">-</Data>
        <Data Name="TargetOutboundUserName">-</Data>
        <Data Name="TargetOutboundDomainName">-</Data>
        <Data Name="VirtualAccount">%%1843</Data>
        <Data Name="TargetLinkedLogonId">0x0</Data>
        <Data Name="ElevatedToken">%%1842</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

TargetLogonId, LogonType, IpAddress

Investigation uses

• Investigate unusual logon types and source addresses; correlate the target logon ID with subsequent activity.
• Compare event time with ingestion time and retain the original XML for a reviewable evidence trail.

Validation boundaries

LogonType distinguishes interactive, network and other sessions; a successful logon is not itself compromise. This sample uses event version 2.

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 4625 — Failed logon
• Windows Security 4688 — Process creation
• Windows Security 4698 — Scheduled task created
• Windows Security 4720 — User account 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

• DC0067 — conceptual telemetry association, not coverage proof

References

• 4624(S) An account was successfully logged on. - Windows 10 | Microsoft Learn

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