<?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: NSS Lab Report in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23748#M17305</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, the NSS labs certify its tests in 3 categories:&lt;/P&gt;&lt;P&gt;NSS Gold Award&lt;/P&gt;&lt;P&gt;NSS Approved&lt;/P&gt;&lt;P&gt;NSS Tested&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the lab report indicate the results NSS tested is the a specific reason for this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nando&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Aug 2010 09:47:42 GMT</pubDate>
    <dc:creator>helpdesk</dc:creator>
    <dc:date>2010-08-27T09:47:42Z</dc:date>
    <item>
      <title>NSS Lab Report</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23744#M17301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; I received an email recently touting the results of the NSS Lab Report.&amp;nbsp; After reading the report, I do have a question.&amp;nbsp; What tuning measures did the engineer implement that made such a dramatic improvement in the effectivness that was reported in the report?&amp;nbsp; It claims the effectiveness moved from the 40% range in the default configuration up to the 93.4% number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to know what those changes were so I can verify that I have already made the necessary changes or if I need to alter my configuration.&amp;nbsp; I am close to moving my new unit into production and am very interested in seeing what they did.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Aug 2010 12:47:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23744#M17301</guid>
      <dc:creator>will74103</dc:creator>
      <dc:date>2010-08-26T12:47:31Z</dc:date>
    </item>
    <item>
      <title>Re: NSS Lab Report</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23745#M17302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Default and Tuned settings for the NSS Labs tests were as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Default - Using a default vulnerability protection profile which sets  &lt;/P&gt;&lt;P&gt;default actions for all severities of signatures.&lt;/P&gt;&lt;P&gt;Tuned - All severities of signatures set to block.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NSS Labs does not count alerting on an attack as being detected. It  &lt;/P&gt;&lt;P&gt;must block. In the default profile, many of our signatures are set to  &lt;/P&gt;&lt;P&gt;alert rather than block and were then not counted in the effectiveness.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alfred&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Aug 2010 16:18:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23745#M17302</guid>
      <dc:creator>fredallee</dc:creator>
      <dc:date>2010-08-26T16:18:14Z</dc:date>
    </item>
    <item>
      <title>Re: NSS Lab Report</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23746#M17303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the update!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Aug 2010 17:44:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23746#M17303</guid>
      <dc:creator>will74103</dc:creator>
      <dc:date>2010-08-26T17:44:26Z</dc:date>
    </item>
    <item>
      <title>Re: NSS Lab Report</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23747#M17304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, using "show filter" button I can filter for any column but there is no way to filter which are the default enabled filter.&lt;/P&gt;&lt;P&gt;Have you any suggestion abot it? Is there a way to show the default enabled filter?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thank you&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nando&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Aug 2010 09:41:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23747#M17304</guid>
      <dc:creator>helpdesk</dc:creator>
      <dc:date>2010-08-27T09:41:34Z</dc:date>
    </item>
    <item>
      <title>Re: NSS Lab Report</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23748#M17305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, the NSS labs certify its tests in 3 categories:&lt;/P&gt;&lt;P&gt;NSS Gold Award&lt;/P&gt;&lt;P&gt;NSS Approved&lt;/P&gt;&lt;P&gt;NSS Tested&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the lab report indicate the results NSS tested is the a specific reason for this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nando&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Aug 2010 09:47:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23748#M17305</guid>
      <dc:creator>helpdesk</dc:creator>
      <dc:date>2010-08-27T09:47:42Z</dc:date>
    </item>
    <item>
      <title>Re: NSS Lab Report</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23749#M17306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nando,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your question. NSS Labs offers different types of testing.  &lt;/P&gt;&lt;P&gt;We participated in the standalone public IPS test. The test results  &lt;/P&gt;&lt;P&gt;are either given a rating of recommend, neutral, or caution. We  &lt;/P&gt;&lt;P&gt;received the highest rating of recommend. The Gold, Approved, and  &lt;/P&gt;&lt;P&gt;Tested awards are applied to their monthly testing service called  &lt;/P&gt;&lt;P&gt;Security Update Monitor(SUM). Please refer to the NSS Labs page for  &lt;/P&gt;&lt;P&gt;more details on the SUM testing and ratings: http://nsslabs.com/SUM.  &lt;/P&gt;&lt;P&gt;The bottom of the page states, "Starting Q1, 2009, NSS Labs awards  &lt;/P&gt;&lt;P&gt;participating IPS products at the end of each quarter. All vendors are  &lt;/P&gt;&lt;P&gt;invited to test monthly, and the average of three months scores are  &lt;/P&gt;&lt;P&gt;used to determine the award level. NSS Labs Gold will be awarded for  &lt;/P&gt;&lt;P&gt;accuracy above 95%, Approved above 70% and Tested for all other  &lt;/P&gt;&lt;P&gt;results."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if you have any other questions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alfred&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Aug 2010 16:43:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23749#M17306</guid>
      <dc:creator>fredallee</dc:creator>
      <dc:date>2010-08-27T16:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: NSS Lab Report</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23750#M17307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm also interested in this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So right now on our PAN, we're using the default profile for vulnerability, spyware and virus on various outbound and inbound rules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The test set the default actions to block for everything, but can I confirm that even on the defaults that the various logs on the "Monitor" tab would show any and all incidents?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just want to be sure that because an action/response is set to simply discard/reset that it is still going to be logged and obvious to us?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 28 Aug 2010 10:23:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23750#M17307</guid>
      <dc:creator>networkadmin</dc:creator>
      <dc:date>2010-08-28T10:23:13Z</dc:date>
    </item>
    <item>
      <title>Re: NSS Lab Report</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23751#M17308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The NSS test was only for vulnerability protection (IPS), so they  &lt;/P&gt;&lt;P&gt;didn't have any of the other security profiles set. The default  &lt;/P&gt;&lt;P&gt;actions were set for all vulnerability protection signatures. In the  &lt;/P&gt;&lt;P&gt;default profile, the critical, high and medium severity signatures are  &lt;/P&gt;&lt;P&gt;turned on using the default action associated with each signature,  &lt;/P&gt;&lt;P&gt;which is either block or alert. The low and informational signatures  &lt;/P&gt;&lt;P&gt;are not turned on, meaning that they would not be logged. If you would  &lt;/P&gt;&lt;P&gt;like to see those at least get alerted, simply create a new  &lt;/P&gt;&lt;P&gt;vulnerability protection profile and select alert as the action for  &lt;/P&gt;&lt;P&gt;low and informational severity signatures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alfred&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 28 Aug 2010 20:27:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23751#M17308</guid>
      <dc:creator>fredallee</dc:creator>
      <dc:date>2010-08-28T20:27:38Z</dc:date>
    </item>
    <item>
      <title>Re: NSS Lab Report</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23752#M17309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Alfred.&amp;nbsp; If I create a new profile, is there any reason not to set all levels to "default"?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm working on the theory that Palo Alto have set each vulnerability ID to perform the most suitable action so I guess I'm not sure why low/informational incidents aren't set to do anything by default? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 29 Aug 2010 10:39:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23752#M17309</guid>
      <dc:creator>networkadmin</dc:creator>
      <dc:date>2010-08-29T10:39:41Z</dc:date>
    </item>
    <item>
      <title>Re: NSS Lab Report</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23753#M17310</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You're right that we have set each vulnerability ID to perform the  &lt;/P&gt;&lt;P&gt;most suitable action. So, they are essentially our recommended actions  &lt;/P&gt;&lt;P&gt;for most networks. The low and informational severity attacks are not  &lt;/P&gt;&lt;P&gt;turned on for the default profile because they may fire on more common  &lt;/P&gt;&lt;P&gt;events like an HTTP options request, which in and of itself is  &lt;/P&gt;&lt;P&gt;legitimate traffic, but could also indicate that someone is looking to  &lt;/P&gt;&lt;P&gt;see what resources are available on a web server. This event could  &lt;/P&gt;&lt;P&gt;precede an attack on a web server. So it depends on whether or not you  &lt;/P&gt;&lt;P&gt;want to see these types of events or not. If you select default for  &lt;/P&gt;&lt;P&gt;low and informational severity signatures, you will start to see these  &lt;/P&gt;&lt;P&gt;types of events being logged.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alfred&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 29 Aug 2010 16:11:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23753#M17310</guid>
      <dc:creator>fredallee</dc:creator>
      <dc:date>2010-08-29T16:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: NSS Lab Report</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23754#M17311</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Alfred, makes sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I'd be interested in perhaps seeing as a "jack of all trades" network admin is a best practise for outbound and inbound vuln profiles.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example we obviously have our internal users/servers we want to protect from exploits, but we also have things such as an internal Outlook Web Access server which the Palo publishes - right now I have the default profile applied to that, but it would be nice at some point to perhaps see some guides on what kinds of profiles are recommended for different scenarios.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 29 Aug 2010 16:17:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/nss-lab-report/m-p/23754#M17311</guid>
      <dc:creator>networkadmin</dc:creator>
      <dc:date>2010-08-29T16:17:48Z</dc:date>
    </item>
  </channel>
</rss>

