Deployment Architecture

prevent specific syslog from routing to 3rd party vendor using UDP:514

afamuyiwa
Engager

Is it possible to prevent specific logs from routing to a 3rd party vendor? We have IPS system that is generating too much logs for our 3rd party vendor. Logs appear fine in our Splunk environment. My only dilemma is that our heavy forwarder receives logs from various network devices sending logs using UDP:514. Other than changing the port number on our IPS systems is their another way to use props.conf and transform.conf to avoid sending logs to a 3rd party vendor and keep the logs in Splunk only?

Tags (1)
0 Karma
1 Solution

starcher
Influencer

The best way is log to a syslog receiver such as syslog-ng or rsylsog. Write data to files and use the Universal forwarder to pick up the logs. It is best to avoid taking syslog straight into Splunk with a network input.

View solution in original post

0 Karma

starcher
Influencer

The best way is log to a syslog receiver such as syslog-ng or rsylsog. Write data to files and use the Universal forwarder to pick up the logs. It is best to avoid taking syslog straight into Splunk with a network input.

0 Karma
Get Updates on the Splunk Community!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...