Before sending logs to Splunk, please see the log on-boarding guidelines from ISO as following:
- Use the Splunk Universal Forwarder
- Use the encrypted Syslog service ONLY if you cannot use the Splunk Universal Forwarder
- Use the unencrypted Syslog service ONLY if you cannot use the Splunk Universal Forwarder AND the encrypted Syslog service
For the logs on devices, appliances, and cloud-based applications where Splunk Universal Forwarder cannot be installed, the logs can be sent to Splunk via the Splunk syslog service.
- Encrypted syslog service (server: uitsyslog02 (220.127.116.11), port: 10514).
Using this service, the traffic transmitted between your hosts and the syslog server(uitsyslog02) will be encrypted. It’s recommended to use this service.
- Un-Encrypted syslog service (server: uitsyslog01 (18.104.22.168), port: 514).
Using this service, the traffic transmitted between your hosts and the syslog server(uitsyslog01) will be NOT be encrypted. Use this syslog service ONLY if you cannot use the encrypted syslog service.
Overview of syslog Setup Process
Accessing and setting up the Splunk syslog service will require three parts as outlined below. Detailed instructions for each part follows.
- Request access to the Splunk syslog service.
- Configure your devices to send logs to the Splunk syslog service.
- Validate that the data is onboarding on the Splunk console.
Part 1: Request access to the Splunk syslog service
To request access to the Splunk syslog service, please submit a Help request that includes the following information:
- Specify which Splunk syslog service you want to use: uitsyslog01 or uitsyslog2. If you select uitsyslog01, please state why the encrypted syslog service cannot be used.
- The name and IP address of the source servers.
- The application or service name of the logs.
- The SUNet IDs or work groups who need to access the index.
- Specify any Splunk applications or add-ons as needed.
- Indicate if the daily log volume is more than 100 MB/day.
Part 2: Configure your devices to send logs to the Splunk syslog service
- Configure your devices, appliances, and cloud-based applications to forward logs to the Splunk syslog service (uitsyslog01 or uitsyslog02). If uitsyslog02 is selected, the Splunk team will provide you with a certificate to configure your devices to trust the Splunk syslog service.
- If you have outbound firewall restriction in your local OS firewall or your departmental firewall, you might need to adjust the rules to permit outgoing syslog connections.
Part 3: Validate the data onboarding on splunk console
- The Splunk team will confirm if logs are getting to the Splunk syslog server.
- Once the logs are onboarded, the Splunk team will notify you and provide you with the index name.
- Access https://susplunk.stanford.edu/ and run the following query on the Splunk console, replacing
with the index name provided to you by the Splunk team.