<?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 Blocking port scanners in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Blocking-port-scanners/m-p/203933#M33886</link>
    <description>&lt;P&gt;On my FW I will like to block port scanners. I've attempted the solution outlined in sk110873, but Nmap is still able to extract information about open ports. Do you have any suggestions on effectively blocking port scanners to ensure they cannot gather any information?&lt;/P&gt;&lt;P&gt;I am using R81.10 – gateway and R81.20 for MGMT.&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jan 2024 11:41:46 GMT</pubDate>
    <dc:creator>SubZer0</dc:creator>
    <dc:date>2024-01-23T11:41:46Z</dc:date>
    <item>
      <title>Blocking port scanners</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Blocking-port-scanners/m-p/203933#M33886</link>
      <description>&lt;P&gt;On my FW I will like to block port scanners. I've attempted the solution outlined in sk110873, but Nmap is still able to extract information about open ports. Do you have any suggestions on effectively blocking port scanners to ensure they cannot gather any information?&lt;/P&gt;&lt;P&gt;I am using R81.10 – gateway and R81.20 for MGMT.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2024 11:41:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Blocking-port-scanners/m-p/203933#M33886</guid>
      <dc:creator>SubZer0</dc:creator>
      <dc:date>2024-01-23T11:41:46Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking port scanners</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Blocking-port-scanners/m-p/204011#M33898</link>
      <description>&lt;P&gt;This would be a good next step:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk112241" target="_blank" rel="noopener"&gt;https://support.checkpoint.com/results/sk/sk112241&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Btw you will never truely block port scans. They can be tweaked that they stay under the 'radar'.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So you could scan a subnet, but also one host. You can scan small port range, but also big. You can scan 10 ports a second or more.&lt;/P&gt;
&lt;P&gt;There are so many factor that you can change that a firewall is not able to know if this is a port scan yes or no.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2024 21:24:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Blocking-port-scanners/m-p/204011#M33898</guid>
      <dc:creator>Lesley</dc:creator>
      <dc:date>2024-01-23T21:24:43Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking port scanners</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Blocking-port-scanners/m-p/204014#M33899</link>
      <description>&lt;P&gt;Thats actually really GOOD question. But, in my mind, and this is just me personally, I cant really see logically how that can be achieved, because you would need to know src/port numbers used in order to do it effectively.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2024 21:32:45 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Blocking-port-scanners/m-p/204014#M33899</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-01-23T21:32:45Z</dc:date>
    </item>
  </channel>
</rss>

