<?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: Disable TCP 1323 Timestamp response through Palo Alto Firewall? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/305583#M79415</link>
    <description>&lt;P&gt;Interestingly, for me it is the PALO ALTO 5200 series Vers 8.1 that IS RESPONDING to timestamp requests from a desktop.&lt;BR /&gt;&lt;BR /&gt;Why? I don't know.&amp;nbsp; Why offer discovery information that a hacker could use?&amp;nbsp; We have PING enabled on the interface--but I don't see any way to stop it from answering these esoteric ICMP queries.&lt;BR /&gt;&lt;BR /&gt;It is also being asked for ADDRESS MASK (ICMP), but at least it doesn't respond to that.&lt;/P&gt;</description>
    <pubDate>Fri, 03 Jan 2020 18:05:45 GMT</pubDate>
    <dc:creator>Royalfr</dc:creator>
    <dc:date>2020-01-03T18:05:45Z</dc:date>
    <item>
      <title>Disable TCP 1323 Timestamp response through Palo Alto Firewall?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/37517#M27508</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'm wondering whether is there a way to set the PAN Firewall to detect and drop TCP 1323 Timestamp queries to servers?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;According to some web vulnerabilities scanning reports, it is reccomended to disable the TCP Timestamp as it discloses server uptime information, allowing attackers to guess the OS patch status.&lt;/P&gt;&lt;P&gt;In the recent Windows server OS (2008 and R2), disabling the TCP1323opts in registry doesn't seem to disable to the Timestamp responses as nmap scan test will still be able to get the uptime information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In some web scanner reports, there are reccomendations to set in cisco firewalls to disable tcp timestamp eg, (no ip tcp timestamp).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate the reponse,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Hans&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Apr 2013 04:54:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/37517#M27508</guid>
      <dc:creator>LCMember4126</dc:creator>
      <dc:date>2013-04-26T04:54:44Z</dc:date>
    </item>
    <item>
      <title>Re: Disable TCP 1323 Timestamp response through Palo Alto Firewall?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/37518#M27509</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not that im aware of.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Disabling timestamps should be done at the endpoints if you want to block timestamp information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Easy to do in a linuxbox:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;echo "0" &amp;gt; /proc/sys/net/ipv4/tcp_timestamps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you reboot your windowsbox before you did the new nmap test?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also verify with pcap so the uptime which nmap picks up isnt from some application running on your server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The "no ip tcp timestamp" is usually for traffic that the cisco device itself generates (such as stuff from its mgmt-interface etc) and not for traffic that passes through.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However note that timestamps are part of "high performance tcp" if I remember it correctly so disabling timestamps could in some situations be bad (&lt;A href="http://www.ietf.org/rfc/rfc1323.txt" title="http://www.ietf.org/rfc/rfc1323.txt"&gt;http://www.ietf.org/rfc/rfc1323.txt&lt;/A&gt;).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Apr 2013 05:38:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/37518#M27509</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-04-26T05:38:14Z</dc:date>
    </item>
    <item>
      <title>Re: Disable TCP 1323 Timestamp response through Palo Alto Firewall?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/37519#M27510</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also instead of altering the registry try to use this cmdline instead:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;netsh int tcp set global timestamps=disabled&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://technet.microsoft.com/en-us/library/cc731258%28WS.10%29.aspx#BKMK_6" title="http://technet.microsoft.com/en-us/library/cc731258%28WS.10%29.aspx#BKMK_6"&gt;http://technet.microsoft.com/en-us/library/cc731258%28WS.10%29.aspx#BKMK_6&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You might need a reboot afterwards aswell...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Apr 2013 05:47:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/37519#M27510</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-04-26T05:47:28Z</dc:date>
    </item>
    <item>
      <title>Re: Disable TCP 1323 Timestamp response through Palo Alto Firewall?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/305583#M79415</link>
      <description>&lt;P&gt;Interestingly, for me it is the PALO ALTO 5200 series Vers 8.1 that IS RESPONDING to timestamp requests from a desktop.&lt;BR /&gt;&lt;BR /&gt;Why? I don't know.&amp;nbsp; Why offer discovery information that a hacker could use?&amp;nbsp; We have PING enabled on the interface--but I don't see any way to stop it from answering these esoteric ICMP queries.&lt;BR /&gt;&lt;BR /&gt;It is also being asked for ADDRESS MASK (ICMP), but at least it doesn't respond to that.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jan 2020 18:05:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/305583#M79415</guid>
      <dc:creator>Royalfr</dc:creator>
      <dc:date>2020-01-03T18:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: Disable TCP 1323 Timestamp response through Palo Alto Firewall?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/305766#M79472</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is possible to drop packets with the timestamp option set through a Zone Protection profile.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Network -&amp;gt; Zone Protection -&amp;gt; Packet Based Attack Protection -&amp;gt; IP Drop -&amp;gt; Timestamp.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The zone protection profile would then be applied to the ingress zone, untrust.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Luke.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jan 2020 15:21:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/305766#M79472</guid>
      <dc:creator>LukeBullimore</dc:creator>
      <dc:date>2020-01-06T15:21:40Z</dc:date>
    </item>
    <item>
      <title>Re: Disable TCP 1323 Timestamp response through Palo Alto Firewall?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/340535#M85462</link>
      <description>&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;In my case, the Rapid7 reported this vulnerability on PA5020 and PA5220:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;&lt;STRONG&gt;Vulnerability Title:&lt;/STRONG&gt; TCP timestamp response&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;&lt;STRONG&gt;Description:&lt;/STRONG&gt; The remote host responded with a TCP timestamp. The TCP timestamp response can be used to approximate the remote host's uptime, potentially aiding in further attacks. Additionally, some operating systems can be fingerprinted based on the behavior of their TCP timestamps.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;The scanning was ran to the MGMT interface, that's why the Zone Protection Profile won't work in this case.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jul 2020 16:02:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/340535#M85462</guid>
      <dc:creator>Alvaro_Arango</dc:creator>
      <dc:date>2020-07-24T16:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: Disable TCP 1323 Timestamp response through Palo Alto Firewall?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/384904#M90083</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Was there any solution for disabling tcp timestamp in mgmt interface.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Feb 2021 00:40:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/384904#M90083</guid>
      <dc:creator>dinesh3888</dc:creator>
      <dc:date>2021-02-10T00:40:47Z</dc:date>
    </item>
    <item>
      <title>Re: Disable TCP 1323 Timestamp response through Palo Alto Firewall?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/405562#M92024</link>
      <description>&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/threat-vulnerability-discussions/tcp-timestamp-response-on-mgmnt-ip/td-p/384943" target="_blank" rel="noopener"&gt;https://live.paloaltonetworks.com/t5/threat-vulnerability-discussions/tcp-timestamp-response-on-mgmn...&lt;/A&gt;&lt;/P&gt;&lt;P&gt;User&amp;nbsp;&lt;A href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/34186" target="_blank"&gt;@mivaldi&lt;/A&gt;&amp;nbsp; explains this topic and what can be done.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also found this option as well:&lt;BR /&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClFZCA0" target="_blank" rel="nofollow noopener noreferrer"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClFZCA0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 May 2021 19:40:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/disable-tcp-1323-timestamp-response-through-palo-alto-firewall/m-p/405562#M92024</guid>
      <dc:creator>DaBone</dc:creator>
      <dc:date>2021-05-07T19:40:04Z</dc:date>
    </item>
  </channel>
</rss>

