<?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: PIX TCP timeout in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-tcp-timeout/m-p/193314#M620880</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't think that this is a real security problem for TCP connections because TCP headers include the sequence numbers of the packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is not a good idea to do this for UDP connections since there are no sequence numbers inside the UCP header.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Jun 2003 15:07:32 GMT</pubDate>
    <dc:creator>tvanginneken</dc:creator>
    <dc:date>2003-06-25T15:07:32Z</dc:date>
    <item>
      <title>PIX TCP timeout</title>
      <link>https://community.cisco.com/t5/network-security/pix-tcp-timeout/m-p/193313#M620878</link>
      <description>&lt;P&gt;We have some developers that have an application that they say needs to have the TCP timeout set to 4 hours (talking to some mainframe somewhere)and I need some ammunition/arguments that will show them how this is not a secure thing to do.  &lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:49:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-tcp-timeout/m-p/193313#M620878</guid>
      <dc:creator>rnance</dc:creator>
      <dc:date>2020-02-21T06:49:14Z</dc:date>
    </item>
    <item>
      <title>Re: PIX TCP timeout</title>
      <link>https://community.cisco.com/t5/network-security/pix-tcp-timeout/m-p/193314#M620880</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't think that this is a real security problem for TCP connections because TCP headers include the sequence numbers of the packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is not a good idea to do this for UDP connections since there are no sequence numbers inside the UCP header.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jun 2003 15:07:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-tcp-timeout/m-p/193314#M620880</guid>
      <dc:creator>tvanginneken</dc:creator>
      <dc:date>2003-06-25T15:07:32Z</dc:date>
    </item>
    <item>
      <title>Re: PIX TCP timeout</title>
      <link>https://community.cisco.com/t5/network-security/pix-tcp-timeout/m-p/193315#M620882</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's not really a security issue.  However, if the firewall handles alot of sessions, it may significantly impact memory consumption and slightly on the CPU load.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What type of client and server? What protocol is used for connectivity?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*nix hosts can be configured to send keepalives.  The client side app can be configured/written to send keepalives.  This will prevent the timeouts on the firewall.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jun 2003 15:19:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-tcp-timeout/m-p/193315#M620882</guid>
      <dc:creator>shannong</dc:creator>
      <dc:date>2003-06-25T15:19:39Z</dc:date>
    </item>
  </channel>
</rss>

