Getting Data In

How to edit inputs.conf to blacklist an eventcode?

t_gayathirik
New Member

I have the following inputs.conf stanza:

[WinEventLog://Security]
    
disabled=0
    
current_only=1
    
blacklist1=EventCode=4662 Message=”Object Type:s+(?!groupPolicyContainer)”

Still we are receiving all the eventcode. Could you please help what else changes has to be made?

Note: We are making the changes in the deployment server for the blacklist

0 Karma
1 Solution

Richfez
SplunkTrust
SplunkTrust

Pulled from my working blacklist of that precise same EventCode and scenario:

blacklist1 = EventCode="4662" Message="Object Type:\s+(?!groupPolicyContainer)"

Not sure if the differences are copy/paste issues or if they're broken in your stanza, but the above has worked for me. Note the \s+.

View solution in original post

0 Karma

Richfez
SplunkTrust
SplunkTrust

Pulled from my working blacklist of that precise same EventCode and scenario:

blacklist1 = EventCode="4662" Message="Object Type:\s+(?!groupPolicyContainer)"

Not sure if the differences are copy/paste issues or if they're broken in your stanza, but the above has worked for me. Note the \s+.

0 Karma

adonio
Ultra Champion

what is the full path to file of the above inputs.conf?
are you leveraging the Splunk TA for Windows?

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!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Register to Attend   Join our Tech Talk ...

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...

Trusted Autonomy in the SOC: A Maturity Journey

AI is compressing attacker timelines and pushing SOC teams beyond human capacity thresholds. The next SOC ...