<?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: best practice to protect Database connection password in Member Support</title>
    <link>https://community.isc2.org/t5/Member-Support/best-practice-to-protect-Database-connection-password/m-p/1426#M132</link>
    <description>yes, indeed. two situation here, one is developing by Java, one is developing by php or some other scripting language. the same function is they all need to connect to database to update data. the encryption principle is separating key and cipher text. for java, there is a way to secure DB password as below: 1. generate a root key and a instance key 2. encrypt DB password by instance key and store it in config file 3. encrypt instance key by root key and store it in config file 4. keep root key in other server and get them when require after authenticated please let me know your advice, thx.</description>
    <pubDate>Thu, 19 Oct 2017 01:56:45 GMT</pubDate>
    <dc:creator>AmyZ</dc:creator>
    <dc:date>2017-10-19T01:56:45Z</dc:date>
    <item>
      <title>best practice to protect Database connection password</title>
      <link>https://community.isc2.org/t5/Member-Support/best-practice-to-protect-Database-connection-password/m-p/1395#M126</link>
      <description>Storing DB connection password in plain text in config file is very common way， but we know it's not secure. what's the best practices to protect DB password? thanks.</description>
      <pubDate>Wed, 18 Oct 2017 09:29:23 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Member-Support/best-practice-to-protect-Database-connection-password/m-p/1395#M126</guid>
      <dc:creator>AmyZ</dc:creator>
      <dc:date>2017-10-18T09:29:23Z</dc:date>
    </item>
    <item>
      <title>Re: best practice to protect Database connection password</title>
      <link>https://community.isc2.org/t5/Member-Support/best-practice-to-protect-Database-connection-password/m-p/1399#M127</link>
      <description>Hi, The technique will vary based on language and environment that you are deploying. Perhaps you can provide further information on this?</description>
      <pubDate>Wed, 18 Oct 2017 13:44:18 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Member-Support/best-practice-to-protect-Database-connection-password/m-p/1399#M127</guid>
      <dc:creator>sureshdr</dc:creator>
      <dc:date>2017-10-18T13:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: best practice to protect Database connection password</title>
      <link>https://community.isc2.org/t5/Member-Support/best-practice-to-protect-Database-connection-password/m-p/1426#M132</link>
      <description>yes, indeed. two situation here, one is developing by Java, one is developing by php or some other scripting language. the same function is they all need to connect to database to update data. the encryption principle is separating key and cipher text. for java, there is a way to secure DB password as below: 1. generate a root key and a instance key 2. encrypt DB password by instance key and store it in config file 3. encrypt instance key by root key and store it in config file 4. keep root key in other server and get them when require after authenticated please let me know your advice, thx.</description>
      <pubDate>Thu, 19 Oct 2017 01:56:45 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Member-Support/best-practice-to-protect-Database-connection-password/m-p/1426#M132</guid>
      <dc:creator>AmyZ</dc:creator>
      <dc:date>2017-10-19T01:56:45Z</dc:date>
    </item>
  </channel>
</rss>

