<?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 Vulnerability assessment (False Positives and Evaluation Method) in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/vulnerability-assessment-false-positives-and-evaluation-method/m-p/7844#M5793</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a good write-up on how the vulnerability assessment is performed and how it actually works?&amp;nbsp; Specifically, we had a web server set up in front of a MSSQL server -- for hosts connecting to the web server from IP segment "A" it worked fine, but hosts from segment "B" caused the creation of "&lt;A href="https://216.130.23.127/esp/monitor.esp#" style="color: #036dda; text-decoration: none;" title="Threat Detail"&gt;HTTP SQL Injection Attempt&lt;/A&gt; " messages in the Threats log.&amp;nbsp; Adding an exception not only fixed the problem for segment "B", but also the other segments that couldn't login in (the web server's page was authenticating against the SQL server).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 Apr 2011 20:47:55 GMT</pubDate>
    <dc:creator>bhelman</dc:creator>
    <dc:date>2011-04-22T20:47:55Z</dc:date>
    <item>
      <title>Vulnerability assessment (False Positives and Evaluation Method)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vulnerability-assessment-false-positives-and-evaluation-method/m-p/7844#M5793</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a good write-up on how the vulnerability assessment is performed and how it actually works?&amp;nbsp; Specifically, we had a web server set up in front of a MSSQL server -- for hosts connecting to the web server from IP segment "A" it worked fine, but hosts from segment "B" caused the creation of "&lt;A href="https://216.130.23.127/esp/monitor.esp#" style="color: #036dda; text-decoration: none;" title="Threat Detail"&gt;HTTP SQL Injection Attempt&lt;/A&gt; " messages in the Threats log.&amp;nbsp; Adding an exception not only fixed the problem for segment "B", but also the other segments that couldn't login in (the web server's page was authenticating against the SQL server).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 20:47:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vulnerability-assessment-false-positives-and-evaluation-method/m-p/7844#M5793</guid>
      <dc:creator>bhelman</dc:creator>
      <dc:date>2011-04-22T20:47:55Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability assessment (False Positives and Evaluation Method)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vulnerability-assessment-false-positives-and-evaluation-method/m-p/7845#M5794</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would start with a packet capture, and see what the requests look like.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Apr 2011 19:52:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vulnerability-assessment-false-positives-and-evaluation-method/m-p/7845#M5794</guid>
      <dc:creator>mharding</dc:creator>
      <dc:date>2011-04-26T19:52:49Z</dc:date>
    </item>
  </channel>
</rss>

