There really isn’t much that’s more important than securing your web server when launching a website. Most of your development tasks are completed (hopefully), your designs are wonderful, and your designers are excited to finally get this project off their plate. So how do we go about securing our web server after launch?
Today, I’ll be talking specifically about the Apache2 web server. The particular flavour of Linux OS that I’ll be addressing is Ubuntu 16.04 (Debian also) considering it seems to be one of the most frequently used web servers today. There are some minor file location differences with RHEL/CentOS/Fedora, though not major. There are other tutorials addressing the particulars floating around. So I won’t include them here.
I’ll be using my favourite command line text editor Vim, but feel free to replace any vim
command with nano
if you’re more familiar with. I’ll include some basic information to help you through using Vim if you’re unfamiliar.
Shut-out Server Specification: Hide Your Server Version and OS Details
When hitting a server display page like a directory listing or a 404, you may notice that there exists a small colophon reading your servers version, IP, and Port. You can get rid of this tidbit of revealing data by changing some code in your Apache2 configuration files.
Type sudo vim /etc/apache2/apache2.conf
to edit the file.
You may quickly notice a nice little message describing that your configuration file has been split for simplicity at the top. Always read documentation!
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.
# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |-- apache2.conf
# | `-- ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf-enabled
# | `-- *.conf
# `-- sites-enabled
# `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
# together by including all remaining configuration files when starting up the
# web server.
#
# * ports.conf is always included from the main configuration file. It is
# supposed to determine listening ports for incoming connections which can be
# customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
# directories contain particular configuration snippets which manage modules,
# global configuration fragments, or virtual host configurations,
# respectively.
#
# They are activated by symlinking available configuration files from their
# respective *-available/ counterparts. These should be managed by using our
# helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
# their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
# the default configuration, apache2 needs to be started/stopped with
# /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
# work with the default configuration.
The actual file will be located in a separate configuration folder. Press esc
to enter command mode and type :q
or :q!
if you accidentally changed the file to exit the file in Vim.
Type sudo vim /etc/apache2/conf-enabled/security.conf
to edit the file containing security features.
Look for the string ServerSignature
by typing /ServerSignature
in Vim command mode (press esc
at any time to enter command mode). You can use the arrow keys or h
,j
,k
, and l
to move your cursor left, down, up, and right respectively in command mode.
press i
to enter text edit mode. This is the mode that you will be most familiar with when typing using a keyboard. Press esc
to go back into command mode.
Change the following variables as follows:
ServerSignature Off
ServerTokens Prod
Once you’re done editing the file, enter command mode (esc
) and type :wq
to write the file and quit. If you’ve messed up the file, feel free to :q!
to forcefully quit the file and ignore all changes as :q
may not do the job alone. Typing u
in command mode will undo any changes you’ve recently made as well, if that suits you better.
Once you’re back in the Ubuntu command line, restart the server by typing sudo service apache2 restart
Now when you visit the same 404 or directory listing page, you won’t be seeing that server signature! Congrats on completing step one!
Disable Detailed Directories: Hide Directory Listing and Files
Your Apache2 server will want to list out all the directories and files if you don’t have a base index.html or index.php (or other if specified in Apache2) in your directory. You can hide this functionality by adding a simple line of code to your apache2.conf file.
Type sudo vim /etc/apache2/apache2.conf
to edit the base configuration file and hide directories from all sites located in your web folder.
Type /Directory /var/www/html
to find the code you need to edit. It should be a block that looks like this:
<Directory /var/www/html>
AllowOverride All
</Directory>
Just below AllowOverride All
you’ll want to add Options -Indexes
. You should end up with this.
<Directory /var/www/html>
AllowOverride All
Options -Indexes
</Directory>
Once you’ve changed your code, :wq
out of the file and restart your server with sudo service apache2 restart
. Once you hit a directory, you’ll now find a message forbidding you from accessing that folder. Congrats on completing step 2!
Write Where We’re Willed: Web Server File Permissions
Web servers are left open to hackers when using open file permissions (777
or -rwxrwxrwx
/ drwxrwxrwx
). It’s important to make sure that your web server is given proper permissions to access and write directories, without opening them to hackers and visitors.
One simple way to do this is to disable write and execution tags where applicable in the permissions for folders and files. Permissions use binary triplets to turn on and off permissions. First, the base ten digit is converted to binary, and those positions turn on and off file and folder features.
To change all directories within your web folder to 755
(rwxr-xr-x
):
find /var/www/html -type d -exec chmod 755 {} \;
To change all files within your web folder to 644
(rw-r--r--
):
find /var/ww/html -type f -exec chmod 644 {} \;
These permissions not only work well for statically built websites, but also for content management systems like Magento and WordPress.
Updating Ubuntu: Specifically Apache2
Updating your server, and specifically updating Apache2 is very important. You’ll want to make sure you’re updating regularly to make sure the most important security patches have been applied.
Firstly you’ll want to update your package information by using sudo apt-get update
If you’d simply like to install updates for Apache2, just type sudo apt-get install apache2
. You should be returned a message that looks something like the following.
Reading package lists... Done
Building dependency tree
Reading state information... Done
apache2 is already the newest version (2.4.18-2ubuntu3.3).
0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
As you can see, I have 21 packages that are not upgraded on my server. If you’d like to update all of these packages, you can type sudo apt-get upgrade.
If you’d rather view the packages that need updating and install them one by one (using a command similar to the one for apache2), you can do so by typing sudo apt-get upgrade --dry-run
or /usr/lib/update-notifier/apt-check -p
for a simpler return.
Conclusion
These are only a few of the many ways you can harden your Apache2 web server. I’ll be adding to and maintaining this list as time passes, but there are a few extra things you’ll want to be sure to check out.
HTTPS and SSL Certificates
You’ll want to make sure that you’re installing SSL Certificates on all of your sites. Whether they’re extended validation or self signed, this can help keep traffic encrypted, and your users feeling safe. There are many other reasons to install SSL, a big reason is that Google promotes sites that use it more than ones that don’t (for obvious reasons). With tools like Lets Encrypt there really is no reason not to install a cert on all of your servers.
Firewalls Firewalls Firewalls
Personally, I like to host on AWS where their console and security features allow for very strict access to your cloud network infrastructure. If you don’t have access to such strong security measures on your own personal server, you’ll want to ensure that you take advantage of the firewall tools available in Ubuntu.
If you have any questions, make sure you comment below!
Cheers,
Cole Speelman