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!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

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