I have a situation when I need to dump a remote Security log with wevtutil and subseqently upload it into Splunk to cross-correlate it with XmlWinEventlog sourcetype logs.
I hoped that the XML structure of wevtutil XML file is the same as the structure of the file received by Splunk from Universal Forwarders. It looks like it is not the case.
I tried to upload the XML file into Splunk, but for some reason Splunk converts it into a bunch of unicode characters rather than recognizing it as XML file. Selecting XmlWinEventlog sourcetype did not help either.
I wonder if anyone managed to load XML file created by wevtutil utility into Splunk with proper field extraction.
Thank you.