Hi,
I'm uncertain which Process name—CreatorProcessName, ParentProcessName, or NewProcessName—is the appropriate one to apply windows events blacklisting in this context.
Thanks..
I don't know why Splunk is not matching that event. The regex looks good to me. Perhaps try without the groups? It shouldn't matter, but perhaps it will and the groups are not necessary.
Hi
Can you pls give me and eg. for above regex with out group ?
Thanks
ParentProcessName.+Microsoft Monitoring Agent\\Agent\\MonitoringHost\.exe
Can we use the props and transforms to send the unwanted events to null queue aas the applied regex are not working!
Yes, the indexers or heavy forwarders can use the regex to discard matching events.
@richgalloway ,
is this with quotes ?
blacklist5 = EventCode="4688" Message="(ParentProcessName.+Microsoft Monitoring Agent\\Agent\\MonitoringHost\.exe)"
You asked for a regex so that is what I gave you. Add quotes and other text as necessary.
Hello, @richgalloway @PickleRick ,
The regex I used seems effective, but it's unexpectedly blocking all my Windows security events. I've checked the regex, and I haven't specifically blacklisted any Windows executables. Could you assist me in analyzing the below list of blacklisted executables?
@AL3Z wrote:# DO NOT EDIT THIS FILE!# Please make all changes to files in $SPLUNK_HOME/etc/apps/Splunk_TA_windows/local.
# To make changes, copy the section/stanza you want to change from $SPLUNK_HOME/etc/apps/Splunk_TA_windows/default
# into ../local and edit there.
Stop right there! These comments are very important and yet you've chosen to ignore them by editing a file that should not be modified. What other instructions have you disregarded?
The configs shown look good to me, but I am not familiar enough with Windows to know if there's something there that shouldn't be there or vice versa.
I have made changes to local inputs.conf on this app and deployed it to over 3k servers so we need to move these configurations from local to default to get it work ?
Thanks..
It will work as it is, but it is poor practice. Your changes will be lost the next time Splunk_TA_windows is upgraded.