Server Administration
  Home arrow Server Administration arrow Preventive Measures to Block SSH Attac...
Codewalker Forums 
  Tutorials  
Database Articles  
Miscellaneous  
Navigation Usability  
PEAR Articles  
Programming Basics  
Server Administration  
XML Tutorials  
  Reviews  
Database Book Reviews  
Linux Book Reviews  
Miscellaneous Reviews  
PHP Book Reviews  
PHP Software Reviews  
Server Admin Reviews  
SQL Tool Reviews  
  Code Gallery  
Content Management Code  
Contest Code  
Counters Code  
Database Code  
Date Time Code  
Discussion Board Code  
Email Code  
File Manipulation Code  
GUI Code  
Link Farm Code  
Miscellaneous Code  
Search Code  
Site Navigation Code  
User Management Code  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
Download TestComplete 
Forums Sitemap 
Weekly Newsletter 
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
SERVER ADMINISTRATION

Preventive Measures to Block SSH Attacks
By: Barzan 'Tony' Antal
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 3
    2009-10-28

    Table of Contents:
  • Preventive Measures to Block SSH Attacks
  • Preventive Measures
  • Even More Measures
  • Final Thoughts

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Preventive Measures to Block SSH Attacks


    (Page 1 of 4 )

    It should not surprise anyone that over the past few years, SSH attacks have become stupendously frequent. It is not uncommon to see tens of thousands of login occurrences in the case of a mid-sized company. Throughout this article we will look into viable solutions and preventive measures that we recommend implementing to reduce the count of these attacks—often eliminating them entirely.

    The vast majority of SSH attacks aren’t executed by skilled hackers that are willing to do everything it takes to break into your servers. Statistics have proven that script kiddies dominate, and most of the time, they have no real reasons or motives. It is just that getting remote access into a server can open doors to countless other opportunities. But losing control over machines can be pretty sad.

    We will focus on taking preventive measures to block brute-force SSH attacks. Brute-force is a technique that includes automating the login procedure, doing a countless number of attempts in a particular time-frame, using dictionaries and other specific techniques, to improve the probability of guessing the password. These attacks are pretty visible from the log files as multiple failed login attempts. And they can be blocked—effectively!

    Larger corporations and business organizations are hiring experts and the services of numerous high-profile IT security companies to greatly increase their security. Unfortunately, the harsh reality is that when and if the attack is targeted, there is almost always a way to get in. It’s like acquiring the most secure car and using the best possible alarm systems on the market—there is still a way to break into it.

    The question is more than likely “how far” the attacker is willing to go instead. In the case of most attacks, those script kiddies will quickly switch targets, since all they go for is checking the obvious; if those doors are open, they are more than happy to step through them, but when things gets tougher, they simply give up. This is basically good news for us, since it means that, almost always, the attacker won’t go the extra mile.

    In this article we will discuss most prevention techniques, security tips, and popular strategies that do an awesome job eliminating most attacks. But please be aware that there are no guarantees and there is always a way in. However, chances are you will also find out that once these are implemented, the count of SSH attacks drops to almost zero. Brute-forcing won’t be possible. It takes too much time. It’s just too hard.

    Let’s get down to action.

    More Server Administration Articles
    More By Barzan 'Tony' Antal


     

    SERVER ADMINISTRATION ARTICLES

    - Processes in the UNIX Shell
    - Migrating from Windows to Wine
    - Wine: Not Another Emulator
    - Preventive Measures to Block SSH Attacks
    - Monitoring Temperatures with Cacti
    - Cacti: RRDTool-based Graphing Solution
    - Network Magic 5.0 Review
    - Netfilter and Iptables Overview
    - Installing and Configuring Squid
    - Clickfree PC Backup Systems Compared
    - Squid, the Caching Proxy
    - Regular Expressions in the Unix Shell
    - Source Code Version Control Solutions
    - OTRS: Open Source Ticket Request System
    - Clonezilla: Free Mass Disk-Cloning Utility





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 2 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek