<?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: XQL - Hostfirewall events in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xql-hostfirewall-events/m-p/1253466#M9304</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1561359921"&gt;@J.Gammara&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;DIV class="relative basis-auto flex-col -mb-(--composer-overlap-px) pb-(--composer-overlap-px) [--composer-overlap-px:28px] grow flex"&gt;
&lt;DIV class="flex flex-col text-sm"&gt;
&lt;SECTION class="text-token-text-primary w-full focus:outline-none [--shadow-height:45px] has-data-writing-block:pointer-events-none has-data-writing-block:-mt-(--shadow-height) has-data-writing-block:pt-(--shadow-height) [&amp;amp;:has([data-writing-block])&amp;gt;*]:pointer-events-auto [content-visibility:auto] supports-[content-visibility:auto]:[contain-intrinsic-size:auto_100lvh] R6Vx5W_threadScrollVars scroll-mb-[calc(var(--scroll-root-safe-area-inset-bottom,0px)+var(--thread-response-height))] scroll-mt-[calc(var(--header-height)+min(200px,max(70px,20svh)))]" dir="auto" data-turn="assistant" data-scroll-anchor="false" data-testid="conversation-turn-2" data-turn-id="request-WEB:1bca8f7b-5d3b-4d1b-9f45-e577caf4b9b6-0"&gt;
&lt;DIV class="text-base my-auto mx-auto pb-10 [--thread-content-margin:var(--thread-content-margin-xs,calc(var(--spacing)*4))] @w-sm/main:[--thread-content-margin:var(--thread-content-margin-sm,calc(var(--spacing)*6))] @w-lg/main:[--thread-content-margin:var(--thread-content-margin-lg,calc(var(--spacing)*16))] px-(--thread-content-margin)"&gt;
&lt;DIV class="[--thread-content-max-width:40rem] @w-lg/main:[--thread-content-max-width:48rem] mx-auto max-w-(--thread-content-max-width) flex-1 group/turn-messages focus-visible:outline-hidden relative flex w-full min-w-0 flex-col agent-turn"&gt;
&lt;DIV class="flex max-w-full flex-col gap-4 grow"&gt;
&lt;DIV class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal outline-none keyboard-focused:focus-ring [.text-message+&amp;amp;]:mt-1" dir="auto" tabindex="0" data-turn-start-message="true" data-message-model-slug="gpt-5-3" data-message-id="3714b27e-9b00-4cb9-99de-af4091cac3b9" data-message-author-role="assistant"&gt;
&lt;DIV class="flex w-full flex-col gap-1 empty:hidden"&gt;
&lt;DIV class="markdown prose dark:prose-invert w-full wrap-break-word light markdown-new-styling"&gt;
&lt;P data-end="375" data-start="0"&gt;To review and correlate network traffic with Host Firewall events efficiently in Cortex XDR, you should utilize a combination of dedicated datasets and optimized XQL join stages.&lt;/P&gt;
&lt;P data-end="375" data-start="0"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="375" data-start="0"&gt;The optimal approach involves querying the &lt;CODE data-end="244" data-start="222"&gt;host_firewall_events&lt;/CODE&gt; dataset for firewall-specific enforcement and joining it with normalized network presets to gain process and connectivity context.&lt;/P&gt;
&lt;P data-end="375" data-start="0"&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4 data-end="413" data-start="377" data-section-id="195wcm3"&gt;1. Identify the Correct Datasets:&lt;/H4&gt;
&lt;UL data-end="837" data-start="414"&gt;
&lt;LI data-end="574" data-start="414" data-section-id="1efxxmn"&gt;&lt;STRONG data-end="441" data-start="416"&gt;Host Firewall Events:&lt;/STRONG&gt; Enforcement actions (Allow/Block) taken by the agent's firewall module are stored in the dedicated &lt;CODE data-end="563" data-start="541"&gt;host_firewall_events&lt;/CODE&gt; dataset.&lt;/LI&gt;
&lt;LI data-end="837" data-start="575" data-section-id="1jw7skf"&gt;&lt;STRONG data-end="597" data-start="577"&gt;Network Traffic:&lt;/STRONG&gt; General network activity is best reviewed using the &lt;CODE data-end="665" data-start="650"&gt;network_story&lt;/CODE&gt; (Network Connections) preset, which contains stitched logs combining events from various sources. Alternatively, raw agent network events reside in the &lt;CODE data-end="828" data-start="818"&gt;xdr_data&lt;/CODE&gt; dataset.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H4 data-end="871" data-start="839" data-section-id="1wl8sif"&gt;Sample XQL Correlation Query:&lt;/H4&gt;
&lt;P data-end="1028" data-start="872"&gt;The following query correlates blocked Host Firewall events with network connectivity data to identify which processes were involved in the blocked traffic:&lt;/P&gt;
&lt;DIV class="relative w-full mt-4 mb-1"&gt;
&lt;DIV class=""&gt;
&lt;DIV class="relative"&gt;
&lt;DIV class="h-full min-h-0 min-w-0"&gt;
&lt;DIV class="h-full min-h-0 min-w-0"&gt;
&lt;DIV class="border border-token-border-light border-radius-3xl corner-superellipse/1.1 rounded-3xl"&gt;
&lt;DIV class="h-full w-full border-radius-3xl bg-token-bg-elevated-secondary corner-superellipse/1.1 overflow-clip rounded-3xl lxnfua_clipPathFallback"&gt;
&lt;DIV class="pointer-events-none absolute end-1.5 top-1 z-2 md:end-2 md:top-1"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="relative"&gt;
&lt;DIV class="pe-11 pt-3"&gt;
&lt;DIV class="relative z-0 flex max-w-full"&gt;
&lt;DIV id="code-block-viewer" class="q9tKkq_viewer cm-editor z-10 light:cm-light dark:cm-light flex h-full w-full flex-col items-stretch ͼd ͼr" dir="ltr"&gt;
&lt;DIV class="cm-scroller"&gt;
&lt;PRE class="cm-content q9tKkq_readonly m-0"&gt;&lt;CODE&gt;&lt;SPAN&gt;dataset = host_firewall_events &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;| filter action = 2 // Filter for Blocked events&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;| fields _time, agent_hostname, action_local_ip, action_remote_ip, action_remote_port, action_process_image_path, actor_process_instance_id, agent_id&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;| join (&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    preset = network_story &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    | fields agent_hostname, actor_process_instance_id, action_app_id_transitions, action_external_hostname&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;) as net network.agent_hostname = agent_hostname and network.actor_process_instance_id = actor_process_instance_id&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;| fields _time, agent_hostname, action_process_image_path, action_local_ip, action_remote_ip, action_remote_port, net.action_app_id_transitions, net.action_external_hostname&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/SECTION&gt;
&lt;/DIV&gt;
&lt;/DIV&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&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;like&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and on&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;"mark this as a Solution".&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 05 May 2026 13:38:41 GMT</pubDate>
    <dc:creator>susekar</dc:creator>
    <dc:date>2026-05-05T13:38:41Z</dc:date>
    <item>
      <title>XQL - Hostfirewall events</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xql-hostfirewall-events/m-p/1253448#M9299</link>
      <description>&lt;P data-path-to-node="6"&gt;Hi everyone,&lt;/P&gt;
&lt;P data-path-to-node="7"&gt;What is the best and most efficient way to review network traffic and correlate or compare it with Host Firewall events using XQL?&lt;/P&gt;
&lt;P data-path-to-node="8"&gt;I am looking for the optimal approach to query and analyze this data together without impacting performance. If anyone has a sample XQL query or advice on how you handle this in your SOC, I would really appreciate it.&lt;/P&gt;
&lt;P data-path-to-node="9"&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Mon, 04 May 2026 16:46:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xql-hostfirewall-events/m-p/1253448#M9299</guid>
      <dc:creator>J.Gammara</dc:creator>
      <dc:date>2026-05-04T16:46:48Z</dc:date>
    </item>
    <item>
      <title>Re: XQL - Hostfirewall events</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xql-hostfirewall-events/m-p/1253466#M9304</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1561359921"&gt;@J.Gammara&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;DIV class="relative basis-auto flex-col -mb-(--composer-overlap-px) pb-(--composer-overlap-px) [--composer-overlap-px:28px] grow flex"&gt;
&lt;DIV class="flex flex-col text-sm"&gt;
&lt;SECTION class="text-token-text-primary w-full focus:outline-none [--shadow-height:45px] has-data-writing-block:pointer-events-none has-data-writing-block:-mt-(--shadow-height) has-data-writing-block:pt-(--shadow-height) [&amp;amp;:has([data-writing-block])&amp;gt;*]:pointer-events-auto [content-visibility:auto] supports-[content-visibility:auto]:[contain-intrinsic-size:auto_100lvh] R6Vx5W_threadScrollVars scroll-mb-[calc(var(--scroll-root-safe-area-inset-bottom,0px)+var(--thread-response-height))] scroll-mt-[calc(var(--header-height)+min(200px,max(70px,20svh)))]" dir="auto" data-turn="assistant" data-scroll-anchor="false" data-testid="conversation-turn-2" data-turn-id="request-WEB:1bca8f7b-5d3b-4d1b-9f45-e577caf4b9b6-0"&gt;
&lt;DIV class="text-base my-auto mx-auto pb-10 [--thread-content-margin:var(--thread-content-margin-xs,calc(var(--spacing)*4))] @w-sm/main:[--thread-content-margin:var(--thread-content-margin-sm,calc(var(--spacing)*6))] @w-lg/main:[--thread-content-margin:var(--thread-content-margin-lg,calc(var(--spacing)*16))] px-(--thread-content-margin)"&gt;
&lt;DIV class="[--thread-content-max-width:40rem] @w-lg/main:[--thread-content-max-width:48rem] mx-auto max-w-(--thread-content-max-width) flex-1 group/turn-messages focus-visible:outline-hidden relative flex w-full min-w-0 flex-col agent-turn"&gt;
&lt;DIV class="flex max-w-full flex-col gap-4 grow"&gt;
&lt;DIV class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal outline-none keyboard-focused:focus-ring [.text-message+&amp;amp;]:mt-1" dir="auto" tabindex="0" data-turn-start-message="true" data-message-model-slug="gpt-5-3" data-message-id="3714b27e-9b00-4cb9-99de-af4091cac3b9" data-message-author-role="assistant"&gt;
&lt;DIV class="flex w-full flex-col gap-1 empty:hidden"&gt;
&lt;DIV class="markdown prose dark:prose-invert w-full wrap-break-word light markdown-new-styling"&gt;
&lt;P data-end="375" data-start="0"&gt;To review and correlate network traffic with Host Firewall events efficiently in Cortex XDR, you should utilize a combination of dedicated datasets and optimized XQL join stages.&lt;/P&gt;
&lt;P data-end="375" data-start="0"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="375" data-start="0"&gt;The optimal approach involves querying the &lt;CODE data-end="244" data-start="222"&gt;host_firewall_events&lt;/CODE&gt; dataset for firewall-specific enforcement and joining it with normalized network presets to gain process and connectivity context.&lt;/P&gt;
&lt;P data-end="375" data-start="0"&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4 data-end="413" data-start="377" data-section-id="195wcm3"&gt;1. Identify the Correct Datasets:&lt;/H4&gt;
&lt;UL data-end="837" data-start="414"&gt;
&lt;LI data-end="574" data-start="414" data-section-id="1efxxmn"&gt;&lt;STRONG data-end="441" data-start="416"&gt;Host Firewall Events:&lt;/STRONG&gt; Enforcement actions (Allow/Block) taken by the agent's firewall module are stored in the dedicated &lt;CODE data-end="563" data-start="541"&gt;host_firewall_events&lt;/CODE&gt; dataset.&lt;/LI&gt;
&lt;LI data-end="837" data-start="575" data-section-id="1jw7skf"&gt;&lt;STRONG data-end="597" data-start="577"&gt;Network Traffic:&lt;/STRONG&gt; General network activity is best reviewed using the &lt;CODE data-end="665" data-start="650"&gt;network_story&lt;/CODE&gt; (Network Connections) preset, which contains stitched logs combining events from various sources. Alternatively, raw agent network events reside in the &lt;CODE data-end="828" data-start="818"&gt;xdr_data&lt;/CODE&gt; dataset.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H4 data-end="871" data-start="839" data-section-id="1wl8sif"&gt;Sample XQL Correlation Query:&lt;/H4&gt;
&lt;P data-end="1028" data-start="872"&gt;The following query correlates blocked Host Firewall events with network connectivity data to identify which processes were involved in the blocked traffic:&lt;/P&gt;
&lt;DIV class="relative w-full mt-4 mb-1"&gt;
&lt;DIV class=""&gt;
&lt;DIV class="relative"&gt;
&lt;DIV class="h-full min-h-0 min-w-0"&gt;
&lt;DIV class="h-full min-h-0 min-w-0"&gt;
&lt;DIV class="border border-token-border-light border-radius-3xl corner-superellipse/1.1 rounded-3xl"&gt;
&lt;DIV class="h-full w-full border-radius-3xl bg-token-bg-elevated-secondary corner-superellipse/1.1 overflow-clip rounded-3xl lxnfua_clipPathFallback"&gt;
&lt;DIV class="pointer-events-none absolute end-1.5 top-1 z-2 md:end-2 md:top-1"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="relative"&gt;
&lt;DIV class="pe-11 pt-3"&gt;
&lt;DIV class="relative z-0 flex max-w-full"&gt;
&lt;DIV id="code-block-viewer" class="q9tKkq_viewer cm-editor z-10 light:cm-light dark:cm-light flex h-full w-full flex-col items-stretch ͼd ͼr" dir="ltr"&gt;
&lt;DIV class="cm-scroller"&gt;
&lt;PRE class="cm-content q9tKkq_readonly m-0"&gt;&lt;CODE&gt;&lt;SPAN&gt;dataset = host_firewall_events &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;| filter action = 2 // Filter for Blocked events&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;| fields _time, agent_hostname, action_local_ip, action_remote_ip, action_remote_port, action_process_image_path, actor_process_instance_id, agent_id&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;| join (&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    preset = network_story &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    | fields agent_hostname, actor_process_instance_id, action_app_id_transitions, action_external_hostname&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;) as net network.agent_hostname = agent_hostname and network.actor_process_instance_id = actor_process_instance_id&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;| fields _time, agent_hostname, action_process_image_path, action_local_ip, action_remote_ip, action_remote_port, net.action_app_id_transitions, net.action_external_hostname&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/SECTION&gt;
&lt;/DIV&gt;
&lt;/DIV&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&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;like&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and on&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;"mark this as a Solution".&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 05 May 2026 13:38:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xql-hostfirewall-events/m-p/1253466#M9304</guid>
      <dc:creator>susekar</dc:creator>
      <dc:date>2026-05-05T13:38:41Z</dc:date>
    </item>
  </channel>
</rss>

