<?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 Regarding sinkholed hosts in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/regarding-sinkholed-hosts/m-p/407111#M92197</link>
    <description>&lt;P&gt;Hello Bros,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; We have subscribed to palo alto dns-security and the license has been applied to the device.&lt;/P&gt;&lt;P&gt;Rules with anti-spyware "dns-security sinkhole action enabled".&lt;/P&gt;&lt;P&gt;Now regarding the hosts with sinkhole action, that means these hosts trying to connect to a malicious domains.&lt;/P&gt;&lt;P&gt;These trials blocked but is these another recommended actions to be taken towards these hosts? Is there a recommended method to stop them from trying to connect to these malicious domains?&lt;/P&gt;&lt;P&gt;TIA&lt;/P&gt;</description>
    <pubDate>Sun, 16 May 2021 15:13:52 GMT</pubDate>
    <dc:creator>MRamadanAHafiez</dc:creator>
    <dc:date>2021-05-16T15:13:52Z</dc:date>
    <item>
      <title>Regarding sinkholed hosts</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/regarding-sinkholed-hosts/m-p/407111#M92197</link>
      <description>&lt;P&gt;Hello Bros,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; We have subscribed to palo alto dns-security and the license has been applied to the device.&lt;/P&gt;&lt;P&gt;Rules with anti-spyware "dns-security sinkhole action enabled".&lt;/P&gt;&lt;P&gt;Now regarding the hosts with sinkhole action, that means these hosts trying to connect to a malicious domains.&lt;/P&gt;&lt;P&gt;These trials blocked but is these another recommended actions to be taken towards these hosts? Is there a recommended method to stop them from trying to connect to these malicious domains?&lt;/P&gt;&lt;P&gt;TIA&lt;/P&gt;</description>
      <pubDate>Sun, 16 May 2021 15:13:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/regarding-sinkholed-hosts/m-p/407111#M92197</guid>
      <dc:creator>MRamadanAHafiez</dc:creator>
      <dc:date>2021-05-16T15:13:52Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding sinkholed hosts</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/regarding-sinkholed-hosts/m-p/407121#M92199</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/159497"&gt;@MRamadanAHafiez&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The recommendation would be to check these hosts if there is some sort of malware/spyware running which tries to connect to these domains. With the sinkhole feature it shows you these hosts which otherwise wouldn't be identified.&lt;/P&gt;
&lt;P&gt;The little problem is to differentiate if it really was some sort of malware or only connections done by the users browsers which probably are the reason for most of the sinkholed connections. It's not that (my assumption) that users directly connect to these domains, these requests are because of advertisements on the actual websites or because of malicious scripts somehow get executed on the websites that the users open.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So there is no way to fully stop clients connecting to domains whitch are redirected to the sinkhole, but it still is a very helpful feature to identify clients which should be checked.&lt;/P&gt;</description>
      <pubDate>Sun, 16 May 2021 15:52:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/regarding-sinkholed-hosts/m-p/407121#M92199</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2021-05-16T15:52:14Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding sinkholed hosts</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/regarding-sinkholed-hosts/m-p/407424#M92231</link>
      <description>&lt;P&gt;Thank you so much Bro.&lt;/P&gt;</description>
      <pubDate>Mon, 17 May 2021 23:40:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/regarding-sinkholed-hosts/m-p/407424#M92231</guid>
      <dc:creator>MRamadanAHafiez</dc:creator>
      <dc:date>2021-05-17T23:40:28Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding sinkholed hosts</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/regarding-sinkholed-hosts/m-p/423009#M94129</link>
      <description>&lt;P&gt;If you are using XDR you can setup an IOC to alert when a client connects to the sinkhole IP.&amp;nbsp; Then put an exclusion on the the alert if it is coming from a browser and then investigate any endpoint that has a process other than a browser connecting to the sinkhole.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jul 2021 12:58:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/regarding-sinkholed-hosts/m-p/423009#M94129</guid>
      <dc:creator>JasonPeterson</dc:creator>
      <dc:date>2021-07-29T12:58:59Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding sinkholed hosts</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/regarding-sinkholed-hosts/m-p/423388#M94156</link>
      <description>&lt;P&gt;Thank you for participation but unfortunately we don't have XDR.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jul 2021 12:23:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/regarding-sinkholed-hosts/m-p/423388#M94156</guid>
      <dc:creator>MRamadanAHafiez</dc:creator>
      <dc:date>2021-07-30T12:23:38Z</dc:date>
    </item>
  </channel>
</rss>

