Content Security Policy HTTP header is a part of the Shield's HTTP Headers module. It helps you to restrict the sources and types of content that may be loaded and processed by visitor browsers.
In essence it allows you to dictate which resources, files, etc. can be loaded/processed by the browser.
Shield's Content Security Policy Header covers all types of assets, whether it’s images, scripts, objects, or styles etc.
What are the Content Security Policy options?
Important: The following CSP options are no longer available from v10.2.2 and onward. Please see ShieldPRO 10.2 Upgrade Guide here.
Due to the complexity of CSP and the superficial nature of our CSP implementation, we've decided to remove these options. We explore the issue in full detail in our blog post on this topic here.
The Content Security Policy options are as follows:
- Allow 'self' Directive - Resources from your own host:protocol are permitted.
- Allow "data:" Directives - Allows use of embedded data directives, most commonly used for images and fonts.
- HTTPS Resource Loading - Allows loading of any content provided over HTTPS.
- Permitted Hosts and Domains - You can explicitly state which hosts/domain from which content may be loaded. Take great care and test your site as you may block legitimate resources.
- Manual Rules - You can add manual CSP rules which are not covered by the rules above.
How to add custom CSP rules
You can enable CSP headers and use 'Manual Rules' option for this. For example, media files, media-src:
Feel free to provide as many custom Content Security Policy rules as you need to.
Important: There is no validation that your rules are structured correctly, nor whether they’re appropriate for your particular site and circumstances. Great care should be taken when providing your custom rules and advice should be sought from your web developer on what is most appropriate.
To learn more about HTTP Content Security Policy Headers, read the blog article here.
We also recommend you to read: