Nowadays, protecting our Linux server is very important. Blocking the SSH and FTP access to specific IP addresses and network ranges is a very important step to improve security.<\/p>\n
Let us discuss why we should block the SSH and FTP access on our Linux operating system. We will also talk about two different types of methods to block the SSH and FTP access to specific IP and network ranges in our Linux system.<\/p>\n
For various convincing reasons, blocking the SSH (Secure Shell) and FTP (File Transfer Protocol) access in Linux is critical. First and foremost, security is very important. We limit the attack chances in our Linux by blocking the access and making it less vulnerable. Brute-force attacks and other unwanted access attempts frequently target the SSH and FTP. We prevent these attacks by blocking the access to specific IP and network ranges.<\/p>\n
Second, the regulatory compliance and privacy are the major issues. Many businesses must follow the strict industry or government rules such as GDPR, HIPAA, or PCI DSS. These rules often require the implementation of severe access controls by enterprises.<\/p>\n
Furthermore, we may adjust our server’s security measures to our organization’s specific needs by blocking the SSH and FTP\u00a0access to specified IP addresses or network ranges. This helps us access only the right individuals. We can use these methods since these methods reduce\u00a0the danger of data breaches and ensure a server stability.<\/p>\n
The iptables is an effective tool to control the network security on Linux. It works at the packet level, allowing us to establish the rules for blocking the traffic based on a variety of parameters such as the source and destination IP addresses.<\/p>\n
Let us see the steps on how we can block the SSH and FTP access with the help of iptables.<\/p>\n
We can create our rules by accessing the iptables configuration file which is usually located at \u201c\/etc\/sysconfig\/iptables\u201d or \u201c\/etc\/iptables\/rules.v4\u201d.<\/p>\n
To block the SSH access from a specific IP address, type the following line to the configuration file:<\/p>\n
-A INPUT -s 192.168.2.101 -p tcp –destination-port 22 -j DROP<\/p>\n
To block the FTP access, we have to input a similar line for the FTP port:<\/p>\n
-A INPUT -s 192.168.2.101 -p tcp –destination-port 21 -j DROP<\/p>\n
After adding these rules, we have to save the configuration file and restart the \u201ciptables\u201d service.<\/p>\n
We have to type the following command to apply these changes:<\/p>\n
Another way to block the SSH and FTP access is using the TCP Wrappers. TCP Wrappers is a simple yet the best host-based network access control method. The TCP Wrappers is integrated with SSH and FTP, both simplifying the process. We can easily manage them by changing these two important files: \u201c\/etc\/hosts.allow\u201d and \u201c\/etc\/hosts.deny\u201d.<\/p>\n
To block the access to specific IP and network range, we need to open the \u201c\/etc\/hosts.deny\u201d file using any text editor.<\/p>\n
Then, we have to type two lines to block a specific incoming SSH connection.<\/p>\n
To block the FTP access, we have to type the following lines in the same file:<\/p>\n
Finally, we have to restart the SSH and FTP services. Now, the SSH and FTP access are blocked to some IP and Networks.<\/p>\n
We can restart SSH by typing the following commands in our terminal:<\/p>\n
We can restart FTP by typing the following commands in our terminal:<\/p>\n
The SSH and FTP access from the hosts with the IP address of 192.168.2.101 and the network range of 192.168.2.0 will be blocked.<\/p>\n
Linux gives us various methods for personalized access control such as iptables or TCP Wrappers. We can easily reduce the vulnerabilities and the risk of unauthorized access by blocking the SSH and FTP access to specific IP addresses and network ranges. It is a good security practice that makes maintaining our server very simple.<\/p>","protected":false},"excerpt":{"rendered":"
Practical guide on the two different types of methods to block the SSH and FTP access to specific IP and network ranges in our Linux system along with examples.<\/p>","protected":false},"author":111,"featured_media":23553,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1049],"tags":[],"class_list":["post-23548","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux-commands"],"_links":{"self":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/23548","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/users\/111"}],"replies":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/comments?post=23548"}],"version-history":[{"count":0,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/23548\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/media\/23553"}],"wp:attachment":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/media?parent=23548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/categories?post=23548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/tags?post=23548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}