Getting Data In

What is the proper syntax to whitelist a single EventCode from wineventlog security with a UF ?

Glasses
Builder

Hi - 

Not having any luck testing or finding the answer in documentation so hopefully someone can confirm.

 

I want to collect a single EventCode=4624 from a Windows Server with a UF (v 8.0.6).

I am using an inputs.conf stanza like this>>>

#2021.4.19
[WinEventLog://Security]
disabled = 0
index=foo
whitelist1 = EventCode=4624

I am still collecting all wineventlog security EventCodes.

Any ideas?

TY!

0 Karma
1 Solution

Glasses
Builder

Actually the issue was something with the UF not restarting splunkd.   

 

This stanza does work now... 

[WinEventLog://Security]
disabled = 0
index=foo
whitelist = 4624

View solution in original post

0 Karma

Glasses
Builder

Even tried >>>

 

whitelist = 4624

 

no luck 😞

 

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @Glasses,

whitelist and blacklist require regexes, so, please, try:

whitelist1 = EventCode\=4624

then, are your logs in json or normal format? if in json the regex is different.

Ciao.

Giuseppe

Glasses
Builder

Actually the issue was something with the UF not restarting splunkd.   

 

This stanza does work now... 

[WinEventLog://Security]
disabled = 0
index=foo
whitelist = 4624

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!

Event Series: Splunk Observability Metrics Cost Optimization

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...