<?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: Block outbound NTLM auth in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/block-outbound-ntlm-auth/m-p/210097#M61381</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/48237"&gt;@DPoppleton&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I would probably just ensure that 445, 137, 139 are blocked to the untrust interface. I wouldn't even do this by app-id unless you need those ports open for something else to function correctly. As&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/5300"&gt;@Brandon_Wertz&lt;/a&gt;&amp;nbsp;already pointed out, this shouldn't be allowed by your configuration anyways.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 13 Apr 2018 20:03:14 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2018-04-13T20:03:14Z</dc:date>
    <item>
      <title>Block outbound NTLM auth</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-outbound-ntlm-auth/m-p/209984#M61355</link>
      <description>&lt;P&gt;With CVE-2018-0950 from Microsoft, if an outlook user clicks on an OLE object in an RTF email, the client will send credentials try to logon. Our security group is quite concerned about this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While allowing ports 445, 137 and 139 out to the internet is a really bad idea, they want to make sure that it is explicitly blocked. Is the application "ms-netlogon" the app to block? It includes many more ports than just the three mentioned above. Is anyone else doing this? Are 'we' just overreacting?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Apr 2018 12:36:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-outbound-ntlm-auth/m-p/209984#M61355</guid>
      <dc:creator>DPoppleton</dc:creator>
      <dc:date>2018-04-13T12:36:38Z</dc:date>
    </item>
    <item>
      <title>Re: Block outbound NTLM auth</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-outbound-ntlm-auth/m-p/210076#M61369</link>
      <description>&lt;P&gt;I would think that your firewall policy would already be preventing that application; either by default or exception.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If not, I don't think it would be over-reacting to ensure it's blocked.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Apr 2018 18:41:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-outbound-ntlm-auth/m-p/210076#M61369</guid>
      <dc:creator>Brandon_Wertz</dc:creator>
      <dc:date>2018-04-13T18:41:59Z</dc:date>
    </item>
    <item>
      <title>Re: Block outbound NTLM auth</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-outbound-ntlm-auth/m-p/210097#M61381</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/48237"&gt;@DPoppleton&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I would probably just ensure that 445, 137, 139 are blocked to the untrust interface. I wouldn't even do this by app-id unless you need those ports open for something else to function correctly. As&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/5300"&gt;@Brandon_Wertz&lt;/a&gt;&amp;nbsp;already pointed out, this shouldn't be allowed by your configuration anyways.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Apr 2018 20:03:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-outbound-ntlm-auth/m-p/210097#M61381</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-04-13T20:03:14Z</dc:date>
    </item>
  </channel>
</rss>

