Only recently I’ve started to work with Git, don’t blame me I’m mainly a system administrator not a developer, and one of the things I’ve been asked to setup is a way to have a cloned Git project shared over SSH to a particular group of person that share the same linux group. The issue [...]
Article By Stanton Levens
Let face it, the Secure Shell (SSH) daemon running on your VPS is the most sensitive service open to attack on your system. Any hacker worth their salt will first try to gain access to your VPS via SSH and 99.9% of all VPS connected to the internet run this service by default and on their public IP.
If somebody gains access to your VPS via the SSH service, you can kiss your data and entire VPS goodbye. This is the ultimate goal for any would-be hacker and as such, needs to be the first thing you secure as a VPS administrator.
In this article I’m going to show you how to take three simple precautions with the SSH service that will stop most hackers and script kiddies in their tracks. So what will you learn?
- How and why to change the port SSH listens on
- How to disable password based access to SSH and only allow key based access
- Monitor failed SSH login attempts and automatically block the originating IP using an Intrusion Detection System