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
Motivator

Try setting it like this:

[WinEventLog://Security]
index = wineventlog
sourcetype = WinEventLog:Security
disabled = 0
whitelist = 0-6000
blacklist = 1,2,3,4
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!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...