<?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 Custom Vulnerability Protection in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/custom-vulnerability-protection/m-p/147112#M49319</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've made a custum VP and included into my VP group. In security policy I have applied the standard one (NOT my personal VP) to a security policy but when I go in monitor threat I see that matched also the custom VP. Why??&lt;/P&gt;</description>
    <pubDate>Fri, 10 Mar 2017 16:31:00 GMT</pubDate>
    <dc:creator>s_quasar</dc:creator>
    <dc:date>2017-03-10T16:31:00Z</dc:date>
    <item>
      <title>Custom Vulnerability Protection</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-vulnerability-protection/m-p/147112#M49319</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've made a custum VP and included into my VP group. In security policy I have applied the standard one (NOT my personal VP) to a security policy but when I go in monitor threat I see that matched also the custom VP. Why??&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2017 16:31:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-vulnerability-protection/m-p/147112#M49319</guid>
      <dc:creator>s_quasar</dc:creator>
      <dc:date>2017-03-10T16:31:00Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Vulnerability Protection</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-vulnerability-protection/m-p/147349#M49365</link>
      <description>&lt;P&gt;I guess you've set flags for your custom VP in a way that some rule in general (default) protection profile matches them.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Mar 2017 07:38:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-vulnerability-protection/m-p/147349#M49365</guid>
      <dc:creator>santonic</dc:creator>
      <dc:date>2017-03-13T07:38:35Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Vulnerability Protection</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-vulnerability-protection/m-p/147370#M49380</link>
      <description>&lt;P&gt;a custom vulnerability works pretty much the same way as a custom URL category: it automatically gets added to all Vulnerability profiles.&lt;/P&gt;

&lt;P&gt;If you only want a specific profile to enforce upon it, you should set the default action of the custom vulnerability&amp;nbsp;to alert (no action) or allow (no action + no logging) and then manually set an action (drop, reset ,..) in the profile you want to use for enforcement.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Mar 2017 09:02:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-vulnerability-protection/m-p/147370#M49380</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-03-13T09:02:54Z</dc:date>
    </item>
  </channel>
</rss>

