<?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: Force one-way inspection in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Force-one-way-inspection/m-p/245537#M40985</link>
    <description>&lt;P&gt;For UDP it's easy, you can turn off 'accept replies for unknown UDP' and make sure 'accept replies' is not enabled on the custom UDP service object.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Normal inbound connections are already blocked simply by not putting a rule in to allow them.&lt;/P&gt;
&lt;P&gt;Using an open outbound HTTPS connection to prevent data transfer inbound I don't know that we can, we have to accept reply packets for the session to establish else you won't get anything. In order to be able understand the nature of the HTTPS stream once the session is up, we'd have to decrypt it so that we can see what's going on in there, which may already break things due to cert stuff etc. At a basic layer 3/4 level I don't know that anything could accomplish what you're asking for.&lt;/P&gt;
&lt;P&gt;We need to better understand the connections that are established and in what direction to be able to properly determine the course of action here.&lt;/P&gt;</description>
    <pubDate>Thu, 03 Apr 2025 02:10:59 GMT</pubDate>
    <dc:creator>emmap</dc:creator>
    <dc:date>2025-04-03T02:10:59Z</dc:date>
    <item>
      <title>Force one-way inspection</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Force-one-way-inspection/m-p/245527#M40980</link>
      <description>&lt;P&gt;Experts,&lt;/P&gt;&lt;P&gt;Is it possible to force a security gateway to behave like a Cisco ASA firewall for a limited use case and only allow traffic one way? For example,&amp;nbsp;&lt;SPAN&gt;opening up https and another non-standard port outbound from a DMZ at one location and this system talks outbound to a cloud service for monitoring. There are capabilities of the system to connect inbound from the cloud service but we only want the system in the DMZ to connect outbound to transfer data. No inbound even if it's a reverse tunnel from an existing https outbound connection.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 21:32:06 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Force-one-way-inspection/m-p/245527#M40980</guid>
      <dc:creator>CPArk</dc:creator>
      <dc:date>2025-04-02T21:32:06Z</dc:date>
    </item>
    <item>
      <title>Re: Force one-way inspection</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Force-one-way-inspection/m-p/245530#M40982</link>
      <description>&lt;P&gt;Let me take a "crack" at this, though there are way smarter people on here than myself, so Im sure they will give you correct answer.&lt;/P&gt;
&lt;P&gt;Some ways I can think of doing what you asked:&lt;/P&gt;
&lt;P&gt;-define rules to allow ONLY outbound connections, you can use zones in the policy for this and create rules to block inbound connections&lt;/P&gt;
&lt;P&gt;-define anti spoofing for specific interface just to reflect that specific network&lt;/P&gt;
&lt;P&gt;-stateless inspection, ie disable statefull inspection (not 100% sure though if that is a must here)&lt;/P&gt;
&lt;P&gt;-policy based routing&lt;/P&gt;
&lt;P&gt;-NAT (for example define static nat only where required)&lt;/P&gt;
&lt;P&gt;Hope that helps.&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 22:29:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Force-one-way-inspection/m-p/245530#M40982</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-04-02T22:29:22Z</dc:date>
    </item>
    <item>
      <title>Re: Force one-way inspection</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Force-one-way-inspection/m-p/245537#M40985</link>
      <description>&lt;P&gt;For UDP it's easy, you can turn off 'accept replies for unknown UDP' and make sure 'accept replies' is not enabled on the custom UDP service object.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Normal inbound connections are already blocked simply by not putting a rule in to allow them.&lt;/P&gt;
&lt;P&gt;Using an open outbound HTTPS connection to prevent data transfer inbound I don't know that we can, we have to accept reply packets for the session to establish else you won't get anything. In order to be able understand the nature of the HTTPS stream once the session is up, we'd have to decrypt it so that we can see what's going on in there, which may already break things due to cert stuff etc. At a basic layer 3/4 level I don't know that anything could accomplish what you're asking for.&lt;/P&gt;
&lt;P&gt;We need to better understand the connections that are established and in what direction to be able to properly determine the course of action here.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 02:10:59 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Force-one-way-inspection/m-p/245537#M40985</guid>
      <dc:creator>emmap</dc:creator>
      <dc:date>2025-04-03T02:10:59Z</dc:date>
    </item>
  </channel>
</rss>

