Secure Apache from Clickjacking with X-FRAME-OPTIONS

Implement X-FRAME-OPTIONS in HTTP headers to prevent Clickjacking attacks

Clickjacking is a well-known web application vulnerabilities.

For example, it was used as an attack on Twitter.

To defense the Clickjacking attack on your Apache web server, you can use X-FRAME-OPTIONS to avoid your website being hacked from Clickjacking.

The X-Frame-Options in HTTP response header can be used to indicate whether or not a browser should be allowed to open a page in frame or iframe.

This will prevent site content embedded into other sites.

Did you every try embed Google.com on your website as a frame? You can’t because it’s protected and you can protect it too.

There are three settings for X-Frame-Options:

SAMEORIGIN: This setting will allow a page to be displayed in a frame on the same origin as the page itself.
DENY: This setting will prevent a page displaying in a frame or iframe.
ALLOW-FROM uri: This setting will allow a page to be displayed only on the specified origin.

Note: – you may also use Content Security Policy header to control how you want your site content to be embed. Refer this article for CSP header.

Implement in Apache, IBM HTTP Server

Header always append X-Frame-Options SAMEORIGIN

If your website is hosted on shared web hosting, then you won’t have permission to modify httpd.conf.

However, you can achieve this by adding the following line in the .htaccess file.

Header append X-FRAME-OPTIONS "SAMEORIGIN"

Change is reflected immediately without doing any restart.

You can use any web developer tool to view Response headers. You can also use an online tool – Header Checker to verify.

How did it go?

If you are running an online business, then you may consider using Cloud WAF for all-in-one security protection and monitoring.