<?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 Signature Review/Modification in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/signature-review-modification/m-p/2356#M1741</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I tried searching through the discussions but didn't see anything regarding this. Is it possible to see what the actual threats are matching on? Essentially what their signature is so I can make a more accurate analysis of the validity. For example, Scripts/Win32.Rsrc.o is classified as a Medium severity virus threat. The description is simply "This signature detected Scripts/Win32.Rsrc.o" which doesn't allow me to make any sort of knowledgeable decission regarding next-steps for investigation. I haven't dropped down to the CLI yet to see if it's possible to peer into the signatures and figure out what exactly is being keyed off in the packet, but I would hope this feature exists within the web UI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In addition to the above, is it possible to modify the signatures and define what networks (src/dst) would be required to trigger it? Our company has a lot of home grown apps which trigger on things that are not malicious; however, I don't want my only available course of action to be excluded it entirely from triggering.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Sep 2011 17:08:16 GMT</pubDate>
    <dc:creator>jeff_white1</dc:creator>
    <dc:date>2011-09-21T17:08:16Z</dc:date>
    <item>
      <title>Signature Review/Modification</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/signature-review-modification/m-p/2356#M1741</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I tried searching through the discussions but didn't see anything regarding this. Is it possible to see what the actual threats are matching on? Essentially what their signature is so I can make a more accurate analysis of the validity. For example, Scripts/Win32.Rsrc.o is classified as a Medium severity virus threat. The description is simply "This signature detected Scripts/Win32.Rsrc.o" which doesn't allow me to make any sort of knowledgeable decission regarding next-steps for investigation. I haven't dropped down to the CLI yet to see if it's possible to peer into the signatures and figure out what exactly is being keyed off in the packet, but I would hope this feature exists within the web UI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In addition to the above, is it possible to modify the signatures and define what networks (src/dst) would be required to trigger it? Our company has a lot of home grown apps which trigger on things that are not malicious; however, I don't want my only available course of action to be excluded it entirely from triggering.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Sep 2011 17:08:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/signature-review-modification/m-p/2356#M1741</guid>
      <dc:creator>jeff_white1</dc:creator>
      <dc:date>2011-09-21T17:08:16Z</dc:date>
    </item>
    <item>
      <title>Re: Signature Review/Modification</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/signature-review-modification/m-p/2357#M1742</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looked in the CLI and the patterns are all encrypted (proprietary issue I assume). I also can't seem to find a way to edit the predefined signatures for the second part of my original post, just editing shared signatures you create yourself.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Sep 2011 18:29:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/signature-review-modification/m-p/2357#M1742</guid>
      <dc:creator>jeff_white1</dc:creator>
      <dc:date>2011-09-21T18:29:58Z</dc:date>
    </item>
    <item>
      <title>Re: Signature Review/Modification</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/signature-review-modification/m-p/2358#M1743</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@jeff.white:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the signatures are not viewable by the end-user and this is by design. As a general rule we are not going to expose the details behind our threat detection methodology and signatures to end-users. If you want to have a detailed discussion on this topic I encourage you to talk to your sales team.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With regard to your second question: Yes this is possible if you create multiple threat (vulnerability/spyware/AV) profiles and apply them to security policies that are crafted to apply to specific source/destination FQDNs or IP addresses. Each threat profile can be tailored to specific environments/servers by using exclusions on specific threats that are not relevant for the traffic to/from the host/network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Benjamin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Sep 2011 19:21:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/signature-review-modification/m-p/2358#M1743</guid>
      <dc:creator>bpappas</dc:creator>
      <dc:date>2011-09-21T19:21:29Z</dc:date>
    </item>
  </channel>
</rss>

