<?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: Web API and encrypting login credentials in API / CLI Discussion</title>
    <link>https://community.checkpoint.com/t5/API-CLI-Discussion/Web-API-and-encrypting-login-credentials/m-p/77005#M4502</link>
    <description>&lt;P&gt;Hi Steve,&lt;/P&gt;
&lt;P&gt;As &lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/7"&gt;@PhoneBoy&lt;/a&gt;&amp;nbsp;has already said, using API Key for authentication is better than just username/password in terms of security.&lt;/P&gt;
&lt;P&gt;This authentication method complies with the industry standards due to:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;128-bit length make it a super challenging task to guess it&lt;/LI&gt;
&lt;LI&gt;randomly generated, so prevents from re-use between different environments&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;prevent the users' account being compromised if the user name is public&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;prevent a leaked key from identifying the user in any way&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Whatever method you choose, there are many tools existing on the market to keep a key or user credentials safely:&lt;/P&gt;
&lt;P&gt;open-source applications, dedicated hardware modules, cloud-based solutions.&lt;/P&gt;
&lt;P&gt;Examples: HashiCorp Vault,&amp;nbsp;Keywhiz,&amp;nbsp;AWS Secrets Manager.&lt;/P&gt;
&lt;P&gt;Of course, to integrate your API-based application with one of these tools, you'll be requested to provide a master password in some way.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 03 Mar 2020 16:08:19 GMT</pubDate>
    <dc:creator>Alex_Mitsevich</dc:creator>
    <dc:date>2020-03-03T16:08:19Z</dc:date>
    <item>
      <title>Web API and encrypting login credentials</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/Web-API-and-encrypting-login-credentials/m-p/76912#M4493</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Is there a way to secure the credentials used in the following API call:&lt;/P&gt;&lt;P&gt;curl --silent -X POST -H "Content-Type: application/json" -k -d @login.json &lt;A href="https://&amp;lt;fw" target="_blank"&gt;https://&amp;lt;fw_mgmt_srv&amp;gt;&lt;/A&gt;/web_api/login&lt;/P&gt;&lt;P&gt;The login.json is a clear text file. Anyone familiar with best practices on how to secure the file contents?&lt;/P&gt;&lt;P&gt;Much appreciated,&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;</description>
      <pubDate>Mon, 02 Mar 2020 22:04:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/Web-API-and-encrypting-login-credentials/m-p/76912#M4493</guid>
      <dc:creator>Steve_Bihari</dc:creator>
      <dc:date>2020-03-02T22:04:54Z</dc:date>
    </item>
    <item>
      <title>Re: Web API and encrypting login credentials</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/Web-API-and-encrypting-login-credentials/m-p/76920#M4494</link>
      <description>In R80.40, you can use API keys instead of credentials, which is slightly better but has the same fundamental issue: it needs to be stored either in plaintext or in a manner that can be easily reversed.&lt;BR /&gt;Not sure how folks are handling this.</description>
      <pubDate>Tue, 03 Mar 2020 01:48:48 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/Web-API-and-encrypting-login-credentials/m-p/76920#M4494</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-03-03T01:48:48Z</dc:date>
    </item>
    <item>
      <title>Re: Web API and encrypting login credentials</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/Web-API-and-encrypting-login-credentials/m-p/77005#M4502</link>
      <description>&lt;P&gt;Hi Steve,&lt;/P&gt;
&lt;P&gt;As &lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/7"&gt;@PhoneBoy&lt;/a&gt;&amp;nbsp;has already said, using API Key for authentication is better than just username/password in terms of security.&lt;/P&gt;
&lt;P&gt;This authentication method complies with the industry standards due to:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;128-bit length make it a super challenging task to guess it&lt;/LI&gt;
&lt;LI&gt;randomly generated, so prevents from re-use between different environments&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;prevent the users' account being compromised if the user name is public&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;prevent a leaked key from identifying the user in any way&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Whatever method you choose, there are many tools existing on the market to keep a key or user credentials safely:&lt;/P&gt;
&lt;P&gt;open-source applications, dedicated hardware modules, cloud-based solutions.&lt;/P&gt;
&lt;P&gt;Examples: HashiCorp Vault,&amp;nbsp;Keywhiz,&amp;nbsp;AWS Secrets Manager.&lt;/P&gt;
&lt;P&gt;Of course, to integrate your API-based application with one of these tools, you'll be requested to provide a master password in some way.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2020 16:08:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/Web-API-and-encrypting-login-credentials/m-p/77005#M4502</guid>
      <dc:creator>Alex_Mitsevich</dc:creator>
      <dc:date>2020-03-03T16:08:19Z</dc:date>
    </item>
  </channel>
</rss>

