<?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 Egress Internet Traffic from Single Gateway host in Azure blocked via AWS WAF -HostingProviderIPList in Cloud Firewall</title>
    <link>https://community.checkpoint.com/t5/Cloud-Firewall/Egress-Internet-Traffic-from-Single-Gateway-host-in-Azure/m-p/250656#M5367</link>
    <description>&lt;P&gt;Hi There,&lt;BR /&gt;We are an MSP that has a number of clients configured with Azure Hosted Citrix deployments.&amp;nbsp; Egress/Ingress internet traffic is filtered by R82.0 Azure hosted Security Gateway and managed by Smart-1 Cloud Saas Platform.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We are finding random egress traffic is blocked by AWS hosted sites WAF, and i believe this is due to provider utilizing the HostingProviderIPList reputation rules.&amp;nbsp; Additionally we found services like Youtube are now forcing users to sign in when connections are detected from Azure.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We understand we can utilize Azure BYOD PIP service, but from the R&amp;amp;D i have completed it seems the clients need to use /24 PIP as a minimum.&amp;nbsp; Most of the clients aren't large enough to consider this.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;While the issue has nothing to do with Checkpoint NVA, i was hopefully of finding any real-life experience on how others have handled this situation without having to change the entire client egress internet flow.&amp;nbsp; On the surface, configuring the NVA to forward egress traffic to a forward proxy sounds like a viable option, but have been unable to find too much technical info around if such an option exists.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;thanks in advance&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 00:31:46 GMT</pubDate>
    <dc:creator>jfelix</dc:creator>
    <dc:date>2025-06-05T00:31:46Z</dc:date>
    <item>
      <title>Egress Internet Traffic from Single Gateway host in Azure blocked via AWS WAF -HostingProviderIPList</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Egress-Internet-Traffic-from-Single-Gateway-host-in-Azure/m-p/250656#M5367</link>
      <description>&lt;P&gt;Hi There,&lt;BR /&gt;We are an MSP that has a number of clients configured with Azure Hosted Citrix deployments.&amp;nbsp; Egress/Ingress internet traffic is filtered by R82.0 Azure hosted Security Gateway and managed by Smart-1 Cloud Saas Platform.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We are finding random egress traffic is blocked by AWS hosted sites WAF, and i believe this is due to provider utilizing the HostingProviderIPList reputation rules.&amp;nbsp; Additionally we found services like Youtube are now forcing users to sign in when connections are detected from Azure.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We understand we can utilize Azure BYOD PIP service, but from the R&amp;amp;D i have completed it seems the clients need to use /24 PIP as a minimum.&amp;nbsp; Most of the clients aren't large enough to consider this.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;While the issue has nothing to do with Checkpoint NVA, i was hopefully of finding any real-life experience on how others have handled this situation without having to change the entire client egress internet flow.&amp;nbsp; On the surface, configuring the NVA to forward egress traffic to a forward proxy sounds like a viable option, but have been unable to find too much technical info around if such an option exists.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;thanks in advance&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 00:31:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Egress-Internet-Traffic-from-Single-Gateway-host-in-Azure/m-p/250656#M5367</guid>
      <dc:creator>jfelix</dc:creator>
      <dc:date>2025-06-05T00:31:46Z</dc:date>
    </item>
  </channel>
</rss>

