<?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: WannaCry - Kill Switch &amp;amp; DNS sinkholing in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156664#M51441</link>
    <description>&lt;P&gt;The kill switch works when the malware is able to reach out to the killswitch domain. &amp;nbsp;If you block/sinkhole/prevent access to that, then the malware will do its thing and encrypt/ransom your data. &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 15 May 2017 14:50:13 GMT</pubDate>
    <dc:creator>jvalentine</dc:creator>
    <dc:date>2017-05-15T14:50:13Z</dc:date>
    <item>
      <title>WannaCry - Kill Switch &amp; DNS sinkholing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156655#M51438</link>
      <description>&lt;P&gt;Why Palo is not sinkholing DNS queries to the kill switch URLs? Currently if I run a DNS lookup request for the kill switch URL, it come back with the valid DNS response. shouldn't this be sinkholed?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When the guy "accidentally" found the kill switch, I thought, Palo would be able to do this as well. But alas, it didn't and still hasn't yet, I guess there must be an reason behind this, anyone knows why?&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2017 14:33:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156655#M51438</guid>
      <dc:creator>Fengrui</dc:creator>
      <dc:date>2017-05-15T14:33:31Z</dc:date>
    </item>
    <item>
      <title>Re: WannaCry - Kill Switch &amp; DNS sinkholing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156660#M51439</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/38202"&gt;@Fengrui&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Palo Alto Networks customers are protected from WanaCrypt0r ransomware through multiple complementary prevention controls across our Next-Generation Security Platform. &amp;nbsp;Please refer to the following post for more details :&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="http://researchcenter.paloaltonetworks.com/2017/05/palo-alto-networks-protections-wanacrypt0r-attacks/" target="_blank"&gt;http://researchcenter.paloaltonetworks.com/2017/05/palo-alto-networks-protections-wanacrypt0r-attacks/&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Cheers !&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;-Kiwi&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2017 14:42:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156660#M51439</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2017-05-15T14:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: WannaCry - Kill Switch &amp; DNS sinkholing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156664#M51441</link>
      <description>&lt;P&gt;The kill switch works when the malware is able to reach out to the killswitch domain. &amp;nbsp;If you block/sinkhole/prevent access to that, then the malware will do its thing and encrypt/ransom your data. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2017 14:50:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156664#M51441</guid>
      <dc:creator>jvalentine</dc:creator>
      <dc:date>2017-05-15T14:50:13Z</dc:date>
    </item>
    <item>
      <title>Re: WannaCry - Kill Switch &amp; DNS sinkholing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156665#M51442</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/22017"&gt;@jvalentine&lt;/a&gt;, I think if you sinkhole the the killswitch domain, then the malware will exit and do nothing? As it thinks being analysed in a sandbox environment? That's my understanding how the killswitch worked. You can't block it though.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/11943"&gt;@kiwi&lt;/a&gt;, for DNS sinkhole to work, the domain/URL have to be regarded malicious by palo to start with, and it seems this is not the case yet, we have DNS sinkhole configured in our environment, I'd expect the DNS query internally to the killswitch domain would come back with the sinkhole bogus IP, however it didn't. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2017 14:59:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156665#M51442</guid>
      <dc:creator>Fengrui</dc:creator>
      <dc:date>2017-05-15T14:59:53Z</dc:date>
    </item>
    <item>
      <title>Re: WannaCry - Kill Switch &amp; DNS sinkholing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156668#M51443</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/38202"&gt;@Fengrui&lt;/a&gt;&amp;nbsp;according to this article, if the killswitch domain is&amp;nbsp;accessible, the malware will halt. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;-&amp;nbsp;&lt;A href="https://www.theguardian.com/technology/2017/may/13/accidental-hero-finds-kill-switch-to-stop-spread-of-ransomware-cyber-attack" target="_blank"&gt;https://www.theguardian.com/technology/2017/may/13/accidental-hero-finds-kill-switch-to-stop-spread-of-ransomware-cyber-attack&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2017 15:13:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156668#M51443</guid>
      <dc:creator>jvalentine</dc:creator>
      <dc:date>2017-05-15T15:13:28Z</dc:date>
    </item>
    <item>
      <title>Re: WannaCry - Kill Switch &amp; DNS sinkholing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156669#M51444</link>
      <description>&lt;P&gt;cool, this is great, thanks&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/22017"&gt;@jvalentine&lt;/a&gt;, this explains why Palo is not sinkholing the DNS request.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/11943"&gt;@kiwi&lt;/a&gt;, the article you mentioned probably needs updating, DNS sinkholing in itself is very useful and effective, however in this specific case, looks like it's not being used.&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2017 15:18:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/wannacry-kill-switch-amp-dns-sinkholing/m-p/156669#M51444</guid>
      <dc:creator>Fengrui</dc:creator>
      <dc:date>2017-05-15T15:18:28Z</dc:date>
    </item>
  </channel>
</rss>

