Getting Data In

How to disable Splunk Web on a universal forwarder?

andylee53
New Member

I use Nessus to scan for SSL issues, and the Splunk Web interface is being flagged due to the self signed certs. I have managed to make my indexer / search head use internally MS CA certs and go the cert chain sorted for the login screen to Splunk Web. My question is, do I use a similar process for the forwarders, or can I shut down the web interface on the Universal forwarder? If so, how? If not, how do I change the certs on the UF?

0 Karma
1 Solution

aosso
Path Finder

If the Nessus detection is on port 8089, you can shut it down by adding this to UF's server.conf:

[httpServer]
disableDefaultPort = true

View solution in original post

aosso
Path Finder

If the Nessus detection is on port 8089, you can shut it down by adding this to UF's server.conf:

[httpServer]
disableDefaultPort = true

dwaddle
SplunkTrust
SplunkTrust

Note: This is NOT disabling SplunkWeb. A UF does not have SplunkWeb ever at all, period. This is disabling the REST API server. This has side effects on the UF, such that the CLI largely (but not completely) quite working. See Matt's .conf talk:

http://conf.splunk.com/files/2016/recordings/universal-forwarder-security-dont-input-more-than-data-...
http://conf.splunk.com/files/2016/slides/universal-forwarder-security-dont-input-more-than-data-into...

Get Updates on the Splunk Community!

Splunk Answers Content Calendar, June Edition

Get ready for this week’s post dedicated to Splunk Dashboards! We're celebrating the power of community by ...

What You Read The Most: Splunk Lantern’s Most Popular Articles!

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...