<?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: Anyway to block Webex plugin? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/anyway-to-block-webex-plugin/m-p/139412#M48111</link>
    <description>&lt;P&gt;There is a webex app signature that you can block, this would block not only the extension but the actual client wouldn't be able to connect either. If you manage your Chrome plugins across the organization you can always remove it until it's fixed as well.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 25 Jan 2017 20:02:06 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2017-01-25T20:02:06Z</dc:date>
    <item>
      <title>Anyway to block Webex plugin?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/anyway-to-block-webex-plugin/m-p/139141#M48074</link>
      <description>&lt;P&gt;After hearing the news that the Webex extension in Chrome has a serious vulnerability is it possible to block this at the Palo Alto?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="http://arstechnica.com/security/2017/01/ciscos-webex-chrome-plugin-opens-20-million-users-to-drive-by-attacks/?comments=1" target="_blank"&gt;http://arstechnica.com/security/2017/01/ciscos-webex-chrome-plugin-opens-20-million-users-to-drive-by-attacks/?comments=1&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Either through an App policy or even better a threat signature?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jan 2017 18:44:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/anyway-to-block-webex-plugin/m-p/139141#M48074</guid>
      <dc:creator>pmc</dc:creator>
      <dc:date>2017-01-24T18:44:28Z</dc:date>
    </item>
    <item>
      <title>Re: Anyway to block Webex plugin?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/anyway-to-block-webex-plugin/m-p/139412#M48111</link>
      <description>&lt;P&gt;There is a webex app signature that you can block, this would block not only the extension but the actual client wouldn't be able to connect either. If you manage your Chrome plugins across the organization you can always remove it until it's fixed as well.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2017 20:02:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/anyway-to-block-webex-plugin/m-p/139412#M48111</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2017-01-25T20:02:06Z</dc:date>
    </item>
    <item>
      <title>Re: Anyway to block Webex plugin?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/anyway-to-block-webex-plugin/m-p/139454#M48117</link>
      <description>&lt;P&gt;I checked with support on this one:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have created signature coverage for Cisco Webex Chrome Plugin vulnerability.&lt;BR /&gt;&lt;BR /&gt;We are currently awaiting content release.&lt;BR /&gt;&lt;BR /&gt;We will contact you with content version, and release date. Once the signature has been released.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2017 23:19:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/anyway-to-block-webex-plugin/m-p/139454#M48117</guid>
      <dc:creator>pmc</dc:creator>
      <dc:date>2017-01-25T23:19:11Z</dc:date>
    </item>
    <item>
      <title>Re: Anyway to block Webex plugin?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/anyway-to-block-webex-plugin/m-p/139632#M48153</link>
      <description>&lt;P&gt;Application and Threat content version 656 contains the signature for this vulnerability. &amp;nbsp;I would have preffered to see this out yesterday but at least its here now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="WebEx.jpg" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/7431i3A7DDC4545C866DD/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="WebEx.jpg" alt="WebEx.jpg" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2017 19:22:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/anyway-to-block-webex-plugin/m-p/139632#M48153</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2017-01-26T19:22:53Z</dc:date>
    </item>
    <item>
      <title>Re: Anyway to block Webex plugin?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/anyway-to-block-webex-plugin/m-p/139634#M48154</link>
      <description>&lt;P&gt;I wouldn't really want anyone to rush out a signature as it just means that it wouldn't have been as tested for false positives.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2017 20:48:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/anyway-to-block-webex-plugin/m-p/139634#M48154</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2017-01-26T20:48:24Z</dc:date>
    </item>
  </channel>
</rss>

