<?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 Non-RFC Compliant Telnet Traffic on Port 23 in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/non-rfc-compliant-telnet-traffic-on-port-23/m-p/395325#M1100</link>
    <description>&lt;P&gt;Can someone explain about the threat name/vulnerability Non-RFC compliant Telnet traffic on Port 23?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Apr 2021 05:51:00 GMT</pubDate>
    <dc:creator>agilessk</dc:creator>
    <dc:date>2021-04-01T05:51:00Z</dc:date>
    <item>
      <title>Non-RFC Compliant Telnet Traffic on Port 23</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/non-rfc-compliant-telnet-traffic-on-port-23/m-p/395325#M1100</link>
      <description>&lt;P&gt;Can someone explain about the threat name/vulnerability Non-RFC compliant Telnet traffic on Port 23?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 05:51:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/non-rfc-compliant-telnet-traffic-on-port-23/m-p/395325#M1100</guid>
      <dc:creator>agilessk</dc:creator>
      <dc:date>2021-04-01T05:51:00Z</dc:date>
    </item>
    <item>
      <title>Re: Non-RFC Compliant Telnet Traffic on Port 23</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/non-rfc-compliant-telnet-traffic-on-port-23/m-p/395519#M1101</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;So to start telnet uses port 23. What the message is saying is that it see's the packets but it doesnt conform to the RFC, i.e. the packet doesnt look like its supposed to. Could be that the application sending the traffic is not forming the packets correctly, or another application other than telnet is using that port.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 21:07:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/non-rfc-compliant-telnet-traffic-on-port-23/m-p/395519#M1101</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2021-04-01T21:07:17Z</dc:date>
    </item>
    <item>
      <title>Re: Non-RFC Compliant Telnet Traffic on Port 23</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/non-rfc-compliant-telnet-traffic-on-port-23/m-p/395698#M1102</link>
      <description>&lt;P&gt;Thanks for the response. how to investigate that the&amp;nbsp;&lt;SPAN&gt;application sending the traffic is not forming the packets correctly or non-rfc compliant? any examples or references. Thanks again.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Apr 2021 07:50:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/non-rfc-compliant-telnet-traffic-on-port-23/m-p/395698#M1102</guid>
      <dc:creator>agilessk</dc:creator>
      <dc:date>2021-04-04T07:50:15Z</dc:date>
    </item>
    <item>
      <title>Re: Non-RFC Compliant Telnet Traffic on Port 23</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/non-rfc-compliant-telnet-traffic-on-port-23/m-p/395716#M1103</link>
      <description>&lt;P&gt;You can enable advanced packetcapture on the threat profile&lt;/P&gt;&lt;P&gt;That will allow you to verify what the firewall is receiving&lt;/P&gt;</description>
      <pubDate>Sun, 04 Apr 2021 09:09:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/non-rfc-compliant-telnet-traffic-on-port-23/m-p/395716#M1103</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2021-04-04T09:09:57Z</dc:date>
    </item>
  </channel>
</rss>

