<?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>idea Re: Security enhancement request to QEM - Access to source and target in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1740616#M3370</link>
    <description>&lt;P&gt;Another Big Vote !!!&lt;/P&gt;&lt;P&gt;Working in a Banking environment, the are some system replicating Credit Card Numbers, and this cause a serious risk for the bank.&lt;/P&gt;&lt;P&gt;I really cannot wait for this enhancement to be build..&lt;/P&gt;&lt;P&gt;Please Please Please!!!!!!!&lt;/P&gt;</description>
    <pubDate>Wed, 02 Sep 2020 12:17:55 GMT</pubDate>
    <dc:creator>JCJnr</dc:creator>
    <dc:date>2020-09-02T12:17:55Z</dc:date>
    <item>
      <title>Security enhancement request to QEM - Access to source and target</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idi-p/1717986</link>
      <description>&lt;P&gt;In the current version of QEM, anyone that can login to QEM have the ability to access source and target created by other people.&amp;nbsp; Example: user1 can create a new task in QEM using source and target created previously by user2.&amp;nbsp; This create a security issue since outside of the QEM application the user1 doesn't have access to source and target that user2 have access.&amp;nbsp; It would be ideal to have source and target permission similiar to task permission.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2020 15:10:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idi-p/1717986</guid>
      <dc:creator>l9phan1</dc:creator>
      <dc:date>2020-06-11T15:10:28Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1720407#M2557</link>
      <description>&lt;P&gt;I agree that QEM and the Replicate UI should be able to assign access controls at the individual Endpoint level as can be done for an individual task.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jun 2020 15:20:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1720407#M2557</guid>
      <dc:creator>BradA</dc:creator>
      <dc:date>2020-06-19T15:20:51Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target - Status changed to: Open - Collecting Feedback</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1721781#M2591</link>
      <description>&lt;P&gt;Thank you for your feedback, we are currently collecting additional feedback.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jun 2020 14:30:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1721781#M2591</guid>
      <dc:creator>Ola_Mayer</dc:creator>
      <dc:date>2020-06-24T14:30:12Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1725816#M2784</link>
      <description>&lt;P&gt;This feature is very important to us from a data privacy perspective.&lt;/P&gt;&lt;P&gt;My team works in a governance and compliance role and we use Attunity to move data for several highly sensitive data sources. We discussed the lack of controls at the endpoint and task level with our compliance counsel and it's considered to be a data privacy compliance risk. Our current workaround is to use separate servers for different content, but that's not really scalable for a global organization.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Having this feature is key for us to use the product in a scalable, cost-effective manner.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jul 2020 16:49:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1725816#M2784</guid>
      <dc:creator>Matthew_Christian</dc:creator>
      <dc:date>2020-07-07T16:49:09Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1726853#M2837</link>
      <description>&lt;P&gt;The ability to control access to endpoints is an important topic in my organization as well. We have an analytics group that is separate from IT.&amp;nbsp;Our IT group needs to maintain security on the source systems and ensure compliance with our security policies. &amp;nbsp;It would be ideal to have a granular way to control endpoint access within Replicate itself, and QEM.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jul 2020 14:26:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1726853#M2837</guid>
      <dc:creator>JonCarpenter</dc:creator>
      <dc:date>2020-07-10T14:26:06Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1726895#M2841</link>
      <description>I am glad to see you have the same concern.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Jul 2020 15:36:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1726895#M2841</guid>
      <dc:creator>l9phan1</dc:creator>
      <dc:date>2020-07-10T15:36:07Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1727421#M2872</link>
      <description>&lt;P&gt;Big Up Vote!!!&lt;/P&gt;&lt;P&gt;This SER is spot on by detailing a glaring hole in the QEM/Replicate security model. It is not sufficient to hide a task from prying eyes. The products should also protect the source and target endpoints to ensure that NO unauthorized access or manipulation of data can occur.&lt;/P&gt;&lt;P&gt;Currently anyone with developer access to Replicate can create a task, assign any source endpoint they choose and replicate data. Once replication is complete they delete the task and nobody is the wiser. Sure the activity is recorded in logs, but these are not easily digestible and there are no reports that can easily be run to see who created/executed tasks with&amp;nbsp;which endpoints during a period of time.&lt;/P&gt;&lt;P&gt;This gap in security is forcing my corporation to stand up "secure" replicate servers with tight access permissions to prevent the potential unauthorized access or manipulation of data. This is an unnecessary cost and administrative burden that can be eliminated by &lt;U&gt;simply&lt;/U&gt; applying the same security model to endpoints that is currently in place for tasks.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2020 16:43:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1727421#M2872</guid>
      <dc:creator>paullewis</dc:creator>
      <dc:date>2020-07-13T16:43:40Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1740616#M3370</link>
      <description>&lt;P&gt;Another Big Vote !!!&lt;/P&gt;&lt;P&gt;Working in a Banking environment, the are some system replicating Credit Card Numbers, and this cause a serious risk for the bank.&lt;/P&gt;&lt;P&gt;I really cannot wait for this enhancement to be build..&lt;/P&gt;&lt;P&gt;Please Please Please!!!!!!!&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2020 12:17:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1740616#M3370</guid>
      <dc:creator>JCJnr</dc:creator>
      <dc:date>2020-09-02T12:17:55Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1799843#M5861</link>
      <description>&lt;P&gt;Any updates on this new feature, it's becoming a key item for us to enable replication of sensitive data without having to stand up new instances of Qlik Replicate.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 18:07:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1799843#M5861</guid>
      <dc:creator>sidneyb</dc:creator>
      <dc:date>2021-04-15T18:07:09Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target - Status changed to: Open - On Roadmap</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1824196#M6839</link>
      <description>&lt;P&gt;Thank you for all of the good input.&amp;nbsp; This is in the Replicate roadmap and will update when development is underway.&amp;nbsp; Thank you!&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jul 2021 18:14:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1824196#M6839</guid>
      <dc:creator>Shelley_Brennan</dc:creator>
      <dc:date>2021-07-23T18:14:01Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1900398#M8846</link>
      <description>&lt;P&gt;Security is very critical. I had opened a support case after seeing the highlighted message from QEM window. This feature is key as is the task permissions. No user should be able to make changes on other user's endpoints. It's like the concept of least privilege. You wanna give users the least access so that they can only manage what is theirs only.&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Endpoint Level Permissions.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/73482i5022D11EA1CD90BF/image-size/large?v=v2&amp;amp;px=999" role="button" title="Endpoint Level Permissions.png" alt="Endpoint Level Permissions.png" /&gt;&lt;/span&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Mar 2022 07:59:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1900398#M8846</guid>
      <dc:creator>andile</dc:creator>
      <dc:date>2022-03-03T07:59:49Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1978644#M10310</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Strongly agree..&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Working in a company that has several divisions, where each should not have access to other division's endpoints so as to avoid mistakes or intentionally taking data from other divisions.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Aims&amp;nbsp;mistake or intentionally take data from other divisions.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Really appreciate if this feature is already on the roadmap and can be delivered soon.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2022 11:41:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/1978644#M10310</guid>
      <dc:creator>Herra</dc:creator>
      <dc:date>2022-09-08T11:41:51Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/2051712#M12240</link>
      <description>&lt;P&gt;Thank you for your continued feedback and patience while we deliver new features and enhancements to Replicate product.&lt;/P&gt;
&lt;P&gt;This feature is very important to us, and it is high priority item on Replicate short-term roadmap.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2023 16:57:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/2051712#M12240</guid>
      <dc:creator>marina_marshak</dc:creator>
      <dc:date>2023-03-21T16:57:57Z</dc:date>
    </item>
    <item>
      <title>From now on, please track this idea from the Ideation por...</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/2101395#M14636</link>
      <description>&lt;P&gt;From now on, please track this idea from the Ideation portal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;A title="Link to new idea" href="https://ideation.qlik.com/app/#/case/279041" target="_blank" rel="noopener"&gt;Link to new idea&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Meghann&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;EM&gt;NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you &lt;STRONG&gt;only&lt;/STRONG&gt; see 1 tab with the login page, please try clicking this link first: &lt;STRONG&gt;&lt;A title="Authenticate me!" href="#" target="_blank" rel="noopener"&gt;Authenticate me!&lt;/A&gt;&lt;/STRONG&gt;&amp;nbsp;t&lt;/EM&gt;&lt;EM&gt;hen try the link above again. Ensure pop-up blocker is off.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Aug 2023 16:26:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/2101395#M14636</guid>
      <dc:creator>Meghann_MacDonald</dc:creator>
      <dc:date>2023-08-02T16:26:11Z</dc:date>
    </item>
    <item>
      <title>Re: Security enhancement request to QEM - Access to source and target - Status changed to: Closed - Archived</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/2101396#M14637</link>
      <description />
      <pubDate>Wed, 02 Aug 2023 16:26:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Security-enhancement-request-to-QEM-Access-to-source-and-target/idc-p/2101396#M14637</guid>
      <dc:creator>Ideation</dc:creator>
      <dc:date>2023-08-02T16:26:13Z</dc:date>
    </item>
  </channel>
</rss>

