<?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: Telnet through PIX in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/telnet-through-pix/m-p/1134512#M896100</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Adaptive Security Algorithm, used by the security appliance for stateful application inspection,&lt;/P&gt;&lt;P&gt;ensures the secure use of applications and services. Some applications require special handling by the&lt;/P&gt;&lt;P&gt;security appliance and specific application inspection engines are provided for this purpose.&lt;/P&gt;&lt;P&gt;Applications that require special application inspection engines are those that embed IP addressing&lt;/P&gt;&lt;P&gt;information in the user data packet or open secondary channels on dynamically assigned ports.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Telnet does not require special handling, so it is not added in global policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH...rate if helpful..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Sep 2008 11:26:33 GMT</pubDate>
    <dc:creator>satish_zanjurne</dc:creator>
    <dc:date>2008-09-22T11:26:33Z</dc:date>
    <item>
      <title>Telnet through PIX</title>
      <link>https://community.cisco.com/t5/network-security/telnet-through-pix/m-p/1134511#M896098</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Why can I telnet through the PIX when there is no reference to telnet in the class inspection default list or in the default inspection traffic list? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I see there is a reference to ICMP so that explains why transit pings do not work, but I can^t get my head round the workings of telnet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the Class inspection deafault&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;/P&gt;&lt;P&gt; class inspection_default&lt;/P&gt;&lt;P&gt;  inspect dns preset_dns_map &lt;/P&gt;&lt;P&gt;  inspect ftp &lt;/P&gt;&lt;P&gt;  inspect h323 h225 &lt;/P&gt;&lt;P&gt;  inspect h323 ras &lt;/P&gt;&lt;P&gt;  inspect netbios &lt;/P&gt;&lt;P&gt;  inspect rsh &lt;/P&gt;&lt;P&gt;  inspect rtsp &lt;/P&gt;&lt;P&gt;  inspect skinny  &lt;/P&gt;&lt;P&gt;  inspect esmtp &lt;/P&gt;&lt;P&gt;  inspect sqlnet &lt;/P&gt;&lt;P&gt;  inspect sunrpc &lt;/P&gt;&lt;P&gt;  inspect tftp &lt;/P&gt;&lt;P&gt;  inspect sip  &lt;/P&gt;&lt;P&gt;  inspect xdmcp &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and here is the default inspection traffic&lt;/P&gt;&lt;P&gt;mpf-class-map mode commands/options:&lt;/P&gt;&lt;P&gt;  access-list                 Match an Access List&lt;/P&gt;&lt;P&gt;  any                         Match any packet&lt;/P&gt;&lt;P&gt;  default-inspection-traffic  Match default inspection traffic: &lt;/P&gt;&lt;P&gt;                              ctiqbe----tcp--2748      dns-------udp--53       &lt;/P&gt;&lt;P&gt;                              ftp-------tcp--21        gtp-------udp--2123,3386&lt;/P&gt;&lt;P&gt;                              h323-h225-tcp--1720      h323-ras--udp--1718-1719&lt;/P&gt;&lt;P&gt;                              http------tcp--80        icmp------icmp          &lt;/P&gt;&lt;P&gt;                              ils-------tcp--389       mgcp------udp--2427,2727&lt;/P&gt;&lt;P&gt;                              netbios---udp--137-138   radius-acct---udp--1646&lt;/P&gt;&lt;P&gt;                              rpc-------udp--111       rsh-------tcp--514      &lt;/P&gt;&lt;P&gt;                              rtsp------tcp--554       sip-------tcp--5060     &lt;/P&gt;&lt;P&gt;                              sip-------udp--5060      skinny----tcp--2000     &lt;/P&gt;&lt;P&gt;                              smtp------tcp--25        sqlnet----tcp--1521     &lt;/P&gt;&lt;P&gt;                              tftp------udp--69        xdmcp-----udp--177      &lt;/P&gt;&lt;P&gt;  dscp                        Match IP DSCP (DiffServ CodePoints)&lt;/P&gt;&lt;P&gt;  flow                        Flow based Policy&lt;/P&gt;&lt;P&gt;  port                        Match TCP/UDP port(s)&lt;/P&gt;&lt;P&gt;  precedence                  Match IP precedence&lt;/P&gt;&lt;P&gt;  rtp                         Match RTP port numbers&lt;/P&gt;&lt;P&gt;  tunnel-group                Match a Tunnel Group&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:47:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/telnet-through-pix/m-p/1134511#M896098</guid>
      <dc:creator>walter1972</dc:creator>
      <dc:date>2019-03-11T13:47:35Z</dc:date>
    </item>
    <item>
      <title>Re: Telnet through PIX</title>
      <link>https://community.cisco.com/t5/network-security/telnet-through-pix/m-p/1134512#M896100</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Adaptive Security Algorithm, used by the security appliance for stateful application inspection,&lt;/P&gt;&lt;P&gt;ensures the secure use of applications and services. Some applications require special handling by the&lt;/P&gt;&lt;P&gt;security appliance and specific application inspection engines are provided for this purpose.&lt;/P&gt;&lt;P&gt;Applications that require special application inspection engines are those that embed IP addressing&lt;/P&gt;&lt;P&gt;information in the user data packet or open secondary channels on dynamically assigned ports.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Telnet does not require special handling, so it is not added in global policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH...rate if helpful..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Sep 2008 11:26:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/telnet-through-pix/m-p/1134512#M896100</guid>
      <dc:creator>satish_zanjurne</dc:creator>
      <dc:date>2008-09-22T11:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: Telnet through PIX</title>
      <link>https://community.cisco.com/t5/network-security/telnet-through-pix/m-p/1134513#M896102</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So would I be right in saying that in addition to this, stateful inspection is geared up more for connection oriented traffic ie TCP (telnet here) and that all TCP traffic is inspected. I still don't see why other TCP ports are included in the default inspection traffic in my origional post and yet port 23 is not. How does the class inspection default relate to this default inspection traffic list? &lt;/P&gt;&lt;P&gt;Thanks for the interest. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Sep 2008 18:36:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/telnet-through-pix/m-p/1134513#M896102</guid>
      <dc:creator>walter1972</dc:creator>
      <dc:date>2008-09-22T18:36:49Z</dc:date>
    </item>
    <item>
      <title>Re: Telnet through PIX</title>
      <link>https://community.cisco.com/t5/network-security/telnet-through-pix/m-p/1134514#M896106</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Some of the application requires special handling which includes for an example an application requiring something like opening an dynamic port when an connection is established which require special handling so it is considered as part of application inspection,which inspects packets traveling through firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rate it helps!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Archana.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Sep 2008 05:07:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/telnet-through-pix/m-p/1134514#M896106</guid>
      <dc:creator>marchanamendon</dc:creator>
      <dc:date>2008-09-23T05:07:40Z</dc:date>
    </item>
  </channel>
</rss>

