Fail2ban is an intrusion prevention framework, which works together with a packet-control system or firewall installed on your Cloud Server and is commonly used to block connection attempts after a number of failed tries.
It operates by monitoring log files for certain types of entries and runs predetermined actions based on its findings. You can install the software with the following
sudo apt-get install fail2ban
Once installed, copy the default jail.conf file to make a local configuration with this command
sudo cp /etc/fail2ban/jail.conf /etc/fail2ban/jail.local
Then open the new local configuration file for edit with your favourite text editor, for example
sudo nano /etc/fail2ban/jail.local
Scroll down to go through some of the settings available in the configuration file.
First up are the basic defaults for ignoreip, which allows you to exclude certain IP addresses from being banned, for example, if your own computer has a fixed IP you can enter it here. Next set the bantime which determines how long an offending host will remain blocked until automatically unblocked. Lastly check the findtime and maxretry counts, of which the find time sets the time window for the max retry attempts before the host IP attempting to connect is blocked.
[DEFAULT] ignoreip = 127.0.0.1 bantime = 3600 findtime = 600 maxretry = 3
If you have a sendmail service configured on your cloud server, you can enable the email notifications from Fail2ban by entering your email address into the parameter destemail and changing the action = %(action_)s to action = %(action_mw)s.
Once you’ve done the basic configurations, check the different jails available in the configuration options. Jails are the rules which fail2ban applies to any given application or log file. SSH jail settings, which you can find at the top of the jails list, are enabled by default and not commented out.
[sshd] port = ssh logpath = %(sshd_log)s backend = %(sshd_backend)s
You can enable or disable other jail modules in the same fashion.
When you’ve enabled all the jails you wish, save the configuration file and exit the editor. Then you’ll need to restart the monitor with the following command
sudo systemctl restart fail2ban.service
With that done, you should now check your iptable rules for the newly added jail sections on each of the application modules you enabled.
sudo iptables -L
Any banned IP addresses will appear in the specific chains where the failed login attempts occurred at. You can also manually ban and unban IP addresses from the services you defined jails for with the following commands.
sudo fail2ban-client set <jail> banip/unbanip <ip address> # For example sudo fail2ban-client set sshd unbanip 18.104.22.168
Fail2ban is a handy addition to the iptables and firewall access control in general, feel free to experiment with the configuration and don’t worry if you get your own IP address banned, you can always log in through the web Console at your UpCloud Control Panel to unban yourself afterwards.