<!--
  Collect the Sysmon operational channel.
  Goes inside the <ossec_config> element of
  C:\Program Files (x86)\ossec-agent\ossec.conf.

  Insert it before the LAST </ossec_config>, not at the end of the file: the
  default Windows configuration ends with a trailing XML comment reading
  "END of Default Configuration", so a script anchored on </ossec_config> as
  the last line of the file matches nothing and appends nothing.
  Restart with: Restart-Service WazuhSvc
  Then confirm in ossec.log:
  (1951): Analyzing event log: 'Microsoft-Windows-Sysmon/Operational'.

  Reference:
  https://documentation.wazuh.com/5.0-beta/user-manual/capabilities/log-data-collection/use-cases.html
-->
<localfile>
  <location>Microsoft-Windows-Sysmon/Operational</location>
  <log_format>eventchannel</log_format>
</localfile>

<!--
  Optional: narrow the channel with an XPath query when the Sysmon
  configuration is broader than what you want to ship. Filter in the Sysmon
  configuration first; this is the second line of defence, not the first.
  ignore and restrict do not apply to eventchannel.

  <localfile>
    <location>Microsoft-Windows-Sysmon/Operational</location>
    <log_format>eventchannel</log_format>
    <query>Event/System[EventID = 1 or EventID = 3 or EventID = 7 or EventID = 8 or EventID = 10 or EventID = 11 or EventID = 12 or EventID = 13 or EventID = 22 or EventID = 23 or EventID = 25]</query>
    <reconnect_time>10s</reconnect_time>
  </localfile>
-->
