<?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 Cortex XDR Windows Event Collector in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-windows-event-collector/m-p/404409#M706</link>
    <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;My question is about Windows Event Collector.&lt;/P&gt;&lt;P&gt;Why we need Windows Event Collector? Don't XDR Agents collects all needed information from Windows endpoints? Can Windows Event Collector give us useful information than Agents?&lt;/P&gt;</description>
    <pubDate>Sun, 02 May 2021 08:21:34 GMT</pubDate>
    <dc:creator>OrkanAlibayli</dc:creator>
    <dc:date>2021-05-02T08:21:34Z</dc:date>
    <item>
      <title>Cortex XDR Windows Event Collector</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-windows-event-collector/m-p/404409#M706</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;My question is about Windows Event Collector.&lt;/P&gt;&lt;P&gt;Why we need Windows Event Collector? Don't XDR Agents collects all needed information from Windows endpoints? Can Windows Event Collector give us useful information than Agents?&lt;/P&gt;</description>
      <pubDate>Sun, 02 May 2021 08:21:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-windows-event-collector/m-p/404409#M706</guid>
      <dc:creator>OrkanAlibayli</dc:creator>
      <dc:date>2021-05-02T08:21:34Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XDR Windows Event Collector</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-windows-event-collector/m-p/405376#M715</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/175794"&gt;@OrkanAlibayli&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;My question is about Windows Event Collector.&lt;/P&gt;&lt;P&gt;Why we need Windows Event Collector? Don't XDR Agents collects all needed information from Windows endpoints? Can Windows Event Collector give us useful information than Agents?&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/175794"&gt;@OrkanAlibayli&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Windows Even Collector is used to collect Windows event logs on servers when the Cortex XDR agent would not do so. There are only a &lt;A href="https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-prevent-admin/endpoint-security/customizable-agent-settings/endpoint-data-collected-by-cortex-xdr.html#id369a9a8f-1b0e-47df-8afb-d305bf2f504f_windows-event-logs" target="_self"&gt;select number of Windows event logs collected by the Cortex XDR Agent&lt;/A&gt;, and those are critical as evidence for the malicious behaviors being reported by the agent. The Windows Event Collector can augment that that selection of event logs as a Cortex XDR administrator can specify the log IDs that should be shipped to the Cortex Data Lake (&lt;A href="https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-pro-admin/broker-vm/set-up-broker-vm/activate-the-windows-event-collector.html" target="_self"&gt;See the Windows Event Collector Document for more information&lt;/A&gt;.) Those logs may not necessarily deal with malicious behaviors, but they are interesting enough that a Cortex XDR user may want them brought in.&lt;/P&gt;</description>
      <pubDate>Thu, 06 May 2021 23:08:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-windows-event-collector/m-p/405376#M715</guid>
      <dc:creator>gjenkins</dc:creator>
      <dc:date>2021-05-06T23:08:19Z</dc:date>
    </item>
  </channel>
</rss>

