Getting Data In

How do I edit my inputs.conf to blacklist Windows event logs with Eventcode 7036 on my Splunk 6.1.3 universal forwarder?

chrisbaker
New Member

Hi,

I'm trying to use blacklist on the Universal Forwarder to prevent unwanted events from being sent and indexed. Splunk instance and UF are both version 6.1.3
On the machine with UF, I went to C:\Program Files\SplunkUniversalForwarder\etc\system\local
The inputs.conf file looks like this:

 [default]
 host = Win7HP8440p

 [script://$SPLUNK_HOME\bin\scripts\splunk-wmi.path]

So I added a stanza as shown in many models and now it looks like this:

 [default]
 host = Win7HP8440p

 [WinEventLog://System]
 disabled = false
 blacklist1 = 7036

 [script://$SPLUNK_HOME\bin\scripts\splunk-wmi.path]

I rebooted the host with the UF and then checked on the Splunk instance and Event code 7036 keeps coming through.
I have tried many variations to match the examples I have seen ( like disabled = 0 or removing spaces around = signs etc.) but so far nothing seems to work.

Any suggestions?

0 Karma

juvetm
Communicator

hi
are you using the advanced filtering format

0 Karma

chrisbaker
New Member

How do I check for that? I don't see anything in the docs.

0 Karma

satishsdange
Builder

Any reason to add 1 to blacklist? It could be simply "blacklist = 7036"

0 Karma

chrisbaker
New Member

I've tried with and without the 1. I saw it as "blacklist1" in some examples.

0 Karma
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...