Getting Data In

Why are all events being filter except for EventCode 0 when filtering Windows Events?

splunkcol
Builder

Hi

I'm filtering windows events from the Heavy Forwarder, everything works fine, all events are filtered except for EventCode = 0 any idea why?

 

splunkcol_1-1628884389005.pngsplunkcol_1-1628884389005.png

 

splunkcol_2-1628884418013.pngsplunkcol_2-1628884418013.png

 

 

0 Karma
1 Solution

splunkcol
Builder

 

EventCode 0 was not being filtered because it is an Application event and not a security event.

In this way I solved it

 

props.conf

[source::WinEventLog:Application]
TRANSFORMS-wmi = setnull2

 


transforms.conf

[setnull2]
REGEX= (?msi) ^EventCode=(0)
DEST_KEY=queue
FORMAT=nullQueue

View solution in original post

0 Karma

splunkcol
Builder

 

EventCode 0 was not being filtered because it is an Application event and not a security event.

In this way I solved it

 

props.conf

[source::WinEventLog:Application]
TRANSFORMS-wmi = setnull2

 


transforms.conf

[setnull2]
REGEX= (?msi) ^EventCode=(0)
DEST_KEY=queue
FORMAT=nullQueue

0 Karma

jdhunter
Path Finder

We were able to filter it out from the UF using the following in our inputs.conf:

[WinEventLog://Application]
disabled = 0
index = windows_index
blacklist1 = EventCode="0"

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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

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