<?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: Encrypting Data in Qlik replicate in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Encrypting-Data-in-Qlik-replicate/m-p/2452937#M11094</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/243606"&gt;@gayatri235&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Both Oracle and SQL Server supports column level encryption, however it only can be decrypted within the source database as you need an encryption key to do the job but the key won't be able to work elsewhere and also the encryption algorithm would be different in different DB system.&lt;/P&gt;
&lt;P&gt;Replicate doesn't have an internal encryption mechanism. As &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/125525"&gt;@DesmondWOO&lt;/a&gt;&amp;nbsp;recommended, you can use the hash function which will convert the column to random characters. However please be noted that this is a 'one way encryption' which can't be decrypted afterwards.&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Kent&lt;/P&gt;</description>
    <pubDate>Wed, 15 May 2024 23:49:37 GMT</pubDate>
    <dc:creator>Kent_Feng</dc:creator>
    <dc:date>2024-05-15T23:49:37Z</dc:date>
    <item>
      <title>Encrypting Data in Qlik replicate</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Encrypting-Data-in-Qlik-replicate/m-p/2451345#M11043</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We need to encrypt PII columns from the source and also need to decrypt them if needed.&lt;/P&gt;
&lt;P&gt;Any ideas how can we do it&amp;nbsp; .&lt;/P&gt;
&lt;P&gt;Sources : Oracle, SQL Server&lt;/P&gt;
&lt;P&gt;Target: Postgresql&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Gayatri,&lt;/P&gt;</description>
      <pubDate>Sat, 11 May 2024 15:46:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Encrypting-Data-in-Qlik-replicate/m-p/2451345#M11043</guid>
      <dc:creator>gayatri235</dc:creator>
      <dc:date>2024-05-11T15:46:15Z</dc:date>
    </item>
    <item>
      <title>Re: Encrypting Data in Qlik replicate</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Encrypting-Data-in-Qlik-replicate/m-p/2451562#M11051</link>
      <description>&lt;P&gt;Had a think about it.&amp;nbsp; I'm not sure if there is a common column encryption method between the source(s) and destination (after a few minutes of casual googling) that you can encrypt the PII data on the source and use the key at destination to decrypt it.&lt;/P&gt;
&lt;P&gt;Can you lock down your sources and destinations to particular users?&amp;nbsp; Encryption of data in transit should be handled by the ODBC driver and if you encrypt/lockdown the data directory of qlik replicate; that should take care of the data at rest if the changes get backed up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 May 2024 05:10:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Encrypting-Data-in-Qlik-replicate/m-p/2451562#M11051</guid>
      <dc:creator>Jon_Donker</dc:creator>
      <dc:date>2024-05-13T05:10:22Z</dc:date>
    </item>
    <item>
      <title>Re: Encrypting Data in Qlik replicate</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Encrypting-Data-in-Qlik-replicate/m-p/2451670#M11061</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/243606"&gt;@gayatri235&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;Please check whether&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/replicate/May2021/Content/Global_Common/Content/SharedEMReplicate/Customize%20Tasks/tasks_expressOther.htm?&amp;amp;_ga=2.103444937.875142562.1715563420-362829277.1698887377#Hash" target="_blank" rel="noopener"&gt;HASH function&lt;/A&gt; addresses your requirements.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Desmond&lt;/P&gt;</description>
      <pubDate>Mon, 13 May 2024 10:14:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Encrypting-Data-in-Qlik-replicate/m-p/2451670#M11061</guid>
      <dc:creator>DesmondWOO</dc:creator>
      <dc:date>2024-05-13T10:14:50Z</dc:date>
    </item>
    <item>
      <title>Re: Encrypting Data in Qlik replicate</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Encrypting-Data-in-Qlik-replicate/m-p/2452937#M11094</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/243606"&gt;@gayatri235&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Both Oracle and SQL Server supports column level encryption, however it only can be decrypted within the source database as you need an encryption key to do the job but the key won't be able to work elsewhere and also the encryption algorithm would be different in different DB system.&lt;/P&gt;
&lt;P&gt;Replicate doesn't have an internal encryption mechanism. As &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/125525"&gt;@DesmondWOO&lt;/a&gt;&amp;nbsp;recommended, you can use the hash function which will convert the column to random characters. However please be noted that this is a 'one way encryption' which can't be decrypted afterwards.&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Kent&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2024 23:49:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Encrypting-Data-in-Qlik-replicate/m-p/2452937#M11094</guid>
      <dc:creator>Kent_Feng</dc:creator>
      <dc:date>2024-05-15T23:49:37Z</dc:date>
    </item>
  </channel>
</rss>

