Enable Security Headers

Security headers can effectively prevent a variety of hacking attempts. Therefore, you should consider headers like Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, or X-XSS-Protection.

Security Assessment

CVSS Vector: AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Vulnerability Information

Security headers can effectively prevent a variety of hacking attempts. You should consider headers like Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, or X-XSS-Protection.

Hot to Enable Security Headers

Use the following guides to set correct security headers for your web application:

• Webserver Configuration (Apache, nginx)
• HTTP Strict Transport Security (HSTS)
• X-Frame-Options
• X-XXS-Protection
• X-Content-Type-Options
• Same-Site Cookie
• Content-Security-Policy
• Referrer-Policy
• Access-Control-Allow-Origin

Webserver Configuration

To configure your webserver to contain all described headers, use the following configurations. Below, you find further descriptions of the single headers.

Apache

On Apache you need to update your configuration to include the correct header directives. Add this to the virtual host configuration in /etc/apache2/sites-enabled/domain.conf or /etc/httpd/sites-enabled/domain.conf:

<VirtualHost *:443>
    Header always set Strict-Transport-Security "max-age=31536000"
    Header always set X-Frame-Options "deny"
    Header always set X-XSS-Protection "1; mode=block"
    Header always set X-Content-Type-Options "nosniff"
    Header always set Content-Security-Policy "default-src 'self'"
    Header always set Referrer-Policy "strict-origin-when-cross-origin"
</VirtualHost>

nginx

On Nginx you need to update your configuration file which is usually located at /etc/nginx/nginx.conf, /etc/nginx/sited-enabled/yoursite.com (Ubuntu / Debian) or /etc/nginx/conf.d/nginx.conf (RHEL / CentOS) to include the correct header with the add_header directives:

server {
    add_header Strict-Transport-Security "max-age=63072000; includeSubdomains;" always;
    add_header X-Frame-Options "deny" always;
    add_header X-XSS-Protection "1; mode=block" always;
    add_header X-Content-Type-Options "nosniff" always;
    add_header Content-Security-Policy "default-src 'self'" always;
    add_header Referrer-Policy "strict-origin-when-cross-origin" always;
}

HTTP Strict Transport Security (HSTS)

The HSTS header enforces HTTPS connections. This prevents downgrade attacks to an insecure HTTP connection. See Enable HSTS for the correct settings.

X-Frame-Options

The X-Frame-Options header declares whether this site may be embedded as a frame into other websites. The values are:

Setting this header e.g. to deny will protects the website against clickjacking attacks where an attacker overlays an iframe of your webpage with arbitrary content to bait his victims in clicking on certain links on your website.

X-XXS-Protection

Some web browsers are shipped with a Cross-Site-Scripting (XSS) filter. This filter can detect certain XSS attacks and prevent them. To configure the browser filter behavior, use the X-XSS-Protection header.

Setting this header e.g. to 1; mode=block will tell the browser that it should not render the webpage in case that it detects an attack.

X-Content-Type-Options

Browsers try to detect the MIME-type of files that are sent by the webserver. If an attacker manages to upload a malicious (executable) file to a webserver, which only sends images, the MIME-type can provide some protection, as it tells the browser that it should expect an image and not an executable file. Therefore, the browser must not try to detect the MIME-type, but only use the webserver provided MIME-type. To enforce this behavior, use the X-Content-Type-Options header and set it to nosniff.

Same-Site Cookie

The Same-Site cookie flag tells the browser to not send cookies along with cross-site requests. This cookie flag prevents the risk of cross-site information leakage and can also help to mitigate Cross-Site Request Forgery attacks. Possible values are Strict, Lax or None. In case the Same-Site cookie flag is set to None the Secure flag must be set, to prevent sending the cookie in an insecure context.

Content-Security-Policy

The Content-Security-Policy (CSP) header tells the browser from which domain further resources such as scripts, images, or stylesheets may be loaded. This can prevent various Cross-Site-Scripting (XSS) and other Cross-Site-Injection attacks. The policy needs to be hand-crafted for the particular usage, as it may easily prohibit analytic scripts, fonts, or other resources that are loaded from a third party.

A very simple and restrictive policy can be: default-src 'self'. Make sure to test your configuration thoroughly as you may not want to block your analytics script or other third-party resources.

Referrer-Policy

The Referrer-Policy header defines how much information about the referrer is sent when the user clicks on a link. The referrer may leak sensitive information such as user-specific URLs. Therefore the referrer-policy might be set to some more restrictive value. A relatively secure setting is strict-origin-when-cross-origin.

Cache-Control

The Cache-Control header defines how caching in the browser is configured. Depending on the value of the header, the browser may cache the website including any sensitive information. For pages, where confidentiality is an issue, the header should be set to no-store.

Access-Control-Allow-Origin

The Access-Control-Allow-Origin Header defines, which applications may consume your API. Consider this article It should be set to the domain of your frontend, such as:

Access-Control-Allow-Origin: https://example.org

If you have multiple applications using your API, please consult this blog article.

For more information about Crashtest Security visit crashtest-security.com