<?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: Can extensions carry security risk? in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Can-extensions-carry-security-risk/m-p/1061864#M4548</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So as a rule of thumb extensions poses as much security risk as browsing to Facebook.com, Google.com or any random web page on the web.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Extensions are client side technology, meaning it will execute within the sandbox that is the users browser, so it can't access anything on the server or outside the normal resources a browser can access on the local machine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The potential risk you are running is that a extension could intercept the data from a app and then pipe that to a third party server somewhere. So I would scan for any outgoing connections such as xmlhttprequest, websockets etc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Qlik cookies available to steal won't reveal anything special to the attacker apart from a session id which you can lock down with extended security in your virtual proxy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Feb 2016 19:17:35 GMT</pubDate>
    <dc:creator>Alexander_Thor</dc:creator>
    <dc:date>2016-02-11T19:17:35Z</dc:date>
    <item>
      <title>Can extensions carry security risk?</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Can-extensions-carry-security-risk/m-p/1061862#M4546</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found a couple of open source extension.But before installing them on the Qliksense server ,I want to make sure it does not contain any trojan program that could pose a security risk.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any tips on how to look for malicious code in extensions?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Feb 2016 18:50:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Can-extensions-carry-security-risk/m-p/1061862#M4546</guid>
      <dc:creator>swarup_malli</dc:creator>
      <dc:date>2016-02-05T18:50:37Z</dc:date>
    </item>
    <item>
      <title>Re: Can extensions carry security risk?</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Can-extensions-carry-security-risk/m-p/1061863#M4547</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Make sure you are downloading from a trusted sites and the websites from Qlik Partners&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also you can refer Stephan Walther's website&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.qlikblog.at/" title="http://www.qlikblog.at/"&gt;qlikblog.at | QlikView / Qlik Sense Blog by Stefan Walther&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Feb 2016 19:06:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Can-extensions-carry-security-risk/m-p/1061863#M4547</guid>
      <dc:creator>satishkurra</dc:creator>
      <dc:date>2016-02-11T19:06:31Z</dc:date>
    </item>
    <item>
      <title>Re: Can extensions carry security risk?</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Can-extensions-carry-security-risk/m-p/1061864#M4548</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So as a rule of thumb extensions poses as much security risk as browsing to Facebook.com, Google.com or any random web page on the web.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Extensions are client side technology, meaning it will execute within the sandbox that is the users browser, so it can't access anything on the server or outside the normal resources a browser can access on the local machine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The potential risk you are running is that a extension could intercept the data from a app and then pipe that to a third party server somewhere. So I would scan for any outgoing connections such as xmlhttprequest, websockets etc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Qlik cookies available to steal won't reveal anything special to the attacker apart from a session id which you can lock down with extended security in your virtual proxy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Feb 2016 19:17:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Can-extensions-carry-security-risk/m-p/1061864#M4548</guid>
      <dc:creator>Alexander_Thor</dc:creator>
      <dc:date>2016-02-11T19:17:35Z</dc:date>
    </item>
    <item>
      <title>Re: Can extensions carry security risk?</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Can-extensions-carry-security-risk/m-p/1061865#M4549</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you guys! sorry for the late reply &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Feb 2016 14:16:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Can-extensions-carry-security-risk/m-p/1061865#M4549</guid>
      <dc:creator>swarup_malli</dc:creator>
      <dc:date>2016-02-16T14:16:20Z</dc:date>
    </item>
  </channel>
</rss>

