Warning: This page has not been updated in over over a year and may be outdated or deprecated.
administration:security:content_security_policy
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
administration:security:content_security_policy [2020/06/29 12:14] – created demiankatz | administration:security:content_security_policy [2024/04/11 13:51] (current) – demiankatz | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Content Security Policy ====== | ====== Content Security Policy ====== | ||
- | :!: // This feature was introduced in VuFind | + | :!: // This feature was introduced in VuFind® |
HTTP responses can include a Content Security Policy header which provides restrictions on the behavior of the client in order ot provide improved security. VuFind supports the creation of CSP headers to restrict web browser behavior and prevent common security vulnerabilities such as cross-site scripting. | HTTP responses can include a Content Security Policy header which provides restrictions on the behavior of the client in order ot provide improved security. VuFind supports the creation of CSP headers to restrict web browser behavior and prevent common security vulnerabilities such as cross-site scripting. | ||
- | You can learn more at the [[https:// | + | You can learn more at the Mozilla Developer Resources pages about [[https:// |
+ | ===== Configuring VuFind®' | ||
+ | |||
+ | ==== Configuration File ==== | ||
+ | |||
+ | All settings related to Content Security Policies can be found in [[https:// | ||
+ | |||
+ | ==== Enforcing vs. Reporting ==== | ||
+ | |||
+ | The CSP can be configured to either block violating content, or simply to report problems. VuFind® is set to reporting mode by default to avoid backward compatibility breaks. | ||
+ | |||
+ | === Receiving Reports === | ||
+ | |||
+ | When in reporting mode, you can set the report-to setting in [[https:// | ||
+ | |||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | |||
+ | All violations are usually reported in browser' | ||
===== Best Practices / Recommendations ===== | ===== Best Practices / Recommendations ===== | ||
- | // Details coming soon. // | + | Here are some tips and recommendations: |
+ | |||
+ | * By default, VuFind® is set up to be fairly permissive about which scripts it will execute; if you are not using any options that rely on external scripts, or if you can reliably eliminate the use of non-HTTPS files, you should consider applying more restrictive settings than the defaults. | ||
+ | * By default, VuFind® assumes that all CSS styles, images and fonts will be served up locally; if you are using any services (like Google fonts for example) or customizations that pull these resources in from third-party sites, you will need to set up more permissive settings. | ||
+ | * Consider setting up a reporting server (see tool options listed above) so you can test whether any pages of your site are violating your CSP; once you have determined that the site is working as expected, you should change ' | ||
---- struct data ---- | ---- struct data ---- | ||
+ | properties.Page Owner : | ||
---- | ---- | ||
administration/security/content_security_policy.1593432872.txt.gz · Last modified: 2020/06/29 12:14 by demiankatz