5 Best Practices to Secure and Protect SSH Server

SSH (Secure Shell) is an open source network protocol that is used to connect local or remote Linux servers to transfer files, make remote backups, remote command execution and other network related tasks via scp or sftp between two servers that connects on secure channel over the network.

SSH Security Tips
SSH Server Security Tips

In this article, I will show you some simple tools and tricks that will help you to tighten your ssh server security. Here you will find some useful information on how to secure and prevent ssh server from brute force and dictionary attacks.

1. DenyHosts

DenyHosts is an open source log-based intrusion prevention security script for SSH servers was written in python programming language that intended to run by Linux system administrators and users to monitor and analyzes SSH server access logs for failed login attempts knows as dictionary based attacks and brute force attacks. The script works by banning IP addresses after set number of failed login attempts and also prevent such attacks from gaining access to server.

DenyHosts Features
  1. Keeps track of /var/log/secure to find all successful and failed login attempts and filters them.
  2. Keeps eye on all failed login attempts by user and offending host.
  3. Keeps watch on each existing and non-existent user (eg. xyz) when a failed login attempts.
  4. Keeps track of each offending user, host and suspicious login attempts (If number of login failures) bans that host IP address by adding an entry in /etc/hosts.deny file.
  5. Optionally sends an email notifications of newly blocked hosts and suspicious logins.
  6. Also maintains all valid and invalid failed user login attempts in separate files, so that it makes easy for identifying which valid or invalid user is under attack. So, that we can delete that account or change password or disable shell for that user.

Read More : Install DenyHosts to Block SSH Server Attacks in RHEL / CentOS / Fedora

2. Fail2Ban

Fail2ban is one of the most popular open source intrusion detection/prevention framework written in python programming language. It operates by scanning log files such as /var/log/secure, /var/log/auth.log, /var/log/pwdfail etc. for too many failed login attempts. Fail2ban used to update Netfilter/iptables or TCP Wrapper’s hosts.deny file, to reject an attacker’s IP address for a set amount of time. It also has a ability to unban a blocked IP address for a certain period of time set by administrators. However, an certain minutes of unban is more enough to stop such malicious attacks.

Fail2Ban Features
  1. Multi-threaded and Highly configurable.
  2. Support for log files rotation and can handle multiple services like (sshd, vsftpd, apache, etc).
  3. Monitors log files and looks for known and unknown patterns.
  4. Uses Netfilter/Iptables and TCP Wrapper (/etc/hosts.deny) table to ban attackers IP.
  5. Runs scripts when a given pattern has been identified for the same IP address for more than X times.

Read More : Install Fail2ban to Prevent SSH Server Attacks in RHEL / CentOS / Fedora

3. Disable Root Login

By default Linux systems are per-configured to allow ssh remote logins for everyone including root user itself, which allows everyone to directly log in to system and gain root access. Despite the fact that ssh server allows a more secure way to disable or enable root logins, it’s always a good idea to disable root access, keeping servers a bit more secure.

There are so many people trying to brute force root accounts via SSH attacks by simply supplying different account names and passwords, one after another. If you are a system administrator, you can check ssh server logs, where you will find number of failed login attempts. The main reason behind number of failed login attempts is having weak enough passwords and that makes sense for hackers/attackers to try.

If you are having strong passwords, then you’re probably safe, however it’s better to disable root login and have regular separate account to log into, and then use sudo or su to gain root access whenever required.

Read More : How to Disable SSH Root Login and Limite SSH Access

4. Display SSH Banner

This is one of the oldest feature available from the beginning of the ssh project, but I’ve hardly seen it is used by anyone. Anyway I feels its important and very useful feature that I’ve used for all my Linux servers.

This is not for any security purpose, but the most greatest benefit of this banner is that it is used to display ssh warning messages to UN-authorized access and welcome messages to authorized users before the password prompt and after the user logged in.

Read More : How to Display SSH & MOTD Banner Messages

5. SSH Passwordless Login

A SSH Password-less login with SSH keygen will establish a trust relationship between two Linux servers which makes file transfer and synchronization much easier. This is very useful if you are dealing with remote automated backups, remote scripting execution, file transfer, remote script management etc without enter passwrod each time.

Read More : How to Set SSH Passwordless Login

If you liked this article, then do subscribe to email alerts for Linux tutorials. If you have any questions or doubts? do ask for help in the comments section.

If You Appreciate What We Do Here On TecMint, You Should Consider:

TecMint is the fastest growing and most trusted community site for any kind of Linux Articles, Guides and Books on the web. Millions of people visit TecMint! to search or browse the thousands of published articles available FREELY to all.

If you like what you are reading, please consider buying us a coffee ( or 2 ) as a token of appreciation.

Support Us

We are thankful for your never ending support.

19 thoughts on “5 Best Practices to Secure and Protect SSH Server”

  1. Great Practice, Thanks for Guiding. Cloudways is also integrated Whitelist IP in their Platform. It automatically block bot login attempts.

  2. While this won’t stop malicious users, it’s advised to put in place. An instructor from a Cisco training that I was in attendance of stated that there have been multiple instances where a “hacker” has gotten off free for their crimes due to the fact that there was nothing anywhere on the server stating that the “hacker” or anybody else for that matter, were not allowed to access the server.

    Sure, they’re still going to get access if they want it, but it holds up a lot better in the Judicial system. Every since hearing that, I have set banners and MOTD on every server that I am in charge of because why not? They take just a few seconds to copy and paste in, and could save you some trouble when it comes to court proceeding… then again, I deal with customers who have A LOT to lose.

  3. “4. Display SSH Banner” — huh?
    I guess you think putting a sign on your car that says “it is illegal to steal me” will stop auto-thieves too?
    As long as your at it, you might include the sentence “it is illegal to do things that are against the law” too. That’ll help!


Got something to say? Join the discussion.

Have a question or suggestion? Please leave a comment to start the discussion. Please keep in mind that all comments are moderated and your email address will NOT be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.