<?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 Deny tcp reverse aTTACK on inside interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-attack-on-inside-interface/m-p/2272465#M350145</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;Sounds to me like something that might be good to go through with TAC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you copy/paste (or attach screenshot) of the exact log messages that you are seeing and mention the exact software version running on the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 10 May 2013 15:53:05 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2013-05-10T15:53:05Z</dc:date>
    <item>
      <title>Deny tcp reverse aTTACK on inside interface</title>
      <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-attack-on-inside-interface/m-p/2272464#M350144</link>
      <description>&lt;P&gt;HI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AS checked on asa we are geeting the above logs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cpu on asa is almost 99 utilization .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interseting thing is no user traffic is effected everything is running as usual.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why question is eventhough cpu is high no traffic being affected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More ever we are not able to the malicious traffic.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:41:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-tcp-reverse-attack-on-inside-interface/m-p/2272464#M350144</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2019-03-12T01:41:23Z</dc:date>
    </item>
    <item>
      <title>Deny tcp reverse aTTACK on inside interface</title>
      <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-attack-on-inside-interface/m-p/2272465#M350145</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;Sounds to me like something that might be good to go through with TAC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you copy/paste (or attach screenshot) of the exact log messages that you are seeing and mention the exact software version running on the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 May 2013 15:53:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-tcp-reverse-attack-on-inside-interface/m-p/2272465#M350145</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-05-10T15:53:05Z</dc:date>
    </item>
    <item>
      <title>Deny tcp reverse aTTACK on inside interface</title>
      <link>https://community.cisco.com/t5/network-security/deny-tcp-reverse-attack-on-inside-interface/m-p/2272466#M350146</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thanks for revert&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have ASA 8.2(4)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Plese find the logs attachted .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/0/3/3/139330-reverse%20path%20check.JPG" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Prashant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 May 2013 10:18:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/deny-tcp-reverse-attack-on-inside-interface/m-p/2272466#M350146</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2013-05-16T10:18:13Z</dc:date>
    </item>
  </channel>
</rss>

