Sysinternals
Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.
Sysmon 13.30 SourceUser and TargetUser values different than expected for EventID 10
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 9%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHS%3C/text%3E%3C/svg%3E)
Hubert Sękowski
1
Reputation point
Tests done in one sandbox (AWS instance with Windows 2022; security protection disabled).
Events generated with use of mimikatz, where local user was running the tool.
I was getting '<Data Name='SourceUser'>NT AUTHORITY\SYSTEM</Data><Data Name='TargetUser'>IP-0ACA0544\localuser</Data>' in most cases and '<Data Name='SourceUser'>IP-0ACA0544\localuser</Data><Data Name='TargetUser'>NT AUTHORITY\SYSTEM</Data>' in few cases.
Tests done in another sandbox were showing localuser as a TargetUser till first restart of machine and then it was as expected.
I think that can be also observed here: https://github.com/OTRF/OSSEM-DD/issues/26 (vs https://blog.menasec.net/2021/12/detecting-token-stealing-using-sysmon.html )
Sysinternals
Sign in to answer