<?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: deny telnet command but permit JDBC protocol in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/deny-telnet-command-but-permit-jdbc-protocol/m-p/269597#M74636</link>
    <description>&lt;P&gt;if it is possible, could you explain to me how technically it happens?&lt;BR /&gt;The "telnet address port" command performs only the TCP handshake. So the packages do not contain any information about the application protocol that you want to use.&lt;BR /&gt;How can a firewall make assumptions and deny to initialize tcp protocol?&lt;/P&gt;</description>
    <pubDate>Thu, 13 Jun 2019 12:35:28 GMT</pubDate>
    <dc:creator>cata86</dc:creator>
    <dc:date>2019-06-13T12:35:28Z</dc:date>
    <item>
      <title>deny telnet command but permit JDBC protocol</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/deny-telnet-command-but-permit-jdbc-protocol/m-p/269572#M74635</link>
      <description>&lt;P&gt;We have an internal discussion about whether it is possible to block the 3 way hanshake TCP but allow the JDBC application protocol.&lt;BR /&gt;In other words we would like to block the test of the port with the command "telent address port" but we would like that the connections via JDBC continue to work.&lt;BR /&gt;is it possible to do this theoretically? Is it possibile to do it wiht paloalto firewall?&lt;BR /&gt;Please note: when I say blocking, I mean "connection refused" or "timeout". I do not intend to terminate the connection immediately.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2019 12:27:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/deny-telnet-command-but-permit-jdbc-protocol/m-p/269572#M74635</guid>
      <dc:creator>cata86</dc:creator>
      <dc:date>2019-06-13T12:27:31Z</dc:date>
    </item>
    <item>
      <title>Re: deny telnet command but permit JDBC protocol</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/deny-telnet-command-but-permit-jdbc-protocol/m-p/269597#M74636</link>
      <description>&lt;P&gt;if it is possible, could you explain to me how technically it happens?&lt;BR /&gt;The "telnet address port" command performs only the TCP handshake. So the packages do not contain any information about the application protocol that you want to use.&lt;BR /&gt;How can a firewall make assumptions and deny to initialize tcp protocol?&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2019 12:35:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/deny-telnet-command-but-permit-jdbc-protocol/m-p/269597#M74636</guid>
      <dc:creator>cata86</dc:creator>
      <dc:date>2019-06-13T12:35:28Z</dc:date>
    </item>
    <item>
      <title>Re: deny telnet command but permit JDBC protocol</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/deny-telnet-command-but-permit-jdbc-protocol/m-p/269665#M74646</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Remember the PAN needs to let traffic pass so it can identify the App-id. You might try and block the telnet application and see if that works. But blocking the tcp3way is not advised as it will not allow any traffic that is tcp.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/pan-os/8-0/pan-os-admin/app-id/app-id-overview.html" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/8-0/pan-os-admin/app-id/app-id-overview.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2019 15:46:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/deny-telnet-command-but-permit-jdbc-protocol/m-p/269665#M74646</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2019-06-13T15:46:30Z</dc:date>
    </item>
  </channel>
</rss>

