<?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 Restricting VPN gateway access on the public side in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Restricting-VPN-gateway-access-on-the-public-side/m-p/109618#M9228</link>
    <description>&lt;P&gt;Hi there. Is anyone aware of a way to lock down the public facing interface on a VPN gateway (r80.30) so that any traffic that isn’t coming from a very specific version of the Checkpoint Endpoint VPN is simply dropped? So no poking, no probing, etc on ports required to be open in order for VPN to work, unless it’s coming from a legitimate client, and maybe even a specific version of the client.&amp;nbsp;&lt;BR /&gt;I’m thinking something similar the the User-agent field in the header of a web request. Maybe just a pipe dream, but I thought I’d ask anyway.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 02 Feb 2021 23:16:51 GMT</pubDate>
    <dc:creator>cdooer</dc:creator>
    <dc:date>2021-02-02T23:16:51Z</dc:date>
    <item>
      <title>Restricting VPN gateway access on the public side</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Restricting-VPN-gateway-access-on-the-public-side/m-p/109618#M9228</link>
      <description>&lt;P&gt;Hi there. Is anyone aware of a way to lock down the public facing interface on a VPN gateway (r80.30) so that any traffic that isn’t coming from a very specific version of the Checkpoint Endpoint VPN is simply dropped? So no poking, no probing, etc on ports required to be open in order for VPN to work, unless it’s coming from a legitimate client, and maybe even a specific version of the client.&amp;nbsp;&lt;BR /&gt;I’m thinking something similar the the User-agent field in the header of a web request. Maybe just a pipe dream, but I thought I’d ask anyway.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Feb 2021 23:16:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Restricting-VPN-gateway-access-on-the-public-side/m-p/109618#M9228</guid>
      <dc:creator>cdooer</dc:creator>
      <dc:date>2021-02-02T23:16:51Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting VPN gateway access on the public side</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Restricting-VPN-gateway-access-on-the-public-side/m-p/109628#M9229</link>
      <description>&lt;P&gt;This is most likely an RFE.&lt;BR /&gt;You might be able to modify various .def files to change the implied rules to restrict access from a specific IP, though.&lt;BR /&gt;Will be something you will have to manually track with upgrades, though.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Feb 2021 06:10:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Restricting-VPN-gateway-access-on-the-public-side/m-p/109628#M9229</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2021-02-03T06:10:25Z</dc:date>
    </item>
  </channel>
</rss>

