Getting Data In

What is the workaround for the missing Subject_Account_Name field in WMI Windows security events?

tonopahtaos
Path Finder

Windows security event 4724 and 4738 set Subject_Account_Name if you get these events through Windows universal forwarder locally. But if you do it through WMI, the Subject_Account_Name is set to NULL. Instead, you can see the user name in Account_Name field for both Subject and Target as multiple values. In that case, you do not know which user name is for Subject and which user name is for Target user.

Is there any workaround on this?

Thanks in advance.

0 Karma

ziegfried
Influencer

You can either use inline-extraction of that field using the rex command:

... | rex "(?ims)^subject:.+?account name:\s+(?<Subject_Account_Name>[^\v]+)"

Or you can add this regex to the sourcetype [WMI:WinEventLog:Security] in props.conf:

[WMI:WinEventLog:Security]
EXTRACT-subjectaccountname = (?ims)^subject:.+?account name:\s+(?<Subject_Account_Name>[^\v]+)

tonopahtaos
Path Finder

The second solution works perfectly for me. Thanks a lot.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Design, Compete, Win: Submit Your Best Splunk Dashboards for a .conf26 Pass

Hello Splunkers,  We’re excited to kick off a Splunk Dashboard contest! We know that dashboards are a primary ...

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...

Network to App: Observability Unlocked [May & June Series]

In today’s digital landscape, your environment is no longer confined to the data center. It spans complex ...