Getting Data In

WinEventLog WhiteList 4662

richardphung
Communicator

Greetings--

I am trying to set-up an WinEventLog inputs.conf whitelist for LAPS (EventCode=4662).

These events have a similar structure in so far as:

 

Object:
Object Server: DS
Object Type: computer
Object Name: CN=hostname

 



Which looks something like...

 

[WinEventLog://Security]
disabled = 0
index = wineventlog
checkpointInterval = 5
blacklist1 = EventCode="4660" Message="Process Name:\s+(?i)(?:[C-F]:\\Program Files\\Splunk(?:UniversalForwarder)?\\bin\\(?:btool|splunkd|splunk|splunk-(?:MonitorNoHandle|admon|netmon|optimizer|perfmon|powershell|regmon|winevtlog|winhostinfo|winprintmon|wmi))\.exe)"
blacklist2 = EventCode="4662" Message="Object Type:\s+(?!groupPolicyContainer)"
blacklist3 = EventCode="4663" Message="Process Name:\s+(?i)(?:[C-F]:\\Program Files\\Splunk(?:UniversalForwarder)?\\bin\\(?:btool|splunkd|splunk|splunk-(?:MonitorNoHandle|admon|netmon|optimizer|perfmon|powershell|regmon|winevtlog|winhostinfo|winprintmon|wmi))\.exe)"
blacklist4 = EventCode="566" Message="Object Type:\s+(?!groupPolicyContainer)"
blacklist5 = EventCode="4688" Message="New Process Name: (?i)(?:[C-F]:\\Program Files\\Splunk(?:UniversalForwarder)?\\bin\\(?:btool|splunkd|splunk|splunk-(?:MonitorNoHandle|admon|netmon|optimizer|perfmon|powershell|regmon|winevtlog|winhostinfo|winprintmon|wmi))\.exe)"
whitelist = EventCode="4662" Message\="Object Type:(.*)computer([\s\S]*)Object Name:(.*)CN="

 


This seems to block all EventCode=4662

I have tried to do something to the effect of:

 

EventCode=%^4662$%

 

Per https://community.splunk.com/t5/Getting-Data-In/inputs-conf-Windows-event-whitelist/m-p/502836#M8565...

Labels (3)
0 Karma

richardphung
Communicator

An interesting turn of events..

It looks like the events ARE being indexed..

but instead of Object Type: computer, Object Name: hostname, they are coming in as:

Object:
	Object Server:		DS
	Object Type:		%{bf967a86-0de6-11d0-a285-00aa003049e2}
	Object Name:		%{fbdc83b5-af6f-4dd2-8256-458e8e1348e2}
	Handle ID:		0x0

 

Not sure why...
In the local event viewer, it is resolving the GUID

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...