<?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 Hi, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485057#M268186</link>
    <description>Hi,

You can report this incident to your ISP Abuse support team.

Just give them your firewall logs and they can blackhole the attacking source IP at ISP level. They can also contact the remote admin/ISP to take corrective actions on their network.</description>
    <pubDate>Sat, 22 Mar 2014 03:01:46 GMT</pubDate>
    <dc:creator>johnlloyd_13</dc:creator>
    <dc:date>2014-03-22T03:01:46Z</dc:date>
    <item>
      <title>ASA5505 - Block attacks against port</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485053#M268182</link>
      <description>&lt;P&gt;We have a ASA 5505 that is being hammered on port 3389... Currently the port is set to allow connections from any which needs to stay the same, currently the port is being smashed by a bot that is trying to guess username/password.&lt;/P&gt;&lt;P&gt;Currently we have basic threat detection enabled and I have now enabled scanning threat detection and Shun hosts for 3600&lt;/P&gt;&lt;P&gt;Currently we arent being attacked so i cant tell if this helps the situation but what else can I apply to stop this... I estiamted that in a 30minute period over the past evening they spammed 1400 attempts.&lt;/P&gt;&lt;P&gt;Looking through the logs on the server, the source IP changes so blocking the IP is only a temporary fix.&lt;/P&gt;&lt;P&gt;Thanks for help in advance.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 03:58:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485053#M268182</guid>
      <dc:creator>Kenzie6964</dc:creator>
      <dc:date>2019-03-12T03:58:24Z</dc:date>
    </item>
    <item>
      <title>Anyone? </title>
      <link>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485054#M268183</link>
      <description>&lt;P&gt;Anyone?&amp;nbsp;&lt;IMG alt="frown" height="23" src="https://community.cisco.com/profiles/commons/libraries/ckeditor/plugins/smiley/images/confused_smile.png" title="frown" width="23" /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2014 14:54:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485054#M268183</guid>
      <dc:creator>Kenzie6964</dc:creator>
      <dc:date>2014-03-21T14:54:01Z</dc:date>
    </item>
    <item>
      <title>Are they targeting an ip</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485055#M268184</link>
      <description>&lt;P&gt;Are they targeting an ip address specifically or a URL? If they're using a URL you could try changing the public address. If you have a spare one&lt;/P&gt;&lt;P&gt;It's not a great solution but it will buy you some time to come up with something better&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, you could deny entry to that port, tell your users to use a different port and use NAT to translate the new port to 3389&lt;/P&gt;&lt;P&gt;Another crap idea but it's all I've got&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2014 15:38:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485055#M268184</guid>
      <dc:creator>Tormod Macleod</dc:creator>
      <dc:date>2014-03-21T15:38:27Z</dc:date>
    </item>
    <item>
      <title>They are targetting a IP on</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485056#M268185</link>
      <description>&lt;P&gt;They are targetting a IP on port 3389.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Changing the port isnt ideal but if thats what I have to do then I will have to.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2014 16:05:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485056#M268185</guid>
      <dc:creator>Kenzie6964</dc:creator>
      <dc:date>2014-03-21T16:05:21Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485057#M268186</link>
      <description>Hi,

You can report this incident to your ISP Abuse support team.

Just give them your firewall logs and they can blackhole the attacking source IP at ISP level. They can also contact the remote admin/ISP to take corrective actions on their network.</description>
      <pubDate>Sat, 22 Mar 2014 03:01:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485057#M268186</guid>
      <dc:creator>johnlloyd_13</dc:creator>
      <dc:date>2014-03-22T03:01:46Z</dc:date>
    </item>
    <item>
      <title>Good Afternoon!</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485058#M268187</link>
      <description>Good Afternoon!

It is not a good idea to open up port 3389. It opens up to much risk to your environment. The best option you have, if you need remote access, is to utilize AnyConnect VPN. There are many options that come with the AnyConnect client and is rather easy to configure.

Hope this helped out, sorry there really isn't a better answer!

Cheers!

Ryan</description>
      <pubDate>Mon, 24 Mar 2014 23:03:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-block-attacks-against-port/m-p/2485058#M268187</guid>
      <dc:creator>Ryan Cigelske</dc:creator>
      <dc:date>2014-03-24T23:03:49Z</dc:date>
    </item>
  </channel>
</rss>

