<?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: Replacing Splunk admin account with a non standard admin account in Security</title>
    <link>https://community.splunk.com/t5/Security/Replacing-Splunk-admin-account-with-a-non-standard-admin-account/m-p/29024#M13736</link>
    <description>&lt;P&gt;It is possible clone the admin user to a new "admin"account (eg splunkadm)with identical privileges. Once the new account is created you may delete the original admin account. &lt;/P&gt;

&lt;P&gt;CAVEAT&lt;BR /&gt;
If the "default" admin has created knowledge objects you will need to move these knowledge objects associated with the "default" admin to the "new" admin account.&lt;/P&gt;

&lt;P&gt;It is advisable to test this in a Pre Production Test Enviroment to ensure that no fuctionality is lost&lt;/P&gt;

&lt;P&gt;For futher suggestions on "hardening" the Splunk enviroment please see&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/Security/Hardeningstandards"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/Security/Hardeningstandards&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Nov 2012 16:33:22 GMT</pubDate>
    <dc:creator>dshakespeare_sp</dc:creator>
    <dc:date>2012-11-09T16:33:22Z</dc:date>
    <item>
      <title>Replacing Splunk admin account with a non standard admin account</title>
      <link>https://community.splunk.com/t5/Security/Replacing-Splunk-admin-account-with-a-non-standard-admin-account/m-p/29023#M13735</link>
      <description>&lt;P&gt;A security conscious company has a policy of removing "default" admin accounts from its software products and replacing then with a non standard admin accounts. Is the possible in Splunk?&lt;/P&gt;</description>
      <pubDate>Fri, 09 Nov 2012 16:23:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Replacing-Splunk-admin-account-with-a-non-standard-admin-account/m-p/29023#M13735</guid>
      <dc:creator>dshakespeare_sp</dc:creator>
      <dc:date>2012-11-09T16:23:10Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing Splunk admin account with a non standard admin account</title>
      <link>https://community.splunk.com/t5/Security/Replacing-Splunk-admin-account-with-a-non-standard-admin-account/m-p/29024#M13736</link>
      <description>&lt;P&gt;It is possible clone the admin user to a new "admin"account (eg splunkadm)with identical privileges. Once the new account is created you may delete the original admin account. &lt;/P&gt;

&lt;P&gt;CAVEAT&lt;BR /&gt;
If the "default" admin has created knowledge objects you will need to move these knowledge objects associated with the "default" admin to the "new" admin account.&lt;/P&gt;

&lt;P&gt;It is advisable to test this in a Pre Production Test Enviroment to ensure that no fuctionality is lost&lt;/P&gt;

&lt;P&gt;For futher suggestions on "hardening" the Splunk enviroment please see&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/Security/Hardeningstandards"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/Security/Hardeningstandards&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Nov 2012 16:33:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Replacing-Splunk-admin-account-with-a-non-standard-admin-account/m-p/29024#M13736</guid>
      <dc:creator>dshakespeare_sp</dc:creator>
      <dc:date>2012-11-09T16:33:22Z</dc:date>
    </item>
  </channel>
</rss>

