Getting Data In

Why isn't whitelisting for universal forwarder working in Splunk v6.6.3?

hrithiktej
Communicator

I am using UF 6.6.3.0 on my domain controller and following is my inputs.conf. The whitelisting part is not working I am seeing all event codes.

[WinEventLog://Security]
disabled = 0
start_from = newest
current_only = 1
evt_resolve_ad_obj = 0
checkpointInterval = 5

only index events with these event IDs.

whitelist = 4723,4724,4740,4782
index = wineventlog
renderXml=false

1 Solution

hrithiktej
Communicator

I figured this out here is my new inputs.conf.

IF YOU DONT TYPE blacklist it will not understand whitelist

[WinEventLog://Security]
disabled = 0
start_from = newest
current_only = 1
evt_resolve_ad_obj = 0
checkpointInterval = 5

only index events with these event IDs.

whitelist = 4723,4724,4740,4782

exclude these event IDs from being indexed.

blacklist = 1100-8191
index = wineventlog
renderXml=false

View solution in original post

hrithiktej
Communicator

I figured this out here is my new inputs.conf.

IF YOU DONT TYPE blacklist it will not understand whitelist

[WinEventLog://Security]
disabled = 0
start_from = newest
current_only = 1
evt_resolve_ad_obj = 0
checkpointInterval = 5

only index events with these event IDs.

whitelist = 4723,4724,4740,4782

exclude these event IDs from being indexed.

blacklist = 1100-8191
index = wineventlog
renderXml=false

gcusello
SplunkTrust
SplunkTrust

Hi hrithiktej,
in whitelist you have to insert regexes (see http://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf ).
So in your case, if 4723,4724,4740,4782 are only numbers, try

whitelist = 4723|4724|4740|4782

if they are EventCodes, try

whitelist = EventCode\=4723|EventCode\=4724|EventCode\=4740|EventCode\=4782

(check if in your events EvenCode is written as EventCode or EventID)

Bye.
Giuseppe

hrithiktej
Communicator

thanks for your reply .please check my resolution for this issue below

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 ...