<?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: DNS Signatures in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530915#M1864</link>
    <description>I opened up a support case and they had already deactivated the signature.  I removed the signature exception and found that the domain was still working.  It's good to know that I can just open a support case to get false positives looked at.  In the 8 years as a Palo customer, I have never ran into this before.&lt;BR /&gt;</description>
    <pubDate>Mon, 13 Feb 2023 18:26:16 GMT</pubDate>
    <dc:creator>Jared_Hainline</dc:creator>
    <dc:date>2023-02-13T18:26:16Z</dc:date>
    <item>
      <title>DNS Signatures</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530714#M1856</link>
      <description>&lt;P&gt;Our Palo started blocking a 3rd party site that is used by our organization.&amp;nbsp; It was being sinkholed.&amp;nbsp; I found the threat ID and it appears that it was tagged as virus/spyware.&amp;nbsp; Short of allowing an exception for this one threat ID, is there any other action that can be taken to have palo re-evaluate and create a new signature that would deem the site ok?&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am also happy to inform the users to use a different site if it really is a threat.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2023 17:52:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530714#M1856</guid>
      <dc:creator>Jared_Hainline</dc:creator>
      <dc:date>2023-02-10T17:52:09Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Signatures</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530718#M1857</link>
      <description>&lt;P&gt;Is site categorized as malware?&lt;/P&gt;
&lt;P&gt;You can request recategorization at&amp;nbsp;&lt;A href="https://urlfiltering.paloaltonetworks.com/" target="_blank" rel="noopener"&gt;https://urlfiltering.paloaltonetworks.com/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If it is identified by vulnerability signatures then you can open support case with Palo and provide packet capture.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2023 18:43:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530718#M1857</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2023-02-10T18:43:27Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Signatures</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530719#M1858</link>
      <description>According to the threat vault, it is listed under DNS Signatures, type is AntiVirus and wildfire.  So, the domain got sinkholed.  We don't have the URL filtering license so that wasn't a possibility.&lt;BR /&gt;&lt;BR /&gt;I know I can create an exception for this specific Threat ID.  But if it is a true threat, don't really want to do that.  If the threat ID says that it's Antivirus/WildFire.  How would we get it re-examined?  Does this mean that virus activity was detected on the domain name and that's why the DNS signature was made?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Feb 2023 19:02:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530719#M1858</guid>
      <dc:creator>Jared_Hainline</dc:creator>
      <dc:date>2023-02-10T19:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Signatures</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530721#M1859</link>
      <description>&lt;P&gt;&lt;A href="https://threatvault.paloaltonetworks.com/" target="_blank"&gt;https://threatvault.paloaltonetworks.com/&lt;/A&gt;&amp;nbsp;shows you when this threat id was generated.&lt;/P&gt;
&lt;P&gt;Most likely it was auto generated by Wildfire sandbox.&lt;/P&gt;
&lt;P&gt;Either false positive or someone actually downloaded malicious file from the website and caused website to be tagged as malware site.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2023 19:09:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530721#M1859</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2023-02-10T19:09:03Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Signatures</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530722#M1860</link>
      <description>Yeah, so, how would I go about verifying which one it is?  If it's a false positive, then that needs to be corrected.  If not, then I don't want to add an exception to permit this domain.&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Feb 2023 19:11:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530722#M1860</guid>
      <dc:creator>Jared_Hainline</dc:creator>
      <dc:date>2023-02-10T19:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Signatures</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530725#M1861</link>
      <description>&lt;P&gt;Open support case with Palo.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.paloaltonetworks.com/" target="_blank"&gt;https://support.paloaltonetworks.com/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2023 19:18:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530725#M1861</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2023-02-10T19:18:37Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Signatures</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530815#M1863</link>
      <description>&lt;P&gt;I suggest opening a support case.&lt;BR /&gt;Whether it's False positive or True positive really depends on the signature (the unique threat ID is necessary for further investigation).&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2023 01:40:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530815#M1863</guid>
      <dc:creator>ymiyashita</dc:creator>
      <dc:date>2023-02-13T01:40:30Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Signatures</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530915#M1864</link>
      <description>I opened up a support case and they had already deactivated the signature.  I removed the signature exception and found that the domain was still working.  It's good to know that I can just open a support case to get false positives looked at.  In the 8 years as a Palo customer, I have never ran into this before.&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Feb 2023 18:26:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-signatures/m-p/530915#M1864</guid>
      <dc:creator>Jared_Hainline</dc:creator>
      <dc:date>2023-02-13T18:26:16Z</dc:date>
    </item>
  </channel>
</rss>

