HTTP Security Headers are perhaps the most overlooked way to protect visitors on your WordPress websites. But they’re one of the most powerful.
HTTP Headers tell web browsers what they can and cannot do with your website.
This is important, as it can protect your visitors from malicious content loaded from 3rd parties, as well as high-jacking (aka ClickJacking) your website.
We’ll outline what HTTP Headers are, and what we’re doing to help lock down your site. All the while never making things complicated for you or your visitors.
Sound too good to be true? Don’t worry, our clients are already used to this. 😉
TL;DR: Secure Your WordPress With HTTP Security Headers
If you don’t have time to read the whole article, just install/upgrade your Shield installation to the latest version and you’ll have a new module in there called ‘HTTP Headers’.
Turn it on and leave the settings at default for the most compatible configuration. You should rigorously test your site once this is activated as one size definitely does not fit all.
Also, see for yourself: securityheaders.io
Scan your site both before and after you activate the HTTP Headers module to see the difference.
What are HTTP Headers?
In particular, the headers we’re referring to are the HTTP Response headers – this is the information sent out by your website when a visitor makes a request to load a page from your site.
The HTTP Response Headers are directives about the page that is about load. Some of things covered in here are:
- the time/date of the response
- the protocol used
- the (error) code
- content caching directives
- the server handling the response
- cookies for the client/browser
- … loads more
This information is used to direct how the browser will interpret, store, cache and use the forthcoming content.
Wouldn’t it be great if we could also send some security-related directive in here too? Well now we can…
( To dig further into Headers and understand the technical aspects of this better, please see this explanation from tutsplus.com.)
HTTP Security Headers – what are they and why use them?
HTTP Security Headers are a relatively new development which is why you wont see other security plugins implement these (yet).
They’re designed to protect site visitors. This helps in the event that the original website gets hacked or hijacked. It’s incredibly useful since no matter how much protection you put in place on your site, hacks can and do still occur. But what if you could safeguard your visitors that bit further in the event of such as breach?
The HTTP security headers in question here protect your visitors from a wide range of attacks including ClickJacking, Cross-Site Scripting, Cross-Site Injection.
Shield Security plugin for WordPress implements HTTP Security Headers
From v5.3.0 onward of the Shield Security plugin, you have the ability to set certain HTTP Security Headers.
The particular headers available are:
The X-Frame-Options header improves the protection of web applications against ClickJacking. It lets you direct a web browser as to whether your site content may be displayed/embedded within frame on another web page e.g. through the use of iFrames ( <iframe> ).
Certain browsers come with XSS (Cross-site scripting) protection built into them. These may, for whatever, be on or off and you now have the control to explicitly turn on this extended browser protection.
This is by-far the most powerful, and the most complex, of the security headers available. In essence it allows you to dictate which resources, files, etc. can be loaded/processed by the browser.
Our implementation of this policy covers the so-called “default” directive, so it covers all types of assets, whether it’s images, scripts, objects, or styles etc. Since most WordPress websites will use 3rd party themes, use of this is header is limited, but we’ve provided an implementation that lets you make full use of it. This is a huge feature and full implementation is quite advanced. We’ve provided a starter configuration that you can use to build upon and create your own robust policy.
To dig into these particular security headers a little more, you can read a further summary on this over at KeyCDN here.
Important: With ShieldPRO v10.2, we’ve decided to completely remove many of the CSP options from the Shield plugin, for reasons we outline in this blog post here.
Why are Security Headers not featured in other security plugins?
Our mandate is to build security that works to protect your WordPress sites and your visitors. We’re not restricted to implementing features that only other plugin developers do because it’s en vogue or we want to make a special Pro version. But you’ll probably find that in-time, they’ll implement this feature too since it make good sense and more people will start talking about it.
But by the time that happens, it might already be too late 😉
Who wants to spend hours on security? Shield is easy to setup and gives me more time to do what I really want to – develop the site. Thanks so much for this awesomely useful plugin!
Beats WordFence, especially on price
I run a number of private or not for profit sites where security is needed but budgets are tight, so Shield is the perfect antidote to WordFence. Easy to configure and the pro version is not a rip off. I had it installed on 4 sites. Unfortunately I had to…
With all the options this protction tool can be adjusted to the need of many other plugins and still deliver protection. I’m rolling it out on all my sites.