Getting Data In

Trouble Blacklisting Event Codes

kymenope
Explorer

My inputs.conf from the deployment server (confirmed that it is being pushed to all hosts correctly):

{WinEventLog://Security}

 

index = wineventlog

sourcetype = WinEventLog:Security

disabled = 0

whitelist = EventCode="0-6000"

blacklist = EventCode="1,2,3,4,"

 

Substituted other values for the blacklisted ones.  Despite being explicitly disallowed all host forwarders are still collecting and forwarding these events to the indexer.  Am I misconfiguring this?

Labels (1)
0 Karma
1 Solution

PickleRick
SplunkTrust
SplunkTrust

Yes, you are.

white/blacklist has two options.

1. You explicitly list (dis)allowed event codes

blacklist1=17,234,4762-4767

2. You specify key=regex to match (caveat - doesn't work with xml rendered events; in this case you need another setting)

blacklist1 = EventCode=%47..%

You tried to use the second option to do the first one.

View solution in original post

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Yes, you are.

white/blacklist has two options.

1. You explicitly list (dis)allowed event codes

blacklist1=17,234,4762-4767

2. You specify key=regex to match (caveat - doesn't work with xml rendered events; in this case you need another setting)

blacklist1 = EventCode=%47..%

You tried to use the second option to do the first one.

0 Karma

marnall
Builder

Try setting it like this:

[WinEventLog://Security]
index = wineventlog
sourcetype = WinEventLog:Security
disabled = 0
whitelist = 0-6000
blacklist = 1,2,3,4
0 Karma
Get Updates on the Splunk Community!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

(view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...