Skip to main content

Hardening the Linux server - Part 3

<< Part 2                                                                                                    Part 4 >>
Hardening the Linux server - Part 3



Write firewall rules
You can deny access to your server through your firewall. Ubuntu Server uses a firewall called Uncomplicated FireWall (UFW), which is actually a management tool for iptables. Iptables filters network packets based on a series of rules written by the system administrator. Iptables can be complicated for beginners, so UFW simplifies it. Using UFW can help you harden your server; but if you're truly interested in server security, learning how to write rules for iptables will let you fine-tune a server's security.
To get started with UFW, you need to install it. Follow these steps:
  1. From the command line, type sudo aptitude install ufw
  2. Press Enter and enter your password. Press Enter again to install the package.
  3. To enable the firewall, type the following: sudo ufw enable
  4. Press Enter. You see the message Firewall started and enabled on system startup. Now you can create rules for your firewall.
Remember how you changed the port for SSH earlier? To open the port through UFW by creating a rule, type the following at the command line:
# sudo ufw allow 65000
That command allows access over port 65000 and lets SSH traffic into your server.
To deny access over this port, use the following:
# sudo ufw deny 65000
To allow or deny traffic specifically on TCP port 65000, use the following command:
# sudo ufw allow 65000/tcp
You can also allow or deny traffic according by the protocol it uses. For instance, to block all HTTP traffic, you can use this command:
# sudo ufw deny http
You can create more complicated rules to deny or allow a service based on its IP address. For instance, if your desktop had the IP address 192.168.1.30 and your server had an IP address of 192.168.1.5, you could allow only your computer's IP address the ability to establish an SSH connection:
# sudo ufw allow proto tcp from 192.168.1.30 to 192.1681.5 port 65000
To check which rules you're currently running with UFW, use
# sudo ufw status
You're presented with a list of rules you've written for your firewall. If you see a rule that you wish to delete, type
# sudo delete [rule]

<< Part 2                                                                                                                 Part 4 >>

Labels:

Comments

Post a Comment

Popular posts from this blog

Virtual Box and Alt/Tab Keys

I use virtual box for all my testing activities. It comes too often that I have a virtual box VM window open & I want to switch to my host machine to see some stuff like tutorials etc.. If you press the alt+tab combination it just works inside the VM & doesn't switches to host machine. In these scenarios you can press the host key once ( not hold it ) & then whatever you press goes to host machine. So in general where host key is the default Right Ctrl, just press Right Ctrl once & now press the alt+tab & it will switch you out to host machine. This is really helpful when you have the VM windows open or you're working on seamless mode. Hope it help others too.
4 comments
Read more

CentOS / Redhat : Configure CentOS as a Software Router with two interfaces

Linux can be easily configured to share an internet connection using iptables. All you need to have is, two network interface cards as follows: a) Your internal (LAN) network connected via eth0 with static ip address 192.168.0.1 b) Your external WAN) network is connected via eth1 with static ip address 10.10.10.1  ( public IP provided by ISP ) Please note that interface eth1 may have public IP address or IP assigned by ISP. eth1 may be connected to a dedicated DSL / ADSL / WAN / Cable router: Step # 1: Enable Packet Forwarding Login as the root user. Open /etc/sysctl.conf file # vi /etc/sysctl.conf Add the following line to enable packet forwarding for IPv4: net.ipv4.conf.default.forwarding=1 Save and close the file. Restart networking: # service network restart Step # 2: Enable IP masquerading In Linux networking, Network Address Translation (NAT) or Network Masquerading (IP Masquerading) is a technique of transce...
4 comments
Read more

Create a SSL Certificate for Apache on CentOS 6

About Self-Signed Certificates A SSL certificate is a way to encrypt a site's information and create a more secure connection. Additionally, the certificate can show the virtual private server's identification information to site visitors. Certificate Authorities can issue SSL certificates that verify the virtual server's details while a self-signed certificate has no 3rd party corroboration. Step One—Install Mod SSL In order to set up the self signed certificate, we first have to be sure that Apache and Mod SSL are installed on our VPS. You can install both with one command: yum install mod_ssl Step Two—Create a New Directory Next, we need to create a new directory where we will store the server key and certificate mkdir /etc/httpd/ssl Step Three—Create a Self Signed Certificate When we request a new certificate, we can specify how long the certificate should remain valid by changing the 365 to the number of da...
Post a Comment
Read more