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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Event Series: The Agentic SOC: Trust Before Autonomy

AI is fundamentally changing security operations, but true progress requires more than just automation—it ...

Free Professional Services for .conf26 Attendees

This year at .conf26, we are doing something a little different. We are bringing the best minds from ...

Defend at Machine Speed: Your Guide to Security Sessions at .conf26

Splunk .conf26   With threats moving at machine speed and attack surfaces expanding across hybrid ...