Windows Security 5136 — Directory object modified

Source and collection

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

Configure Audit Directory Service Changes plus applicable SACL. 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: adb342ed79addd4139ff9008d03852b70102b7d696baed95012fb5ca49c73c3a

<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>5136</EventID> 
 <Version>0</Version> 
 <Level>0</Level> 
 <Task>14081</Task> 
 <Opcode>0</Opcode> 
 <Keywords>0x8020000000000000</Keywords> 
 <TimeCreated SystemTime="2015-08-28T17:36:04.129472600Z" /> 
 <EventRecordID>410204</EventRecordID> 
 <Correlation /> 
 <Execution ProcessID="516" ThreadID="4020" /> 
 <Channel>Security</Channel> 
 <Computer>DC01.contoso.local</Computer> 
 <Security /> 
 </System>
<EventData>
 <Data Name="OpCorrelationID">{02647639-8626-43CE-AFE6-7AA1AD657739}</Data> 
 <Data Name="AppCorrelationID">-</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">0x32004</Data> 
 <Data Name="DSName">contoso.local</Data> 
 <Data Name="DSType">%%14676</Data> 
 <Data Name="ObjectDN">CN=Sergey,CN=Builtin,DC=contoso,DC=local</Data> 
 <Data Name="ObjectGUID">{4FE80A66-5F93-4F73-B215-68678058E613}</Data> 
 <Data Name="ObjectClass">user</Data> 
 <Data Name="AttributeLDAPDisplayName">userAccountControl</Data> 
 <Data Name="AttributeSyntaxOID">2.5.5.9</Data> 
 <Data Name="AttributeValue">512</Data> 
 <Data Name="OperationType">%%14675</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

ObjectDN, AttributeLDAPDisplayName, AttributeValue, OperationType

Investigation uses

• Review sensitive attribute changes, the actor and replication or administrative context.
• Compare event time with ingestion time and retain the original XML for a reviewable evidence trail.

Validation boundaries

A modification can produce separate value-deleted and value-added records; preserve correlation and operation fields. 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 4720 — User account created
• Windows Security 4732 — Member added to local security group

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

• DC0066 — conceptual telemetry association, not coverage proof

References

• 5136(S) A directory service object was modified. - Windows 10 | Microsoft Learn

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