<?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: PA Bypass Question - McAfee Evader in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/pa-bypass-question-mcafee-evader/m-p/69166#M40187</link>
    <description>&lt;P&gt;Fast response from PA supprt:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;On November 30th, a video was posted by the owner of the NetSecVulns YouTube channel titled "666 different ways to bypass palo alto networks in 6 minutes”.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;In the first video, posted Nov 30th, NetSecVulns sets up a lab with a Windows XP SP2 victim and the Stonesoft Evader tool configured to use the Conficker attack and a Palo Alto Networks Next-Generation Firewall in Layer 3 mode placed in between 2 endpoints. Great pains are made to show that our firewall is configured using our Best Practices configuration document. Once the Evader tool completes its run, the administrator shows that our firewall missed 666 evasion attempts.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;In reality, NetSecVulns skipped step 4 in our Best Practices document: creation of an unknown application block rule. This can be verified in the video (at 2:20) where we see a single allow rule instead of the expected 2 rules with the first one dropping unknown applications. Later in the video, at 4:31 and 5:49, it shows the "threat logs”, carefully avoiding "traffic logs" where we would have seen unknown-tcp sessions allowed through.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;After running this test in our own lab on PAN-OS 7.0.3, and correctly following the same Best Practices document, we verified that we block&amp;nbsp;&lt;STRONG&gt;&lt;U&gt;100%&lt;/U&gt;&lt;/STRONG&gt;&amp;nbsp;of the 204,090 evasion attempts. Also note that this test is performed by our internal QA team for each PAN-OS major and minor feature release.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;On Dec 3&lt;SUP&gt;rd&lt;/SUP&gt;, NetSecVulns posted a new video, correcting the "step 4" error. However once again they did not follow all steps in the Best Practices document, rendering the test inaccurate and misleading.&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 08 Dec 2015 14:21:59 GMT</pubDate>
    <dc:creator>Demast</dc:creator>
    <dc:date>2015-12-08T14:21:59Z</dc:date>
    <item>
      <title>PA Bypass Question - McAfee Evader</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-bypass-question-mcafee-evader/m-p/69159#M40184</link>
      <description>&lt;P&gt;Does anyone have any information on the latest posted PA bypass?&amp;nbsp; The youtube video shows some of the FW features&amp;nbsp; being bypassed using McAfee Evader.&amp;nbsp; It appears to require an IP of the firewall to execute - the example also shows most of the evasions relating to protocols not likely to be exposed over the firewall (NetBIOS, RPC, SMB) so I'm not sure how broadly this applies or how bad it is.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;666 different ways to bypass palo alto networks in 6 minutes&lt;/P&gt;
&lt;P&gt;Published on Nov 30, 2015&lt;BR /&gt;full log file can be found &lt;A class="js-link post-link" href="http://www.linkedin.com/redir/redirect?url=http%3A%2F%2Fgoo%2Egl%2FWR3VkJ&amp;amp;urlhash=8jhp&amp;amp;_t=tracking_anet" target="_blank"&gt;http://goo.gl/WR3VkJ&lt;/A&gt;&lt;BR /&gt;full config file &lt;A class="js-link post-link" href="http://www.linkedin.com/redir/redirect?url=http%3A%2F%2Fpastebin%2Ecom%2FPXARPh2a&amp;amp;urlhash=NPbs&amp;amp;_t=tracking_anet" target="_blank"&gt;http://pastebin.com/PXARPh2a&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It seems pretty bad, and the video claims "This cannot be resolved by a patch or a signature as the single-pass architecture is fundamentally flawed."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are opening a ticket on this to find out more.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Dec 2015 14:08:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-bypass-question-mcafee-evader/m-p/69159#M40184</guid>
      <dc:creator>Demast</dc:creator>
      <dc:date>2015-12-08T14:08:24Z</dc:date>
    </item>
    <item>
      <title>Re: PA Bypass Question - McAfee Evader</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-bypass-question-mcafee-evader/m-p/69166#M40187</link>
      <description>&lt;P&gt;Fast response from PA supprt:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;On November 30th, a video was posted by the owner of the NetSecVulns YouTube channel titled "666 different ways to bypass palo alto networks in 6 minutes”.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;In the first video, posted Nov 30th, NetSecVulns sets up a lab with a Windows XP SP2 victim and the Stonesoft Evader tool configured to use the Conficker attack and a Palo Alto Networks Next-Generation Firewall in Layer 3 mode placed in between 2 endpoints. Great pains are made to show that our firewall is configured using our Best Practices configuration document. Once the Evader tool completes its run, the administrator shows that our firewall missed 666 evasion attempts.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;In reality, NetSecVulns skipped step 4 in our Best Practices document: creation of an unknown application block rule. This can be verified in the video (at 2:20) where we see a single allow rule instead of the expected 2 rules with the first one dropping unknown applications. Later in the video, at 4:31 and 5:49, it shows the "threat logs”, carefully avoiding "traffic logs" where we would have seen unknown-tcp sessions allowed through.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;After running this test in our own lab on PAN-OS 7.0.3, and correctly following the same Best Practices document, we verified that we block&amp;nbsp;&lt;STRONG&gt;&lt;U&gt;100%&lt;/U&gt;&lt;/STRONG&gt;&amp;nbsp;of the 204,090 evasion attempts. Also note that this test is performed by our internal QA team for each PAN-OS major and minor feature release.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;On Dec 3&lt;SUP&gt;rd&lt;/SUP&gt;, NetSecVulns posted a new video, correcting the "step 4" error. However once again they did not follow all steps in the Best Practices document, rendering the test inaccurate and misleading.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Dec 2015 14:21:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-bypass-question-mcafee-evader/m-p/69166#M40187</guid>
      <dc:creator>Demast</dc:creator>
      <dc:date>2015-12-08T14:21:59Z</dc:date>
    </item>
  </channel>
</rss>

