<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Hardening: \en-US\Modules in Security</title>
    <link>https://community.splunk.com/t5/Security/Hardening-en-US-Modules/m-p/122466#M3753</link>
    <description>&lt;P&gt;You could take an axe to &lt;CODE&gt;$SPLUNK_HOME/Python-2.7/Lib/site-packages/splunk/appserver/mrsparkle/controllers/top.py&lt;/CODE&gt; and for example add a redirect to its &lt;CODE&gt;modules&lt;/CODE&gt; page at around L150:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;@expose_page(must_login=True)
def modules(self, **kwargs):
    self.redirect_to_url('/') # added
    return                    # added
    """
    Generates an HTML page documenting all registered modules
    """
    ...
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;That's not a very pretty approach, and obviously not update-safe... but should do the job. Remember to restart splunkweb after making changes.&lt;/P&gt;</description>
    <pubDate>Mon, 07 Apr 2014 20:40:09 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2014-04-07T20:40:09Z</dc:date>
    <item>
      <title>Hardening: \en-US\Modules</title>
      <link>https://community.splunk.com/t5/Security/Hardening-en-US-Modules/m-p/122465#M3752</link>
      <description>&lt;P&gt;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? &lt;/P&gt;

&lt;P&gt;I created an App and locked the user to that app but it seems like it dod not work for this.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2014 17:36:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Hardening-en-US-Modules/m-p/122465#M3752</guid>
      <dc:creator>rogerroger</dc:creator>
      <dc:date>2014-04-07T17:36:44Z</dc:date>
    </item>
    <item>
      <title>Re: Hardening: \en-US\Modules</title>
      <link>https://community.splunk.com/t5/Security/Hardening-en-US-Modules/m-p/122466#M3753</link>
      <description>&lt;P&gt;You could take an axe to &lt;CODE&gt;$SPLUNK_HOME/Python-2.7/Lib/site-packages/splunk/appserver/mrsparkle/controllers/top.py&lt;/CODE&gt; and for example add a redirect to its &lt;CODE&gt;modules&lt;/CODE&gt; page at around L150:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;@expose_page(must_login=True)
def modules(self, **kwargs):
    self.redirect_to_url('/') # added
    return                    # added
    """
    Generates an HTML page documenting all registered modules
    """
    ...
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;That's not a very pretty approach, and obviously not update-safe... but should do the job. Remember to restart splunkweb after making changes.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2014 20:40:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Hardening-en-US-Modules/m-p/122466#M3753</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-04-07T20:40:09Z</dc:date>
    </item>
  </channel>
</rss>

