<?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: NRD protection in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/nrd-protection/m-p/305847#M719</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/41719"&gt;@ehartcoghlin&lt;/a&gt;&amp;nbsp;You are correct that the URL filtering will only work on client to server web traffic. It can only control users accessing particular domains, but not traffic initiated from those domain. The reason is that the firewall can only see the source IP in incoming traffic and URL filtering looks at the actual URL in the http headers.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Surely you can filter particular emails at the email server level or if you have the feed of IPs of NRDs, then you can import it as an dynamic IP list in the firewall and block SMTP traffic based on that list.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 07 Jan 2020 09:24:42 GMT</pubDate>
    <dc:creator>BatD</dc:creator>
    <dc:date>2020-01-07T09:24:42Z</dc:date>
    <item>
      <title>NRD protection</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/nrd-protection/m-p/305800#M716</link>
      <description>&lt;P&gt;Will enabling an NRD URL filter be able to filter inbound SMTP connections and block for deny emails from a Newly Registered Domain or is it designed to simply block clients from connecting to URLs that have Newly Registered Domains? Is there any way to filter email for NRDs or is that the domain of a SPAM filter?&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jan 2020 21:47:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/nrd-protection/m-p/305800#M716</guid>
      <dc:creator>ehartcoghlin</dc:creator>
      <dc:date>2020-01-06T21:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: NRD protection</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/nrd-protection/m-p/305847#M719</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/41719"&gt;@ehartcoghlin&lt;/a&gt;&amp;nbsp;You are correct that the URL filtering will only work on client to server web traffic. It can only control users accessing particular domains, but not traffic initiated from those domain. The reason is that the firewall can only see the source IP in incoming traffic and URL filtering looks at the actual URL in the http headers.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Surely you can filter particular emails at the email server level or if you have the feed of IPs of NRDs, then you can import it as an dynamic IP list in the firewall and block SMTP traffic based on that list.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2020 09:24:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/nrd-protection/m-p/305847#M719</guid>
      <dc:creator>BatD</dc:creator>
      <dc:date>2020-01-07T09:24:42Z</dc:date>
    </item>
  </channel>
</rss>

