<?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 Blocking Malware Callbacks in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-malware-callbacks/m-p/68725#M40033</link>
    <description>&lt;P&gt;Malware Callbacks for command&amp;amp;control and also for data exfiltration are often transported in&lt;/P&gt;
&lt;P&gt;HTTP POSTs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The URL blocking of category malware URLs seems only to block the HTTP response. The GET or POST request seems to pass untouched to the server. So it is possible to exfiltrate arbitrary data in the GET or POST request.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What is the suggested strategie to block connection to hosts listed in the URL category malware before data can be exfiltrated?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 27 Nov 2015 10:23:13 GMT</pubDate>
    <dc:creator>Unibw</dc:creator>
    <dc:date>2015-11-27T10:23:13Z</dc:date>
    <item>
      <title>Blocking Malware Callbacks</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-malware-callbacks/m-p/68725#M40033</link>
      <description>&lt;P&gt;Malware Callbacks for command&amp;amp;control and also for data exfiltration are often transported in&lt;/P&gt;
&lt;P&gt;HTTP POSTs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The URL blocking of category malware URLs seems only to block the HTTP response. The GET or POST request seems to pass untouched to the server. So it is possible to exfiltrate arbitrary data in the GET or POST request.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What is the suggested strategie to block connection to hosts listed in the URL category malware before data can be exfiltrated?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Nov 2015 10:23:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-malware-callbacks/m-p/68725#M40033</guid>
      <dc:creator>Unibw</dc:creator>
      <dc:date>2015-11-27T10:23:13Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking Malware Callbacks</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-malware-callbacks/m-p/68747#M40042</link>
      <description>&lt;P&gt;You need to use DNS sinkhole feature.&lt;/P&gt;
&lt;P&gt;DNS sinkhole will give fake ip to malware dns requests and then infected pc's try to access this fake ip.&lt;/P&gt;
&lt;P&gt;You should use some ip that is not publicly and internally used.&lt;/P&gt;
&lt;P&gt;Or you can set up some box on it with wireshark to see exactly what data is sent to this fake ip.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Configure-DNS-Sinkhole/ta-p/58891" target="_self"&gt;https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Configure-DNS-Sinkhole/ta-p/58891&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1.1.1.1 as sinkhole is really bad idea because this is is really often used for demo purpouses or in software testing so more often than not you see traffic to 1.1.1.1 even without sinkhole so it is dificult to distinguish if it was really infected pc &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Make up your own ip and monitor traffic log.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Nov 2015 13:38:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-malware-callbacks/m-p/68747#M40042</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2015-11-27T13:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking Malware Callbacks</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-malware-callbacks/m-p/68758#M40050</link>
      <description>&lt;P&gt;Thank you! You are right suggesting sinkholing.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I already use DNS sinkhole for but not every URL in category malware seems to be covered with a DNS suspicious signature.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Only small parts regarding the logs in my environment. Therefore PANW claims a block in the log but a parallel installed IDS shows, that the callback was already transported.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there another modus which withholds the HTTP Request until the respose is there?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any idea why category malware is not completly covered by IDS signatures?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Nov 2015 20:04:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-malware-callbacks/m-p/68758#M40050</guid>
      <dc:creator>Unibw</dc:creator>
      <dc:date>2015-11-27T20:04:10Z</dc:date>
    </item>
  </channel>
</rss>

