<?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>article Network prerequisites for Privilege Cloud Connector Deployment in PAM SaaS Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-saas-articles/network-prerequisites-for-privilege-cloud-connector-deployment/ta-p/1429940</link>
    <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;P&gt;&amp;nbsp;1.&amp;nbsp; Is allowing static FQDN (&lt;A href="https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound-traffic-static.htm" rel="noopener noreferrer" target="_blank"&gt;https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound-traffic-static.htm&lt;/A&gt;"&amp;nbsp; the best approach or do&amp;nbsp; we still need to work on allowing the Wildcard domains as mentioned in the link "Outbound Traffic &amp;amp;&lt;BR /&gt;Port Requirements".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2.&amp;nbsp; &amp;nbsp;Idira documentation (&lt;A href="https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound_traffic.htm#Dynamiccommunicationconfiguration" rel="noopener noreferrer" target="_blank"&gt;https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound_traffic.htm#Dynamiccommunicationconfiguration&lt;/A&gt;)&amp;nbsp; mentions to open *.&lt;A href="https://idap.co/" rel="noopener noreferrer" target="_blank"&gt;idap.co&lt;/A&gt;&amp;nbsp; but there is no specific endpoint on this domain in the Static FQDN doc link mentioned above neither in the attached network requirement file attached to this case.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Can we ignore *.&lt;A href="https://idap.co/" rel="noopener noreferrer" target="_blank"&gt;idap.co&lt;/A&gt;&amp;nbsp; considering if we allow only the static FQDN's?&lt;/P&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;1. We strongly recommend Dynamic Configuration using Wildcard domains. While static configuration is supported as a secondary fallback, wildcard domain allow listing is the preferred architectural pattern for SaaS deployments.&lt;/P&gt;
&lt;P&gt;Relying strictly on static FQDNs carries a high risk of future service disruption.&lt;BR /&gt;&lt;BR /&gt;Here is why:&lt;BR /&gt;&lt;BR /&gt;Elastic SaaS Architecture: Idira SaaS continually updates, scales microservices, and adds new storage endpoints (S3 buckets, CloudFront distributions). Hardcoded static lists require manual updating whenever underlying infrastructure scales.&lt;BR /&gt;&lt;BR /&gt;AWS IoT Core Cross-Region Routing: Services such as Connector Management and Session Interactive Agents (SIA) rely on AWS IoT Core brokers for real-time channels.&amp;nbsp; Even if a tenant primary region is us-east-1, AWS IoT brokers utilize multi-region fallback mechanisms (e.g., routing traffic to us-west-2 or global endpoints during high traffic or failover scenarios). A rigid static list generated at a single point in time will block these secondary endpoints during routing shifts.&lt;BR /&gt;&lt;BR /&gt;2. You do not need to allow *.idap.co for a static configuration. The official connector prerequisite script polls the Idira backend APIs and dynamically outputs the exact requirements for your specific tenant.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 05 Nov 2026 19:44:18 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-11-05T19:44:18Z</dc:date>
    <item>
      <title>Network prerequisites for Privilege Cloud Connector Deployment</title>
      <link>https://live.paloaltonetworks.com/t5/pam-saas-articles/network-prerequisites-for-privilege-cloud-connector-deployment/ta-p/1429940</link>
      <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;P&gt;&amp;nbsp;1.&amp;nbsp; Is allowing static FQDN (&lt;A href="https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound-traffic-static.htm" rel="noopener noreferrer" target="_blank"&gt;https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound-traffic-static.htm&lt;/A&gt;"&amp;nbsp; the best approach or do&amp;nbsp; we still need to work on allowing the Wildcard domains as mentioned in the link "Outbound Traffic &amp;amp;&lt;BR /&gt;Port Requirements".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2.&amp;nbsp; &amp;nbsp;Idira documentation (&lt;A href="https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound_traffic.htm#Dynamiccommunicationconfiguration" rel="noopener noreferrer" target="_blank"&gt;https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound_traffic.htm#Dynamiccommunicationconfiguration&lt;/A&gt;)&amp;nbsp; mentions to open *.&lt;A href="https://idap.co/" rel="noopener noreferrer" target="_blank"&gt;idap.co&lt;/A&gt;&amp;nbsp; but there is no specific endpoint on this domain in the Static FQDN doc link mentioned above neither in the attached network requirement file attached to this case.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Can we ignore *.&lt;A href="https://idap.co/" rel="noopener noreferrer" target="_blank"&gt;idap.co&lt;/A&gt;&amp;nbsp; considering if we allow only the static FQDN's?&lt;/P&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;1. We strongly recommend Dynamic Configuration using Wildcard domains. While static configuration is supported as a secondary fallback, wildcard domain allow listing is the preferred architectural pattern for SaaS deployments.&lt;/P&gt;
&lt;P&gt;Relying strictly on static FQDNs carries a high risk of future service disruption.&lt;BR /&gt;&lt;BR /&gt;Here is why:&lt;BR /&gt;&lt;BR /&gt;Elastic SaaS Architecture: Idira SaaS continually updates, scales microservices, and adds new storage endpoints (S3 buckets, CloudFront distributions). Hardcoded static lists require manual updating whenever underlying infrastructure scales.&lt;BR /&gt;&lt;BR /&gt;AWS IoT Core Cross-Region Routing: Services such as Connector Management and Session Interactive Agents (SIA) rely on AWS IoT Core brokers for real-time channels.&amp;nbsp; Even if a tenant primary region is us-east-1, AWS IoT brokers utilize multi-region fallback mechanisms (e.g., routing traffic to us-west-2 or global endpoints during high traffic or failover scenarios). A rigid static list generated at a single point in time will block these secondary endpoints during routing shifts.&lt;BR /&gt;&lt;BR /&gt;2. You do not need to allow *.idap.co for a static configuration. The official connector prerequisite script polls the Idira backend APIs and dynamically outputs the exact requirements for your specific tenant.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2026 19:44:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-saas-articles/network-prerequisites-for-privilege-cloud-connector-deployment/ta-p/1429940</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-11-05T19:44:18Z</dc:date>
    </item>
  </channel>
</rss>

