<?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 XSIAM broker vm in Cortex XSIAM Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/cortex-xsiam-broker-vm/m-p/1258521#M446</link>
    <description>&lt;P&gt;Our Cortex XSIAM agents connect to the XSIAM server exclusively via the Broker VM's local agent proxy settings applet, as direct outbound internet/server access is blocked for these endpoints. If we want our agents to auto-upgrade, do we absolutely have to enable and configure the 'Agent Installer and content caching' part of the applet on the Broker VM? Or can the agents just utilize the existing proxy connection to fetch the upgrade installer directly from the XSIAM cloud server on their own? We understand that passing the installer through the proxy without caching will consume more cloud-to-local bandwidth, but given our low endpoint count, we want to know if auto-upgrades are functionally supported this way. Additionally, what is the maximum recommended number of agents for this type of deployment?&lt;/P&gt;</description>
    <pubDate>Wed, 08 Jul 2026 18:02:58 GMT</pubDate>
    <dc:creator>bridgetlitt</dc:creator>
    <dc:date>2026-07-08T18:02:58Z</dc:date>
    <item>
      <title>Cortex XSIAM broker vm</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/cortex-xsiam-broker-vm/m-p/1258521#M446</link>
      <description>&lt;P&gt;Our Cortex XSIAM agents connect to the XSIAM server exclusively via the Broker VM's local agent proxy settings applet, as direct outbound internet/server access is blocked for these endpoints. If we want our agents to auto-upgrade, do we absolutely have to enable and configure the 'Agent Installer and content caching' part of the applet on the Broker VM? Or can the agents just utilize the existing proxy connection to fetch the upgrade installer directly from the XSIAM cloud server on their own? We understand that passing the installer through the proxy without caching will consume more cloud-to-local bandwidth, but given our low endpoint count, we want to know if auto-upgrades are functionally supported this way. Additionally, what is the maximum recommended number of agents for this type of deployment?&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jul 2026 18:02:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/cortex-xsiam-broker-vm/m-p/1258521#M446</guid>
      <dc:creator>bridgetlitt</dc:creator>
      <dc:date>2026-07-08T18:02:58Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XSIAM broker vm</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/cortex-xsiam-broker-vm/m-p/1258553#M447</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/710084109"&gt;@bridgetlitt&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The &lt;STRONG&gt;Agent Installer and Content Caching&lt;/STRONG&gt; feature is &lt;STRONG&gt;not required&lt;/STRONG&gt; for Cortex XSIAM agent auto-upgrades. Its primary purpose is to optimize bandwidth by caching agent installers and content updates on the Broker VM.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If only the &lt;STRONG&gt;Local Agent Proxy&lt;/STRONG&gt; is configured, and the endpoints communicate with the Cortex XSIAM cloud exclusively through the Broker VM (with no direct Internet access), the agents can still automatically download and install upgrades through the proxy. In this scenario, the Broker VM simply forwards the traffic between the agents and the Cortex XSIAM cloud. The only trade-off is that each endpoint downloads the installer individually, which increases WAN bandwidth usage during upgrade deployments.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The &lt;STRONG&gt;Agent Installer and Content Caching&lt;/STRONG&gt; feature is recommended for larger environments because it reduces bandwidth consumption and accelerates mass deployments, but it is not a functional requirement for automatic agent upgrades.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regarding scalability, a Broker VM configured for &lt;STRONG&gt;Agent Proxy&lt;/STRONG&gt; can support up to &lt;STRONG&gt;50,000 agents&lt;/STRONG&gt; on newer Broker VM deployments (or &lt;STRONG&gt;28,000 agents&lt;/STRONG&gt; on older deployments), while &lt;STRONG&gt;Agent Installer and Content Caching&lt;/STRONG&gt; supports up to &lt;STRONG&gt;10,000 agents&lt;/STRONG&gt; per Broker VM when the required hardware specifications are met.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Therefore, for a smaller deployment with a limited number of endpoints, using only the Local Agent Proxy without enabling Agent Installer and Content Caching is a supported and practical deployment model.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;Vinothkumar.C.&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 09 Jul 2026 06:33:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/cortex-xsiam-broker-vm/m-p/1258553#M447</guid>
      <dc:creator>Vinothkumar_SBA</dc:creator>
      <dc:date>2026-07-09T06:33:26Z</dc:date>
    </item>
  </channel>
</rss>

