{{wiki:Image1}}

Nginx Security Hardening Tips

Based on the wonderful things you have heard about **Nginx**, perhaps you decided to give it a try. You may have liked it so much that are considering replacing your Apache installations with Nginx after going through some of the articles on the topic that we have published on this site.

If so, I'm sure you will welcome this guide with open arms since we are going to cover **12 tips to increase the security of your Nginx** servers (ranging from keeping Nginx up to date all the way to using using TLS and redirecting HTTP to HTTPS), and you will note that some of them are very similar to what you would do with Apache.

**Don't Miss**:

[[http://www.tecmint.com/apache-security-tips/|13 Apache Web Server Security and Hardening Tips]]
----
[[http://www.tecmint.com/apache-htaccess-tricks/|25 Apache Htaccess Tricks to Secure Apache Web Server]]
----
**Nginx Testing Environment**

We will use the following environment in this guide:

  *Debian GNU/Linux 8.1 (jessie). 
  *IP address: **192.168.0.25** (**tecmintlovesnginx.com**) and 192.168.0.26 (**nginxmeanspower.com**), as described in the IP-based virtual hosts section at 
    *"[[http://www.tecmint.com/nginx-name-based-and-ip-based-virtual-hosts-server-blocks/|How to Setup Name-based and IP-based Virtual Hosts (Server Blocks) with Nginx]]" 
  *Nginx version: nginx/1.6.2. 
  *For your convenience, here is the final configuration file ([[http://pastebin.com/EEvVUJzg|Pastebin link]]). 

With that in mind, let's begin.

**​TIP #1: Keep Nginx up to date**

At the time of this writing, the latest Nginx versions in the CentOS (in **EPEL**) and Debian repositories are **1.6.3** and **1.6.2-5**, respectively.

Although installing software from the repositories is easier than compiling the program from source code, this last option has two advantages: 1) it allows you to build extra modules into Nginx (such as mod_security), and 2) it will always provide a newer version than the repositories (**1.9.9** as of today). The release notes are always available in the Nginx web site.

**Don't Miss**:

[[http://www.tecmint.com/protect-apache-using-mod_security-and-mod_evasive-on-rhel-centos-fedora/|Protect Apache Against Brute Force and DDoS Attacks Using Mod_Security and Mod_Evasive]]
----
**​TIP #2: Remove Unnecessary Modules in Nginx**

To explicitly remove modules from Nginx while installing from source, do:

<code oobas>
# ./configure --without-module1 --without-module2 --without-module3
</code>
For example:

<code oobas>
# ./configure  --without-http_dav_module --withouthttp_spdy_module 
</code>
As you will probably guess, removing modules from a previous Nginx installation from source requires performing the compilation again.

**A word of caution**: Configuration directives are provided by modules. Make sure you don't disable a module that contains a directive you will need down the road! You should check the [[http://nginx.org/en/docs/|nginx docs]] for the list of directives available in each module before taking a decision on disabling modules.

**​TIP #3: Disable server_tokens Directive in Nginx**

The ''server_tokens'' directive tells Nginx to display its current version on error pages. This is not desirable since you do not want to share that information with the world in order to prevent attacks at your web server caused by known vulnerabilities in that specific version.

To disable the ''server_tokens'' directive, set if to off inside a server block:

<code oobas>
server {
    listen       192.168.0.25:80;
    Server_tokens        off;
    server_name  tecmintlovesnginx.com www.tecmintlovesnginx.com;
    access_log  /var/www/logs/tecmintlovesnginx.access.log;
    error_log  /var/www/logs/tecmintlovesnginx.error.log error;
        root   /var/www/tecmintlovesnginx.com/public_html;
        index  index.html index.htm;
}
</code>
Restart nginx and verify the changes:

{{wiki:Image2}}

Hide Nginx Version Information

**​TIP #4: Deny HTTP User Agents in Nginx**

A HTTP user agent is a software that is used for content negotiation against a web server. This also includes malware bots and crawlers that may end up impacting your web server's performance by wasting system resources.

In order to more easily maintain the list of undesired user agents, create a file (''/etc/nginx/blockuseragents.rules'' for example) with the following contents:

<code oobas>
map $http_user_agent $blockedagent {
        default         0;
        ~*malicious     1;
        ~*bot           1;
        ~*backdoor      1;
        ~*crawler       1;
        ~*bandit        1;
}
</code>
Next, place the following line before the server block definition:

<code oobas>
include /etc/nginx/blockuseragents.rules;
</code>
And an if statement to return a 403 response if the user agent string is in the black list defined above:

{{wiki:Image3}}

Disable User Agents in Nginx

Restart nginx, and all user agents whose string matches the above will be blocked from accessing your web server. Replace **192.168.0.25** with your server's IP and feel free to choose a different string for the ''--user-agent'' switch of **wget**:

<code oobas>
# wget http://192.168.0.25/index.html
# wget --user-agent "I am a bandit haha" http://192.168.0.25/index.html 
</code>
{{wiki:Image4}}

Block User Agents in Nginx

**​TIP #5: Disable Unwanted HTTP Methods in Nginx**

Also known as verbs, HTTP methods indicate the desired action to be taken on a resource served by Nginx. For common web sites and applications, you should only allow **GET**, **POST**, and **HEAD** and disable all others.

To do so, place the following lines inside a server block. A **444** HTTP response means an empty response and is often used in Nginx to fool malware attacks:

<code oobas>
if ($request_method !~ ^(GET|HEAD|POST)$) {
   return 444;
}
</code>
To test, use **curl** to send a **DELETE** request and compare the output to when you send a regular **GET**:

<code oobas>
# curl -X DELETE http://192.168.0.25/index.html
# curl -X POST http://192.168.0.25/index.html 
</code>
{{wiki:Image5}}

Disable Unwanted HTTP Requests in Nginx

**​TIP #6: Set Buffer Size Limitations in Nginx**

To prevent buffer overflow attacks against your Nginx web server, set the following directives in a separate file (create a new file named ''/etc/nginx/conf.d/buffer.conf'', for example):

<code oobas>
client_body_buffer_size  1k;
client_header_buffer_size 1k;
client_max_body_size 1k;
large_client_header_buffers 2 1k;
</code>
The directives above will ensure that requests made to your web server will not cause a buffer overflow in your system. Once again, refer to the docs for further details on what each of them does.

Then add an include directive in the configuration file:

<code oobas>
include /etc/nginx/conf.d/*.conf;
</code>
{{wiki:Image6}}

Set Buffer Size in Nginx

**​TIP #7: Limit the Number of Connections by IP in Nginx**

In order to limit the connections by IP, use the ''limit_conn_zone'' (in a http context or at least outside the server block) and limit_conn (in a http, server block, or location context) directives.

However, keep in mind that not all connections are counted - but only those that have a request processed by the server and its whole request header has been read.

For example, let's set the maximum number of connections to ''1'' (yes, it's an exaggeration, but it will do the job just fine in this case) in a zone named addr (you can set this to whatever name you wish):

<code oobas>
limit_conn_zone $binary_remote_addr zone=addr:5m;
limit_conn addr 1;
</code>
{{wiki:Image7}}

Limit Number of HTTP Requests in Nginx

A simple test with [[http://www.tecmint.com/install-varnish-cache-web-accelerator/|Apache Benchmark (Perform Nginx Load)]] where ''10'' total connections are made with ''2'' simultaneous requests will help us to demonstrate our point:

<code oobas>
# ab -n 10 -c 2 http://192.168.0.25/index.html
</code>
See the next tip for further details.

**​TIP #8: Setup Monitor Logs for Nginx**

Once you have performed the test described in the previous tip, check the error log that is defined for the server block:

{{wiki:Image8}}

Nginx Error Log

You may want to use **grep** to filter the logs for failed requests made to the **add**r zone defined in **TIP #7**:

<code oobas>
# grep addr /var/www/logs/tecmintlovesnginx.error.log --color=auto
</code>
{{wiki:Image9}}

Nginx Log Monitoring

Likewise, you can filter the access log for information of interest, such as:

  *Client IP 
  *Browser type 
  *HTTP request type 
  *Resource requested 
  *Server block answering the request (useful if several virtual hosts are logging to the same file). 

And take appropriate action if you detect any unusual or undesired activity.

**​TIP #9: Prevent Image Hotlinking in Nginx**

Image hotlinking happens when a person displays in another site an image hosted on yours. This causes an increase in your bandwidth use (which you pay for) while the other person happily displays the image as if it was his or her property. In other words, it's a double loss for you.

For example, let's say you have a subdirectory named ''img'' inside your server block where you store all the images used in that virtual host. To prevent other sites from using your images, you will need to insert the following location block inside your virtual host definition:

<code oobas>
location /img/ {
  valid_referers none blocked 192.168.0.25;
   if ($invalid_referer) {
     return   403;
   }
}
</code>
Then modify the ''index.html'' file in each virtual host as follows:

|192.168.0.26|192.168.0.25|
|<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8″>
<title>Nginx means power</title>
</head>
<body>
<h1>Nginx means power!</h1>
<img src="http:%%//%%192.168.0.25/img/nginx.png" />
</body>
</html>|<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8″>
<title>Tecmint loves Nginx</title>
</head>
<body>
<h1>Tecmint loves Nginx!</h1>
<img src="img/nginx.png" />
</body>
</html>|

Now browse to each site and as you can see, the image is correctly displayed in **192.168.0.25** but is replaced by a **403** response in **192.168.0.26**:

{{wiki:Image10}}

Disable Nginx Image Hotlinking

Note that this tip depends on the remote browser sending the Referer field.

**​TIP #10: Disable SSL and only Enable TLS in Nginx**

Whenever possible, do whatever it takes to avoid **SSL** in any of its versions and use **TLS** instead. The following ''ssl_protocols'' should be placed in a server or http context in your virtual host file or is a separate file via an include directive (some people use a file named ''ssl.conf'', but it's entirely up to you):

<code oobas>
ssl_protocols       TLSv1 TLSv1.1 TLSv1.2;
</code>
For example:

{{wiki:Image11}}

Disable SSL and Enable TLS in Nginx

**​TIP #11: Create Certificates in Nginx**

First off, generate a key and a certificate. Feel free to use a different type of encryption if you want:

<code oobas>
# openssl genrsa -aes256 -out tecmintlovesnginx.key 1024
# openssl req -new -key tecmintlovesnginx.key -out tecmintlovesnginx.csr
# cp tecmintlovesnginx.key tecmintlovesnginx.key.org
# openssl rsa -in tecmintlovesnginx.key.org -out tecmintlovesnginx.key
# openssl x509 -req -days 365 -in tecmintlovesnginx.csr -signkey tecmintlovesnginx.key -out tecmintlovesnginx.crt
</code>
Then add the following lines inside a separate server block in preparation for the next tip (''http --> https'' redirection) and move the SSL-related directives to the new block as well:

<code oobas>
server {
    listen 192.168.0.25:443 ssl;
    server_tokens off;
    server_name  tecmintlovesnginx.com www.tecmintlovesnginx.com;
    root   /var/www/tecmintlovesnginx.com/public_html;
    ssl_certificate /etc/nginx/sites-enabled/certs/tecmintlovesnginx.crt;
    ssl_certificate_key /etc/nginx/sites-enabled/certs/tecmintlovesnginx.key;
    ssl_protocols       TLSv1 TLSv1.1 TLSv1.2;
}
</code>
In the next tip we will verify how our site is now using a self-signed cert and TLS.

**​TIP #12: Redirect HTTP traffic to HTTPS in Nginx**

Add the following line to the first server block:

<code oobas>
return 301 https://$server_name$request_uri;
</code>
{{wiki:Image12}}

Redirect HTTP to HTTPS in Nginx

The above directive will return a **301** (Moved permanently) response, which is used for permanent URL redirection whenever a request is made to port 80 of your virtual host, and will redirect the request to the server block we added in the previous tip.

The image below shows the redirection and confirms the fact that we are using **TLS 1.2** and **AES-256** for encryption:

{{wiki:Image13}}

Verify TLS Nginx Encryption

**Summary**

In this article we have shared a few tips to secure your Nginx web server. We would love to hear what you think and, if you have other tips that you would like to share with the rest of the community, feel free to let us know by sending us a note using the comment form below.