<?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 Paloalto detected vulnerability traffic but the traffic is allowed in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/paloalto-detected-vulnerability-traffic-but-the-traffic-is/m-p/184294#M56530</link>
    <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SIEM tool - QRadar&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Firewall - Paloalto&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Received one exploit alert in our siem console&lt;/P&gt;&lt;P&gt;Source ip is internal workstation reaching to external remote public ips like yahoo,aws&lt;/P&gt;&lt;P&gt;alert name is exploit events across multiple targets containing generic prompt xss vulnerability&lt;/P&gt;&lt;P&gt;Paloalto detected&amp;nbsp; the vulnerability traffic and sent those logs to SIEM however the traffic is allowed in paloalto&lt;BR /&gt;what might be the reason?&lt;/P&gt;</description>
    <pubDate>Sat, 28 Oct 2017 15:47:32 GMT</pubDate>
    <dc:creator>saighanasyam42</dc:creator>
    <dc:date>2017-10-28T15:47:32Z</dc:date>
    <item>
      <title>Paloalto detected vulnerability traffic but the traffic is allowed</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/paloalto-detected-vulnerability-traffic-but-the-traffic-is/m-p/184294#M56530</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SIEM tool - QRadar&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Firewall - Paloalto&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Received one exploit alert in our siem console&lt;/P&gt;&lt;P&gt;Source ip is internal workstation reaching to external remote public ips like yahoo,aws&lt;/P&gt;&lt;P&gt;alert name is exploit events across multiple targets containing generic prompt xss vulnerability&lt;/P&gt;&lt;P&gt;Paloalto detected&amp;nbsp; the vulnerability traffic and sent those logs to SIEM however the traffic is allowed in paloalto&lt;BR /&gt;what might be the reason?&lt;/P&gt;</description>
      <pubDate>Sat, 28 Oct 2017 15:47:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/paloalto-detected-vulnerability-traffic-but-the-traffic-is/m-p/184294#M56530</guid>
      <dc:creator>saighanasyam42</dc:creator>
      <dc:date>2017-10-28T15:47:32Z</dc:date>
    </item>
    <item>
      <title>Re: Paloalto detected vulnerability traffic but the traffic is allowed</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/paloalto-detected-vulnerability-traffic-but-the-traffic-is/m-p/184478#M56575</link>
      <description>&lt;P&gt;have you checke dthe threat log? there should be an associated action to the threat which is tied to the configuration of the security profile assovciated with the security policy that allows the session to start&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;if the threat is of severifty 'informational; for example, the default action is typically 'alert' which simply generates a log but takes no action&lt;/P&gt;</description>
      <pubDate>Mon, 30 Oct 2017 14:32:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/paloalto-detected-vulnerability-traffic-but-the-traffic-is/m-p/184478#M56575</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-10-30T14:32:49Z</dc:date>
    </item>
  </channel>
</rss>

