<?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 Finding the offending file associated with threat event in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/finding-the-offending-file-associated-with-threat-event/m-p/242931#M476</link>
    <description>I’m having an issue identifying the offending file that triggered a vulnerability detection. We had an IT admin transfer a large batch of files across a network segment that traveled on of or PA firewllls. One of the transfers triggered an alert for an Adobe Reader remote code execution signature. The “file name” in Panorama shows “content.xml” but does not show the actual name of the file that contained code that matched the signature.&lt;BR /&gt;&lt;BR /&gt;How does one find the actual offending file in instances like this?&lt;BR /&gt;&lt;BR /&gt;We’ve encounteed similar issues with the virus profile too. During the transfer of files the palo will alert on a virus detection but will not show the actual name of the malicious file. This makes response very challenging.</description>
    <pubDate>Wed, 12 Dec 2018 02:01:36 GMT</pubDate>
    <dc:creator>r_gine</dc:creator>
    <dc:date>2018-12-12T02:01:36Z</dc:date>
    <item>
      <title>Finding the offending file associated with threat event</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/finding-the-offending-file-associated-with-threat-event/m-p/242931#M476</link>
      <description>I’m having an issue identifying the offending file that triggered a vulnerability detection. We had an IT admin transfer a large batch of files across a network segment that traveled on of or PA firewllls. One of the transfers triggered an alert for an Adobe Reader remote code execution signature. The “file name” in Panorama shows “content.xml” but does not show the actual name of the file that contained code that matched the signature.&lt;BR /&gt;&lt;BR /&gt;How does one find the actual offending file in instances like this?&lt;BR /&gt;&lt;BR /&gt;We’ve encounteed similar issues with the virus profile too. During the transfer of files the palo will alert on a virus detection but will not show the actual name of the malicious file. This makes response very challenging.</description>
      <pubDate>Wed, 12 Dec 2018 02:01:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/finding-the-offending-file-associated-with-threat-event/m-p/242931#M476</guid>
      <dc:creator>r_gine</dc:creator>
      <dc:date>2018-12-12T02:01:36Z</dc:date>
    </item>
  </channel>
</rss>

