Getting Data In

WinEventLog:Security filtering does not work

arapozo
Explorer

Even after reading the documentation and a lot of posts here on answers, I just can't get filtering to work. I've recently installed two VM to test it out.

One indexer server and one universal forwarder. The configuration is being done in the Indexer since universal forwarder according to the docs doesn't do parsing.

REGEX is set to "." to test if the filtering is working.

SPLUNK\etc\system\local\props.conf
[WinEventLog:Security]
TRANSFORMS-setnull = setnull

SPLUNK\etc\system\local\transforms.conf
[setnull]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue

Isn't this configuration supposed to filter everything from WinEventLog:Security?
I get all the logs anyways.

Additional information that may be related:

http://answers.splunk.com/questions/13196/universal-forwarder-sending-cooked-data-to-indexer

1 Solution

Ellen
Splunk Employee
Splunk Employee

You have run into a known issue (SPL-38443) with the 4.2 Lightweight and Universal Forwarder.

The Windows 4.2 lightweight and universal forwarder parses WinEventLog datastreams on the forwarder, preventing all parsing control on the indexer.

The symptoms of this are: no filtering nor routing to the nullqueue based on props and transforms. WinEventLog data is bypassing props.conf and transforms.conf on the indexer.

The workaround would be to use a 4.2 full/regular forwarder or 4.1.x lightweight forwarder but this will be fixed for 4.2.1

http://www.splunk.com/base/Documentation/latest/ReleaseNotes/Knownissues

View solution in original post

Ellen
Splunk Employee
Splunk Employee

You have run into a known issue (SPL-38443) with the 4.2 Lightweight and Universal Forwarder.

The Windows 4.2 lightweight and universal forwarder parses WinEventLog datastreams on the forwarder, preventing all parsing control on the indexer.

The symptoms of this are: no filtering nor routing to the nullqueue based on props and transforms. WinEventLog data is bypassing props.conf and transforms.conf on the indexer.

The workaround would be to use a 4.2 full/regular forwarder or 4.1.x lightweight forwarder but this will be fixed for 4.2.1

http://www.splunk.com/base/Documentation/latest/ReleaseNotes/Knownissues

MuS
SplunkTrust
SplunkTrust

Hi Ellen,
is this really solved in 4.2.1 universal forwarder? I just ran into exactly this problem, that I was unable to redirect WinEventLog events no matter what transform I used. Only way to get them into different indexes was to set the index in inputs.conf on the 4.2.1 universal forwarder.

best regards, MuS

0 Karma

arapozo
Explorer

I just installed the forwarder and only selected the security log in the wizard, nothing else.

0 Karma

jbsplunk
Splunk Employee
Splunk Employee

What does the input on the Universal Forwarder use to get data from the event logs?

0 Karma

arapozo
Explorer

I'm not using WMI to collect events, the source is always a universal forwarder.

0 Karma
Get Updates on the Splunk Community!

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened Audit Trail v2 wasn’t written in isolation—it was shaped by your voices. In ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

 Prepare to elevate your security operations with the powerful upgrade to Splunk Enterprise Security 8.x! This ...

Get Early Access to AI Playbook Authoring: Apply for the Alpha Private Preview ...

Passionate about security automation? Apply now to our AI Playbook Authoring Alpha private preview ...