bpassini

Easily conform to the EU GDPR by blocking all 3rd party requests.
The aim is to block all unwanted requests as simply as possible. This is made possible by setting the general content security policy.
This plugin also supports some Elementor blocks: 
– block the Google Maps block until visitor excplicitly allows it 
– block the OpenStreetMap block until visitor excplicitly allows it

GDPR Helper using CSP

This plugin allows easy addition of Content Security Policy

thapa.laxman

The idea is quite simple: By sending a CSP header from a website, you are telling the browser what it is authorized to execute and what it is authorized to block. And by doing this, Content Security Policy helps block the XSS vulnerabilities. 
CSP allows a host to specify a whitelist of approved sources that a browser can load content from and is an effective countermeasure for XSS attacks. 
Content Security Policy is delivered via a HTTP response header, much like HSTS, and defines approved sources of content that the browser may load. It can be an effective countermeasure to Cross Site Scripting (XSS) attacks and is also widely supported and usually easily deployed.
CSP Directives 
* default-src: Define loading policy for all resources type in case of a resource type dedicated directive is not defined (fallback), 
* script-src: Define which scripts the protected resource can execute, 
* object-src: Define from where the protected resource can load plugins, 
* style-src: Define which styles (CSS) the user applies to the protected resource, 
* img-src: Define from where the protected resource can load images, 
* media-src: Define from where the protected resource can load video and audio, 
* frame-src: Define from where the protected resource can embed frames, 
* font-src: Define from where the protected resource can load fonts, 
* connect-src: Define which URIs the protected resource can load using script interfaces, 
* form-action: Define which URIs can be used as the action of HTML form elements, 
* sandbox: Specifies an HTML sandbox policy that the user agent applies to the protected resource, 
* script-nonce: Define script execution by requiring the presence of the specified nonce on script elements, 
* plugin-types: Define the set of plugins that can be invoked by the protected resource by limiting the types of resources that can be embedded, 
* reflected-xss: Instructs a user agent to activate or deactivate any heuristics used to filter or block reflected cross-site scripting attacks, equivalent to the effects of the non-standard X-XSS-Protection header, 
* report-uri: Specifies a URI to which the user agent sends reports about policy violation
<h3>Written By</h3>
This plugin was written by Laxman Thapa, <a href="lakshman.com.np" rel="nofollow ugc">Web Developer</a>.

Content Security Policy Pro

This Content Security Policy plugin will help the setup the Content-Security-Policy HTTP response header and block the XSS vulnerabilities.

GDPR Helper using CSP vs Content Security Policy Pro