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.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
administration:security:content_security_policy [2020/06/29 18:20] – [Configuring VuFind's CSP] demiankatz | administration:security:content_security_policy [2020/06/29 20:05] – demiankatz | ||
---|---|---|---|
Line 5: | Line 5: | ||
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' | ===== Configuring VuFind' | ||
Line 11: | Line 11: | ||
==== Configuration File ==== | ==== Configuration File ==== | ||
- | All settings related to Content Security Policies can be found in contentsecuritypolicy.ini. | + | All settings related to Content Security Policies can be found in [[https:// |
==== Enforcing vs. Reporting ==== | ==== Enforcing vs. Reporting ==== | ||
Line 19: | Line 19: | ||
=== Receiving Reports === | === Receiving Reports === | ||
- | When in reporting mode, you can set the report-to setting in contentsecuritypolicy.ini to send reports of violations to a URI that implements a simple API. VuFind does not currently include a built-in reporting endpoint, but several options exist, including: | + | When in reporting mode, you can set the report-to setting in [[https:// |
* [[https:// | * [[https:// | ||
Line 25: | Line 25: | ||
===== 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 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 turn off report_only settings for your production site in order to improve security. | ||
administration/security/content_security_policy.txt · Last modified: 2024/04/11 13:51 by demiankatz