<?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 SSH Access Lost in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ssh-access-lost/m-p/2811407#M173209</link>
    <description>&lt;P style="margin: 0in 0in 8pt;"&gt;&lt;FONT color="#000000" face="Calibri"&gt;There was some penetration test happened and one machine has sent huge logs towards syslog server. Because of which whole bandwidth got choked and SSH access to all servers falling in that VLAN got lost,&lt;/FONT&gt;&lt;/P&gt;
&lt;P style="margin: 0in 0in 8pt;"&gt;&lt;FONT color="#000000" face="Calibri"&gt;Eventually, we had to restart the restart the servers from ILO.&lt;/FONT&gt;&lt;/P&gt;
&lt;P style="margin: 0in 0in 8pt;"&gt;&lt;FONT color="#000000" face="Calibri"&gt;Note – only SSH access was gone, rest all the service on servers were running fine on servers.&lt;/FONT&gt;&lt;/P&gt;
&lt;P style="margin: 0in 0in 8pt;"&gt;&lt;FONT color="#000000" face="Calibri"&gt;Is there any kind of hardening can be done on CISCO ASA Firewall’s to prevent receiving huge logs or preventing SSH logs issue. Please keep that in mind that we will not be aware of which source IP will be sending traffic.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000" face="Times New Roman"&gt; &lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 07:10:06 GMT</pubDate>
    <dc:creator>sunil.chhabra</dc:creator>
    <dc:date>2019-03-12T07:10:06Z</dc:date>
    <item>
      <title>SSH Access Lost</title>
      <link>https://community.cisco.com/t5/network-security/ssh-access-lost/m-p/2811407#M173209</link>
      <description>&lt;P style="margin: 0in 0in 8pt;"&gt;&lt;FONT color="#000000" face="Calibri"&gt;There was some penetration test happened and one machine has sent huge logs towards syslog server. Because of which whole bandwidth got choked and SSH access to all servers falling in that VLAN got lost,&lt;/FONT&gt;&lt;/P&gt;
&lt;P style="margin: 0in 0in 8pt;"&gt;&lt;FONT color="#000000" face="Calibri"&gt;Eventually, we had to restart the restart the servers from ILO.&lt;/FONT&gt;&lt;/P&gt;
&lt;P style="margin: 0in 0in 8pt;"&gt;&lt;FONT color="#000000" face="Calibri"&gt;Note – only SSH access was gone, rest all the service on servers were running fine on servers.&lt;/FONT&gt;&lt;/P&gt;
&lt;P style="margin: 0in 0in 8pt;"&gt;&lt;FONT color="#000000" face="Calibri"&gt;Is there any kind of hardening can be done on CISCO ASA Firewall’s to prevent receiving huge logs or preventing SSH logs issue. Please keep that in mind that we will not be aware of which source IP will be sending traffic.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000" face="Times New Roman"&gt; &lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:10:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-access-lost/m-p/2811407#M173209</guid>
      <dc:creator>sunil.chhabra</dc:creator>
      <dc:date>2019-03-12T07:10:06Z</dc:date>
    </item>
    <item>
      <title>The first thought that comes</title>
      <link>https://community.cisco.com/t5/network-security/ssh-access-lost/m-p/2811408#M173210</link>
      <description>&lt;P&gt;The first thought that comes to mind is why allow SSH and syslog from the Internet at all? &amp;nbsp;Close that off. &amp;nbsp;If people need SSH access remotely then do it via VPN.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Second option is to enable a rate limit of SSH traffic. &amp;nbsp;Sample config:&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;access-list rate-limit-ssh-acl extended permit tcp any any eq ssh&lt;BR /&gt;&lt;BR /&gt;class-map rate-limit-ssh&lt;BR /&gt; match access-list rate-limit-ssh-acl&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;policy-map ssh-policy&lt;BR /&gt; class rate-limit-ssh&lt;BR /&gt;   police output 100000 8000&lt;BR /&gt;&lt;BR /&gt;service-policy ssh-policy interface &amp;lt;interface facing servers&amp;gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 21 Jan 2016 04:20:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-access-lost/m-p/2811408#M173210</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-01-21T04:20:24Z</dc:date>
    </item>
    <item>
      <title>Note that with login services</title>
      <link>https://community.cisco.com/t5/network-security/ssh-access-lost/m-p/2811409#M173211</link>
      <description>&lt;P&gt;Note that with login services like SSH you can often configure them to ignore more login attempts after "x" bad login attempts in "y" time. &amp;nbsp;It is possible you tripped this threshold, and it was just blocking new connections.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The other option is you should enable this option on your servers. &amp;nbsp;Maybe tell the servers&amp;nbsp;to ignore connections attempts for 10 minutes if you get more than 20 failed attempts in 60s or something like that.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2016 04:22:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-access-lost/m-p/2811409#M173211</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-01-21T04:22:37Z</dc:date>
    </item>
  </channel>
</rss>

