<?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 Re: Sending USB Alerts via syslog (Cortex XDR) in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/sending-usb-alerts-via-syslog-cortex-xdr/m-p/1247866#M9115</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1184632661"&gt;@Y.SONG464633&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is possible to receive email or syslog notifications whenever a USB device is connected to an endpoint, but the configuration you attempted under &lt;STRONG&gt;Management Audit Logs&lt;/STRONG&gt; failed because those logs are designed to track administrative changes (such as an admin modifying a policy), not endpoint security events.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To achieve USB connection notifications, you must create a &lt;STRONG&gt;Correlation Rule&lt;/STRONG&gt; based on an XQL query that detects USB connection events and then configure &lt;STRONG&gt;Notification Forwarding&lt;/STRONG&gt; for those alerts.&lt;/P&gt;
&lt;H4&gt;1. Verify Prerequisites&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;License:&lt;/STRONG&gt; A Cortex XDR &lt;STRONG&gt;Pro&lt;/STRONG&gt; license is required to access the granular endpoint telemetry needed for these queries.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Data Collection:&lt;/STRONG&gt; Ensure that &lt;STRONG&gt;Enhanced Endpoint Data&lt;/STRONG&gt; collection is enabled in your &lt;STRONG&gt;Agent Settings Profile&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H4&gt;2. Configure the XQL Query&lt;/H4&gt;
&lt;P&gt;While monitoring registry keys can work, it is more efficient and reliable to use the dedicated &lt;STRONG&gt;DEVICE&lt;/STRONG&gt; event type or the built-in device control telemetry.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Recommended XQL Query:&lt;/STRONG&gt;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class="language-xql"&gt;dataset = xdr_data
| filter event_type = DEVICE and event_sub_type = DEVICE_PLUG
| fields _time, agent_hostname, actor_effective_username, action_device_usb_vendor_name, action_device_usb_product_name, action_device_usb_serial_number
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;H4&gt;3. Create a Correlation Rule&lt;/H4&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;Navigate to &lt;STRONG&gt;Detection Rules → Correlation Rules → + New Rule&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Paste the recommended query into the &lt;STRONG&gt;XQL Search&lt;/STRONG&gt; section.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Time Schedule:&lt;/STRONG&gt; Configure the rule to run frequently (for example, every 5 or 15 minutes).&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Action:&lt;/STRONG&gt; Select &lt;STRONG&gt;Generate Alert&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Alert Name:&lt;/STRONG&gt; Assign a unique name such as &lt;CODE&gt;USB_Connection_Detected&lt;/CODE&gt;. This is important for notification filtering.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Alert Fields Mapping (Optional):&lt;/STRONG&gt; Map fields such as &lt;CODE&gt;agent_hostname&lt;/CODE&gt; to standard alert fields for improved visibility.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Save and enable the rule.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;4. Configure Notification Forwarding (Email or Syslog)&lt;/H4&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;Navigate to &lt;STRONG&gt;Settings → Configuration → Notifications → Forwarding Configurations&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Click &lt;STRONG&gt;+ Add Forwarding Configuration&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Alert Source:&lt;/STRONG&gt; Select &lt;STRONG&gt;Cortex XDR Analytics &amp;amp; Correlation&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Filtering:&lt;/STRONG&gt; Filter on the &lt;STRONG&gt;Alert Name&lt;/STRONG&gt; created earlier (for example, &lt;CODE&gt;USB_Connection_Detected&lt;/CODE&gt;).&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Target:&lt;/STRONG&gt; Choose &lt;STRONG&gt;Email&lt;/STRONG&gt; or &lt;STRONG&gt;Syslog&lt;/STRONG&gt; (ensure the syslog server is already configured under &lt;STRONG&gt;Settings → Configurations → Integrations → Syslog&lt;/STRONG&gt;).&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Save the configuration.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Why BIOC Did Not Work&lt;/H4&gt;
&lt;P&gt;BIOC (Behavioral Indicators of Compromise) rules are primarily designed for real-time detection and prevention of malicious activity. While they can technically detect USB-related events, &lt;STRONG&gt;Correlation Rules&lt;/STRONG&gt; are better suited for monitoring environmental or operational events such as hardware connections. They allow scheduled searches across historical raw data and provide simpler alerting and notification workflows.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you feel this has answered your query, please let us know by clicking like and on&amp;nbsp;&lt;STRONG&gt;"mark this as a Solution".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;</description>
    <pubDate>Tue, 10 Feb 2026 13:35:20 GMT</pubDate>
    <dc:creator>susekar</dc:creator>
    <dc:date>2026-02-10T13:35:20Z</dc:date>
    <item>
      <title>Sending USB Alerts via syslog (Cortex XDR)</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/sending-usb-alerts-via-syslog-cortex-xdr/m-p/1247681#M9108</link>
      <description>&lt;P data-start="93" data-end="113"&gt;Hello,&lt;/P&gt;
&lt;P data-start="115" data-end="392"&gt;We have received a request asking whether it is possible for administrators to receive alert emails whenever a USB device is connected to any endpoints.&lt;BR data-start="299" data-end="302" /&gt;(*Currently, the USB policy in &lt;STRONG data-start="332" data-end="366"&gt;Exploit – Device Configuration&lt;/STRONG&gt; is set to &lt;STRONG data-start="377" data-end="390"&gt;Read Only&lt;/STRONG&gt;.)&lt;/P&gt;
&lt;P data-start="115" data-end="392"&gt;(* I think the adminster wants to get the log &lt;STRONG&gt;[Inventory-Device Control Violations]&lt;/STRONG&gt;)&lt;/P&gt;
&lt;P data-start="115" data-end="392"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="394" data-end="628"&gt;We attempted to configure this under &lt;STRONG data-start="431" data-end="475"&gt;Settings → Configuration → Notifications&lt;/STRONG&gt; by selecting &lt;STRONG data-start="489" data-end="514"&gt;Management Audit Logs&lt;/STRONG&gt; and setting the &lt;STRONG data-start="531" data-end="539"&gt;Type&lt;/STRONG&gt; to &lt;STRONG data-start="543" data-end="567"&gt;Device Control (All)&lt;/STRONG&gt;. However, the expected alerts were not generated as desired.&lt;/P&gt;
&lt;P data-start="630" data-end="762"&gt;ChatGPT suggested using &lt;STRONG data-start="654" data-end="668"&gt;XQL + BIOC&lt;/STRONG&gt;, but we are still unable to identify the exact XQL query and the correct configuration steps.&lt;/P&gt;
&lt;P data-start="630" data-end="762"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="YSONG464633_0-1770612974843.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/70601iD5B4895EC46C38FA/image-size/medium?v=v2&amp;amp;px=400" role="button" title="YSONG464633_0-1770612974843.png" alt="YSONG464633_0-1770612974843.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P data-start="630" data-end="762"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="86" data-end="166"&gt;We have created the query below; however, we are not sure whether it is correct.&lt;/P&gt;
&lt;P data-start="168" data-end="240"&gt;Could you please review it and let us know if it is properly configured?&lt;/P&gt;
&lt;P data-start="764" data-end="801"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="803" data-end="967"&gt;At present, the alert flow is configured as &lt;STRONG data-start="847" data-end="887"&gt;Issue Alert → Syslog → Administrator&lt;/STRONG&gt;, so it would be sufficient if USB-related alerts could be forwarded via syslog.&lt;/P&gt;
&lt;P data-start="803" data-end="967"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="969" data-end="979"&gt;Thank you.&lt;/P&gt;
&lt;P data-start="969" data-end="979"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="969" data-end="979"&gt;&lt;LI-PRODUCT title="코텍스 XDR" id="Cortex_XDR"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Feb 2026 04:58:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/sending-usb-alerts-via-syslog-cortex-xdr/m-p/1247681#M9108</guid>
      <dc:creator>Y.SONG464633</dc:creator>
      <dc:date>2026-02-09T04:58:03Z</dc:date>
    </item>
    <item>
      <title>Re: Sending USB Alerts via syslog (Cortex XDR)</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/sending-usb-alerts-via-syslog-cortex-xdr/m-p/1247866#M9115</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1184632661"&gt;@Y.SONG464633&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is possible to receive email or syslog notifications whenever a USB device is connected to an endpoint, but the configuration you attempted under &lt;STRONG&gt;Management Audit Logs&lt;/STRONG&gt; failed because those logs are designed to track administrative changes (such as an admin modifying a policy), not endpoint security events.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To achieve USB connection notifications, you must create a &lt;STRONG&gt;Correlation Rule&lt;/STRONG&gt; based on an XQL query that detects USB connection events and then configure &lt;STRONG&gt;Notification Forwarding&lt;/STRONG&gt; for those alerts.&lt;/P&gt;
&lt;H4&gt;1. Verify Prerequisites&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;License:&lt;/STRONG&gt; A Cortex XDR &lt;STRONG&gt;Pro&lt;/STRONG&gt; license is required to access the granular endpoint telemetry needed for these queries.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Data Collection:&lt;/STRONG&gt; Ensure that &lt;STRONG&gt;Enhanced Endpoint Data&lt;/STRONG&gt; collection is enabled in your &lt;STRONG&gt;Agent Settings Profile&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H4&gt;2. Configure the XQL Query&lt;/H4&gt;
&lt;P&gt;While monitoring registry keys can work, it is more efficient and reliable to use the dedicated &lt;STRONG&gt;DEVICE&lt;/STRONG&gt; event type or the built-in device control telemetry.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Recommended XQL Query:&lt;/STRONG&gt;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class="language-xql"&gt;dataset = xdr_data
| filter event_type = DEVICE and event_sub_type = DEVICE_PLUG
| fields _time, agent_hostname, actor_effective_username, action_device_usb_vendor_name, action_device_usb_product_name, action_device_usb_serial_number
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;H4&gt;3. Create a Correlation Rule&lt;/H4&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;Navigate to &lt;STRONG&gt;Detection Rules → Correlation Rules → + New Rule&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Paste the recommended query into the &lt;STRONG&gt;XQL Search&lt;/STRONG&gt; section.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Time Schedule:&lt;/STRONG&gt; Configure the rule to run frequently (for example, every 5 or 15 minutes).&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Action:&lt;/STRONG&gt; Select &lt;STRONG&gt;Generate Alert&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Alert Name:&lt;/STRONG&gt; Assign a unique name such as &lt;CODE&gt;USB_Connection_Detected&lt;/CODE&gt;. This is important for notification filtering.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Alert Fields Mapping (Optional):&lt;/STRONG&gt; Map fields such as &lt;CODE&gt;agent_hostname&lt;/CODE&gt; to standard alert fields for improved visibility.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Save and enable the rule.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;4. Configure Notification Forwarding (Email or Syslog)&lt;/H4&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;Navigate to &lt;STRONG&gt;Settings → Configuration → Notifications → Forwarding Configurations&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Click &lt;STRONG&gt;+ Add Forwarding Configuration&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Alert Source:&lt;/STRONG&gt; Select &lt;STRONG&gt;Cortex XDR Analytics &amp;amp; Correlation&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Filtering:&lt;/STRONG&gt; Filter on the &lt;STRONG&gt;Alert Name&lt;/STRONG&gt; created earlier (for example, &lt;CODE&gt;USB_Connection_Detected&lt;/CODE&gt;).&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Target:&lt;/STRONG&gt; Choose &lt;STRONG&gt;Email&lt;/STRONG&gt; or &lt;STRONG&gt;Syslog&lt;/STRONG&gt; (ensure the syslog server is already configured under &lt;STRONG&gt;Settings → Configurations → Integrations → Syslog&lt;/STRONG&gt;).&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Save the configuration.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Why BIOC Did Not Work&lt;/H4&gt;
&lt;P&gt;BIOC (Behavioral Indicators of Compromise) rules are primarily designed for real-time detection and prevention of malicious activity. While they can technically detect USB-related events, &lt;STRONG&gt;Correlation Rules&lt;/STRONG&gt; are better suited for monitoring environmental or operational events such as hardware connections. They allow scheduled searches across historical raw data and provide simpler alerting and notification workflows.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you feel this has answered your query, please let us know by clicking like and on&amp;nbsp;&lt;STRONG&gt;"mark this as a Solution".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;</description>
      <pubDate>Tue, 10 Feb 2026 13:35:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/sending-usb-alerts-via-syslog-cortex-xdr/m-p/1247866#M9115</guid>
      <dc:creator>susekar</dc:creator>
      <dc:date>2026-02-10T13:35:20Z</dc:date>
    </item>
    <item>
      <title>Re: Sending USB Alerts via syslog (Cortex XDR)</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/sending-usb-alerts-via-syslog-cortex-xdr/m-p/1247906#M9121</link>
      <description>&lt;P&gt;Thank you Veeeeeeeeeeeeeeeeeeeeeeeeeeeeery Much!!&lt;/P&gt;
&lt;P&gt;You save my life! &lt;span class="lia-unicode-emoji" title=":loudly_crying_face:"&gt;😭&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":loudly_crying_face:"&gt;😭&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":loudly_crying_face:"&gt;😭&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":loudly_crying_face:"&gt;😭&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":loudly_crying_face:"&gt;😭&lt;/span&gt;&lt;span class="lia-unicode-emoji" title=":loudly_crying_face:"&gt;😭&lt;/span&gt;&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":face_blowing_a_kiss:"&gt;😘&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2026 02:18:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/sending-usb-alerts-via-syslog-cortex-xdr/m-p/1247906#M9121</guid>
      <dc:creator>Y.SONG464633</dc:creator>
      <dc:date>2026-02-11T02:18:22Z</dc:date>
    </item>
  </channel>
</rss>

