Security

Hardening: \en-US\Modules

rogerroger
New Member

Adding this to the end of my SPlunk URl allows standard users to see all the modules loaded. I do not want the end users to be able to see what is loaded. Does anyone know how to harden splunk to only allow access to the URl provided?

I created an App and locked the user to that app but it seems like it dod not work for this.

Tags (1)
0 Karma

martin_mueller
SplunkTrust
SplunkTrust

You could take an axe to $SPLUNK_HOME/Python-2.7/Lib/site-packages/splunk/appserver/mrsparkle/controllers/top.py and for example add a redirect to its modules page at around L150:

@expose_page(must_login=True)
def modules(self, **kwargs):
    self.redirect_to_url('/') # added
    return                    # added
    """
    Generates an HTML page documenting all registered modules
    """
    ...

That's not a very pretty approach, and obviously not update-safe... but should do the job. Remember to restart splunkweb after making changes.

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...