<?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: Securing Wireless LAN Controllers against management credential brute force attacks in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/securing-wireless-lan-controllers-against-management-credential/m-p/4145833#M966</link>
    <description>&lt;P&gt;I'll rephrase the question...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the recommended way to secure WLCs against SSH brute force attacks by blocking the bad actor's source address please? It's not enough that an account is locked out after x number of failed login attempts.&amp;nbsp; We need to also block/blacklist any bad actor's source address dynamically &amp;amp; autonomously after x number of failed login attempts.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TIA,&lt;/P&gt;&lt;P&gt;Sam&lt;/P&gt;</description>
    <pubDate>Thu, 03 Sep 2020 14:41:59 GMT</pubDate>
    <dc:creator>shammock</dc:creator>
    <dc:date>2020-09-03T14:41:59Z</dc:date>
    <item>
      <title>Securing Wireless LAN Controllers against management credential brute force attacks</title>
      <link>https://community.cisco.com/t5/wireless/securing-wireless-lan-controllers-against-management-credential/m-p/4144564#M963</link>
      <description>&lt;P&gt;What is the recommended way to secure WLCs against management brute force attacks from the same source MAC or IP address please?&amp;nbsp; Need an autonomous way to recognize multiple failed attempts from a bad actor who moves to another login when an account locks &amp;amp; just continues to hammer away with credential brute force attack over SSH / WebGUI.&amp;nbsp; Bad actor should be blocked without manual intervention.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Sam&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 19:27:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/securing-wireless-lan-controllers-against-management-credential/m-p/4144564#M963</guid>
      <dc:creator>shammock</dc:creator>
      <dc:date>2021-07-05T19:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: Securing Wireless LAN Controllers against management credential brute force attacks</title>
      <link>https://community.cisco.com/t5/wireless/securing-wireless-lan-controllers-against-management-credential/m-p/4144661#M964</link>
      <description>&lt;P&gt;From the same source and MAC address?&amp;nbsp; Block the MAC address from joining the wireless network in the first place.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Sep 2020 18:59:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/securing-wireless-lan-controllers-against-management-credential/m-p/4144661#M964</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2020-09-01T18:59:34Z</dc:date>
    </item>
    <item>
      <title>Re: Securing Wireless LAN Controllers against management credential brute force attacks</title>
      <link>https://community.cisco.com/t5/wireless/securing-wireless-lan-controllers-against-management-credential/m-p/4145833#M966</link>
      <description>&lt;P&gt;I'll rephrase the question...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the recommended way to secure WLCs against SSH brute force attacks by blocking the bad actor's source address please? It's not enough that an account is locked out after x number of failed login attempts.&amp;nbsp; We need to also block/blacklist any bad actor's source address dynamically &amp;amp; autonomously after x number of failed login attempts.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TIA,&lt;/P&gt;&lt;P&gt;Sam&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2020 14:41:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/securing-wireless-lan-controllers-against-management-credential/m-p/4145833#M966</guid>
      <dc:creator>shammock</dc:creator>
      <dc:date>2020-09-03T14:41:59Z</dc:date>
    </item>
    <item>
      <title>Re: Securing Wireless LAN Controllers against management credential brute force attacks</title>
      <link>https://community.cisco.com/t5/wireless/securing-wireless-lan-controllers-against-management-credential/m-p/4145884#M968</link>
      <description>&lt;P&gt;Hi Sam,&lt;/P&gt;&lt;P&gt;What is your network architecture?&lt;SPAN&gt;Do you have firewall?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you getting traps to your mail when someone blocked?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yan Bedia&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2020 16:02:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/securing-wireless-lan-controllers-against-management-credential/m-p/4145884#M968</guid>
      <dc:creator>YanBedia49446</dc:creator>
      <dc:date>2020-09-03T16:02:44Z</dc:date>
    </item>
    <item>
      <title>Re: Securing Wireless LAN Controllers against management credential brute force attacks</title>
      <link>https://community.cisco.com/t5/wireless/securing-wireless-lan-controllers-against-management-credential/m-p/4147383#M969</link>
      <description>&lt;P&gt;There isn't much built in for that. The primary way is to limit the SSH access to the IP addresses of the managing computers and block all others.&lt;/P&gt;
&lt;P&gt;The WLC will generate an snmp trap for every failed attempt (if I'm not mistaken) which you could process in your monitoring system.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Sep 2020 15:37:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/securing-wireless-lan-controllers-against-management-credential/m-p/4147383#M969</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2020-09-07T15:37:16Z</dc:date>
    </item>
  </channel>
</rss>

