<?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 How to take mcafee virus scan and endpoint security version information into account? in Security</title>
    <link>https://community.splunk.com/t5/Security/How-to-take-mcafee-virus-scan-and-endpoint-security-version/m-p/317463#M12616</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;The EPOProdPropsView_VIRUSCAN fields are not present in the new version of McAfee : Endpoint Security replaces Virus Scan. Therefore, we cannot access the version data anymore, which is a problem for security logs analysis.&lt;BR /&gt;
We have seen an answer which brings a partial solution to our problem:&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/626506/moving-from-mcafee-vse-to-ens.html"&gt;https://answers.splunk.com/answers/626506/moving-from-mcafee-vse-to-ens.html&lt;/A&gt;&lt;BR /&gt;
However, the two versions are currently being used,  we need the query to take both into account.&lt;/P&gt;

&lt;P&gt;Could the Splunk team who develops the McAfee addon update the query to take both versions into account?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;Best regards,&lt;/P&gt;</description>
    <pubDate>Mon, 09 Apr 2018 12:22:13 GMT</pubDate>
    <dc:creator>SarahSplunk123</dc:creator>
    <dc:date>2018-04-09T12:22:13Z</dc:date>
    <item>
      <title>How to take mcafee virus scan and endpoint security version information into account?</title>
      <link>https://community.splunk.com/t5/Security/How-to-take-mcafee-virus-scan-and-endpoint-security-version/m-p/317463#M12616</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;The EPOProdPropsView_VIRUSCAN fields are not present in the new version of McAfee : Endpoint Security replaces Virus Scan. Therefore, we cannot access the version data anymore, which is a problem for security logs analysis.&lt;BR /&gt;
We have seen an answer which brings a partial solution to our problem:&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/626506/moving-from-mcafee-vse-to-ens.html"&gt;https://answers.splunk.com/answers/626506/moving-from-mcafee-vse-to-ens.html&lt;/A&gt;&lt;BR /&gt;
However, the two versions are currently being used,  we need the query to take both into account.&lt;/P&gt;

&lt;P&gt;Could the Splunk team who develops the McAfee addon update the query to take both versions into account?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;Best regards,&lt;/P&gt;</description>
      <pubDate>Mon, 09 Apr 2018 12:22:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-take-mcafee-virus-scan-and-endpoint-security-version/m-p/317463#M12616</guid>
      <dc:creator>SarahSplunk123</dc:creator>
      <dc:date>2018-04-09T12:22:13Z</dc:date>
    </item>
  </channel>
</rss>

