<?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: Reserved IP Address in Cisco Secure Access in Cloud Security</title>
    <link>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344416#M2312</link>
    <description>&lt;P&gt;I don't think that is possible, I think once the dedicated IP is deployed to your organization any web traffic will be sourced from that IP.&lt;/P&gt;</description>
    <pubDate>Tue, 04 Nov 2025 14:35:56 GMT</pubDate>
    <dc:creator>Aref Alsouqi</dc:creator>
    <dc:date>2025-11-04T14:35:56Z</dc:date>
    <item>
      <title>Re: Reserved IP Address in Cisco Secure Access</title>
      <link>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344396#M2311</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;If we purchased a Reserved Egress IP Address in Cisco Secure Internet Access, Is it possible that we route some traffic through reserved IP address some traffic through shared IP address ?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Nov 2025 14:09:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344396#M2311</guid>
      <dc:creator>Edsnow</dc:creator>
      <dc:date>2025-11-04T14:09:16Z</dc:date>
    </item>
    <item>
      <title>Re: Reserved IP Address in Cisco Secure Access</title>
      <link>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344416#M2312</link>
      <description>&lt;P&gt;I don't think that is possible, I think once the dedicated IP is deployed to your organization any web traffic will be sourced from that IP.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Nov 2025 14:35:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344416#M2312</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-11-04T14:35:56Z</dc:date>
    </item>
    <item>
      <title>Re: Reserved IP Address in Cisco Secure Access</title>
      <link>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344489#M2313</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1031287"&gt;@Edsnow&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I agree with Aref. The Reserved IP is associated with a specific Secure Access Region (geographic data center location) of Cisco's cloud SSE services&lt;/P&gt;&lt;P&gt;Any traffic that reaches or traverses through that Secure Access Region will use the Reserved IP assigned to the region. If your web traffic passes through a region where you haven’t provisioned a Reserved IP, it will instead use the shared IP range for that region. The choice of which Secure Access Region to use as ingress is dependent on your deployment method, e.g. Cisco Secure Access client vs branch IPSec Network Tunnel.&lt;/P&gt;&lt;P&gt;Attempting to perform traffic engineering&amp;nbsp;to selectively route traffic through either the Reserved IP or the Shared IP based on the destination IP address/domain is not supported&lt;/P&gt;&lt;P&gt;The documentation below may be of use if you've not seen it already! See 'Reserved IP' and 'Secure NAT as a Service'&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.sse.cisco.com/" target="_blank" rel="noopener"&gt;https://docs.sse.cisco.com/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Nov 2025 19:54:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344489#M2313</guid>
      <dc:creator>Royalty</dc:creator>
      <dc:date>2025-11-04T19:54:21Z</dc:date>
    </item>
    <item>
      <title>Re: Reserved IP Address in Cisco Secure Access</title>
      <link>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344554#M2314</link>
      <description>&lt;P&gt;This is not supported today but we are looking to develop this functionality. What's your use-case for doing so?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 02:55:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344554#M2314</guid>
      <dc:creator>adamwin</dc:creator>
      <dc:date>2025-11-05T02:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: Reserved IP Address in Cisco Secure Access</title>
      <link>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344563#M2315</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/182243"&gt;@adamwin&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;There is no use case as of now. but I am bit confused when I filter the logs in my console as shared IP address, I am seeing some of the windows update traffic is egressing with Shared IP Addresses. Any thoughts on this?&lt;/P&gt;&lt;P&gt;As more details The traffic egressing from Mumbai DC in India.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 04:00:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344563#M2315</guid>
      <dc:creator>Edsnow</dc:creator>
      <dc:date>2025-11-05T04:00:57Z</dc:date>
    </item>
    <item>
      <title>Re: Reserved IP Address in Cisco Secure Access</title>
      <link>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344567#M2316</link>
      <description>&lt;P&gt;Reserved IP is not enabled on Microsoft update and some Cisco destinations. This is by-design.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 04:27:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344567#M2316</guid>
      <dc:creator>adamwin</dc:creator>
      <dc:date>2025-11-05T04:27:01Z</dc:date>
    </item>
    <item>
      <title>Re: Reserved IP Address in Cisco Secure Access</title>
      <link>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344589#M2317</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/182243"&gt;@adamwin&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Any cisco Doc for which all are the excluded domains for Reserved IP address?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 06:30:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344589#M2317</guid>
      <dc:creator>Edsnow</dc:creator>
      <dc:date>2025-11-05T06:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: Reserved IP Address in Cisco Secure Access</title>
      <link>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344775#M2318</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1031287"&gt;@Edsnow&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;There is no public document with all of the excluded domains. In general, see below for information on the traffic that is excluded from using the Reserved IP address.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Secure Access excludes Microsoft Update traffic on the organization's reserved IP.&lt;/LI&gt;&lt;LI&gt;Secure Access does not provide the reserved IP for web sites that load over QUIC&lt;/LI&gt;&lt;LI&gt;Secure Access only supports reserved IP for traffic using SWG.&lt;/LI&gt;&lt;LI&gt;Reserved IP is available only for IPv4&lt;/LI&gt;&lt;LI&gt;Remote Browser Isolation (RBI) is not supported by Reserved IP. Applications or services that require a reserved IP address should not use remote browser isolation as they will egress on the Shared IP range.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 05 Nov 2025 15:58:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5344775#M2318</guid>
      <dc:creator>Royalty</dc:creator>
      <dc:date>2025-11-05T15:58:23Z</dc:date>
    </item>
    <item>
      <title>Re: Reserved IP Address in Cisco Secure Access</title>
      <link>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5347412#M2319</link>
      <description>&lt;P&gt;There are some restrictions on Reserved IP address, which you can refer to here.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://securitydocs.cisco.com/docs/csa/olh/121292.dita" target="_blank"&gt;https://securitydocs.cisco.com/docs/csa/olh/121292.dita&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://securitydocs.cisco.com/docs/csa/olh/121296.dita" target="_blank"&gt;https://securitydocs.cisco.com/docs/csa/olh/121296.dita&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://securitydocs.cisco.com/docs/csa/olh/121306.dita" target="_blank"&gt;https://securitydocs.cisco.com/docs/csa/olh/121306.dita&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 16 Nov 2025 15:16:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-security/re-reserved-ip-address-in-cisco-secure-access/m-p/5347412#M2319</guid>
      <dc:creator>msyk.oym</dc:creator>
      <dc:date>2025-11-16T15:16:25Z</dc:date>
    </item>
  </channel>
</rss>

