<?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: Splunk Configuration of Password encryption and Complexity in Security</title>
    <link>https://community.splunk.com/t5/Security/Splunk-Configuration-of-Password-encryption-and-Complexity/m-p/130685#M3942</link>
    <description>&lt;P&gt;There's a setting in &lt;CODE&gt;authentication.conf&lt;/CODE&gt;: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.2/Admin/Authenticationconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.1.2/Admin/Authenticationconf&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;passwordHashAlgorithm = [SHA512-crypt|SHA256-crypt|SHA512-crypt-&amp;lt;num_rounds&amp;gt;|SHA256-crypt-&amp;lt;num_rounds&amp;gt;|MD5-crypt]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I believe the password requirements with built-in authentication is limited to requiring a certain length (same .conf):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;minPasswordLength = &amp;lt;positive integer&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;For more sophisticated complexity requirements you should use external authentication, such as Active Directory.&lt;/P&gt;</description>
    <pubDate>Thu, 03 Jul 2014 20:09:12 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2014-07-03T20:09:12Z</dc:date>
    <item>
      <title>Splunk Configuration of Password encryption and Complexity</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Configuration-of-Password-encryption-and-Complexity/m-p/130684#M3941</link>
      <description>&lt;P&gt;I am trying to determine how SPLUNK passwords are stored using one way encryption. I am also trying to determine if I can change the SPLUNK complexity passwords requirements for users.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jul 2014 18:42:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Configuration-of-Password-encryption-and-Complexity/m-p/130684#M3941</guid>
      <dc:creator>rogerroger</dc:creator>
      <dc:date>2014-07-03T18:42:54Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Configuration of Password encryption and Complexity</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Configuration-of-Password-encryption-and-Complexity/m-p/130685#M3942</link>
      <description>&lt;P&gt;There's a setting in &lt;CODE&gt;authentication.conf&lt;/CODE&gt;: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.2/Admin/Authenticationconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.1.2/Admin/Authenticationconf&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;passwordHashAlgorithm = [SHA512-crypt|SHA256-crypt|SHA512-crypt-&amp;lt;num_rounds&amp;gt;|SHA256-crypt-&amp;lt;num_rounds&amp;gt;|MD5-crypt]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I believe the password requirements with built-in authentication is limited to requiring a certain length (same .conf):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;minPasswordLength = &amp;lt;positive integer&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;For more sophisticated complexity requirements you should use external authentication, such as Active Directory.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jul 2014 20:09:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Configuration-of-Password-encryption-and-Complexity/m-p/130685#M3942</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-07-03T20:09:12Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Configuration of Password encryption and Complexity</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Configuration-of-Password-encryption-and-Complexity/m-p/130686#M3943</link>
      <description>&lt;P&gt;Best thing you can do there is SHA256-crypt-1000000 . This makes it almost impossible to guess passwords unless you have "Welcome-2016". &lt;/P&gt;

&lt;P&gt;In our case we did not have the slow downs mentioned in the doc.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Nov 2016 11:28:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Configuration-of-Password-encryption-and-Complexity/m-p/130686#M3943</guid>
      <dc:creator>msmith4</dc:creator>
      <dc:date>2016-11-01T11:28:54Z</dc:date>
    </item>
  </channel>
</rss>

