Patrick Sletvold

<p><strong>Content Security Policy Manager</strong> is a WordPress plugin that allows you to easily configure <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP" rel="nofollow ugc">Content Security Policy headers</a> for your site. You can have different CSP headers for the admin interface, the frontend for logged in users, and the frontend for regular visitors. The CSP directives can be individually enabled, and each policy can be set to enforce, report or be disabled.</p>
<p>Please note that this plugin offers limited help in figuring out what the contents of the policy should be. It only lets you configure the CSP in a easy to use interface.</p>


Content Security Policy Manager

Plugin for configuring Content Security Policy headers for your site. Allows different CSP headers for admin, logged inn frontend and regular visitors

bluetriangle

<p>SeaSP Community Edition is an automated <strong>Content Security Policy Manager</strong>. SeaSP allows you to create, configure, manage, and deploy a Content Security Policy for your site.</p>
<p>The WordPress SeaSP Community Edition plugin catalogs the domains that appear on your site. Categorize and filter out unwanted domains. Add a layer of WordPress security site from Magecart and other cross-site scripting attacks to keep your WordPress site safe.</p>
<p>SeaSP installs a strict non-blocking CSP to collect violation data and provide a violation report. Violation data flows into the WordPress database as a PHP option within the plugin options schema. Violations can be approved by domains and categorized by directives (CSS, fonts, images, JS, etc.). You can also approve base domains and subdomains. The SeaSP UI helps users by explaining what each directive does, and how to use them to create a CSP.</p>
<p>After configuring the domain and directive settings switch the CSP to blocking mode. Once the CSP goes into blocking mode, the site’s protected from any unrecognized code. SeaSP Community Edition helps secure your site.</p>
<h3>Upgrade Notice for 1.4 only</h3>
<ul>
<li>When you install this version you will need to rebuild your CSP</li>
</ul>
<h3>Usage</h3>
<p>Once installed, a strict non-blocking report-only CSP is implemented on your site. Visit each page of your site to collect CSP violations.<br />
Visit the Current Violations page of the plugin to review domains that have violated a directive in the CSP.<br />
Review each of the domains carefully and check for misspellings of common domains like adobee.com instead of adobe.com as this is a common way hackers inject content into your site.<br />
If you feel confident that the domain belongs on your site and it should be serving the file type stated, click the toggle to approve the domain to include it in the CSP.<br />
If you want to allow subdomains of that domain to be able to serve that type of content, click the Manage subdomains button to view the subdomains.<br />
After this process, you might still see CSP violations regarding inline scripts, inline styles, blobs, or data.<br />
To allow these this type of content in the community version you must navigate to the Directive Settings page, find the offending directive, then toggle the appropriate option.<br />
For convenience, each option has a tooltip explaining what it allows in your CSP.</p>
<h3>Walk Through</h3>
<p>A walk through video can be found on YouTube <a href="https://youtu.be/XdJNh6LEKJw" rel="nofollow ugc">here</a>.</p>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/XdJNh6LEKJw?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<h3>Contributing</h3>
<p>Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.<br />
This project has been tested on WordPress up to version 5.8 on both single and multi-site instances.<br />
The project can be found on <a href="https://github.com/blue-triangle-tech/sea-sp-community-edition" rel="nofollow ugc">github</a>.<br />
This project is sponsored by <a href="www.bluetriangle.com" rel="nofollow ugc">Blue Triangle</a>.</p>
<h3>Third Party Libraries</h3>
<p>We use <a href="https://getbootstrap.com/" rel="nofollow ugc">Bootstrap</a> for the UI of our plugin to make the interface clean and simple.<br />
Bootstraps license can be found <a href="https://github.com/twbs/bootstrap/blob/main/LICENSE" rel="nofollow ugc">here</a></p>
<p>We use <a href="https://www.bootstraptoggle.com/" rel="nofollow ugc">bootstrap toggle</a> because simple check boxes can be confusing and we wanted our CSP mangers UI to feel easy. This code was developed for The New York Times by <a href="https://github.com/minhur" rel="nofollow ugc">Min Hur</a> and is licensed under <a href="https://opensource.org/licenses/MIT" rel="nofollow ugc">MIT</a></p>
<h3>License</h3>
<p><a href="https://choosealicense.com/licenses/gpl-3.0/" rel="nofollow ugc">GNU</a></p>
<h3>Opt In usage data collection</h3>
<p>As of version 1.5 users will be able to opt-in for data collection to help us determine how many people are using our plugin and what features we should be working on in future version. This can be managed in the Usage Data Settings page. We collect and send the following data:<br />
1. wordpress version<br />
2. wordpress debug mode<br />
3. wordpress multisite<br />
4. the base url that the plugin is on ex; www.bluetriangle.com<br />
This data is only accessible to the Blue Triangle organization and will be used to determine our user base and feature planning.</p>


SeaSP Community Edition

SeaSP Community Edition is an automated Content Security Policy Manager. SeaSP allows you to create, configure, manage, and deploy a Content Security  …

Content Security Policy Manager vs SeaSP Community Edition