<?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: Port Scans &amp;amp; Telnets on a PA running 8.0 in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/port-scans-amp-telnets-on-a-pa-running-8-0/m-p/383170#M1047</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think For the syn-scan (with no Threat prevention profile) or telnet you can discover open ports, in traffic logs it should be appear as "incomplete". In session logs also it should be on "discard" state.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**Against scanning zone-protection profiles has good prevetion options.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 31 Jan 2021 23:11:22 GMT</pubDate>
    <dc:creator>upelister</dc:creator>
    <dc:date>2021-01-31T23:11:22Z</dc:date>
    <item>
      <title>Port Scans &amp; Telnets on a PA running 8.0</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/port-scans-amp-telnets-on-a-pa-running-8-0/m-p/224763#M369</link>
      <description>&lt;P&gt;I am new to the world of PA and next gen firewalls and took some online training.&amp;nbsp; I discovered that in the Traffic Proccessing phase before App ID gets applied in the Security Policy that the session is already allowed to start if the layer 4 ports are allowed in the policy.&amp;nbsp; This makes me wonder if I were to run a port scan on my public address or telnet to a specific port that I would still be able to find out if its open using those same old tricks.&amp;nbsp; In my mind&amp;nbsp;since all&amp;nbsp;the telnet trick does is send a&amp;nbsp;SYN packet to the&amp;nbsp;IP address&amp;nbsp;I'm troubleshooting&amp;nbsp;than the PA&amp;nbsp;should still be able to send back a SYN ACK for the port I'm checking thus letting me know if its open or not. &amp;nbsp;I understand that the point of App ID is&amp;nbsp;to prevent&amp;nbsp;hackers&amp;nbsp;from using any application they want over a default port (e.g using http over port 22) but in theory if the session is allowed to start before App ID kicks in then I can still telnet to port 80 to see if its open just like I always have.&amp;nbsp; Is this true or am I&amp;nbsp;way out in deep space nine?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Aug 2018 18:50:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/port-scans-amp-telnets-on-a-pa-running-8-0/m-p/224763#M369</guid>
      <dc:creator>MarioMarquez</dc:creator>
      <dc:date>2018-08-03T18:50:42Z</dc:date>
    </item>
    <item>
      <title>Re: Port Scans &amp; Telnets on a PA running 8.0</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/port-scans-amp-telnets-on-a-pa-running-8-0/m-p/383170#M1047</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think For the syn-scan (with no Threat prevention profile) or telnet you can discover open ports, in traffic logs it should be appear as "incomplete". In session logs also it should be on "discard" state.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**Against scanning zone-protection profiles has good prevetion options.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 31 Jan 2021 23:11:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/port-scans-amp-telnets-on-a-pa-running-8-0/m-p/383170#M1047</guid>
      <dc:creator>upelister</dc:creator>
      <dc:date>2021-01-31T23:11:22Z</dc:date>
    </item>
    <item>
      <title>Re: Port Scans &amp; Telnets on a PA running 8.0</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/port-scans-amp-telnets-on-a-pa-running-8-0/m-p/383174#M1049</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/92764"&gt;@MarioMarquez&lt;/a&gt;&amp;nbsp; your assumption is correct&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you can decrease your external footprint by using application-default in all of your rule so that only the ports you actually expose to the outside are open&amp;nbsp; but the ports that are open are open so can be connected to via telnet&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;to protect from portscans you should enable a zone protection profile with host sweep and port scan set to block so that scanners will be detected and blocked after a number of suspicious connections&lt;/P&gt;</description>
      <pubDate>Sun, 31 Jan 2021 23:38:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/port-scans-amp-telnets-on-a-pa-running-8-0/m-p/383174#M1049</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2021-01-31T23:38:45Z</dc:date>
    </item>
    <item>
      <title>Re: Port Scans &amp; Telnets on a PA running 8.0</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/port-scans-amp-telnets-on-a-pa-running-8-0/m-p/383371#M1055</link>
      <description>&lt;P&gt;This chapter teaches how to scan the operating system for viruses and how to stop DDoS attacks. Although applications such as Zombie Zapper are not foolproof, they can still help you prepare against such attacks&amp;nbsp;&lt;A href="https://prepaidcardstatus.net/" target="_self"&gt;prepaidcardstatus&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Feb 2021 08:24:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/port-scans-amp-telnets-on-a-pa-running-8-0/m-p/383371#M1055</guid>
      <dc:creator>Loyces</dc:creator>
      <dc:date>2021-02-04T08:24:05Z</dc:date>
    </item>
  </channel>
</rss>

