Configure various security-related HTTP headers, including Content Security Policy, Feature Policy, Referrer Policy and more. For CSP and XSS plugin supports report logging with 2 additional database tables to store reports from browsers.
Supported security headers
The plugin has support for following HTTP headers:
- Content Security Policy (CSP) – with reporting
- XSS Protection (XXP) – with reporting
- Feature Policy (Permissions Policy)
- Content Type – No Sniff Policy
- Strict Transport Security
- Referrer Policy
- Frame Options
For CSP, the plugin allows you to set rules for all currently supported directives, additional settings including setting the policy in Report or Live mode. The plugin also includes special extensions that can automatically fill CSP rules for popular Google services you might be using on your website (Fonts, Maps, Adsense, Analytics, TagManager and more) and other popular services (Gravatar, Instagram, PayPal Vimeo and more).
And, for Feature Policy (or Permissions Policy), the plugin allows you to set rules for all currently supported rules (over 25 rules, supported by different browsers).
Permissions Policy rules list includes ‘interest-cohort’ rule that can be used to disable Google’s new tracking method called ‘Federated Learning of Cohorts’ or ‘FLoC’.
Methods for adding headers
The plugin can add all the generated headers into HTACCESS file (for Apache web servers), and they will be applied to all files, not just WordPress generated content. If your website is not using Apache (or .HTACCESS), all rules are generated with each page request and will work with any server type.
And, if you don’t use Apache web server, plugin has a panel where it displays generated headers for most popular servers: Apache, Nginx and IIS, and you can copy generated headers to add to server configuration files.
About the plugin
- PHP: 7.2 or newer
- Plugin doesn’t work with PHP 7.1 or older versions.
- WordPress: 5.3 or newer
- Plugin doesn’t work with WordPress 5.2 or older versions.
- Plugin folder in the WordPress plugins folder must be
gd-security-headersfolder to the
- Activate the plugin through the ‘Plugins’ menu in WordPress.
Does plugin works with WordPress MultiSite installations?
Yes. In Multisite installation, the plugin is available for configuration on the Network level, and headers are configured for all sites in the network at once.
Where can I configure the plugin?
The plugin has own top-level item in the WordPress admin side menu: GD Security Headers. This will open a panel with global plugin settings. In Multisite installation, plugin panel is in the Network administration.
Can I translate the plugin to my language?
Yes. The POT file is provided as a base for translation. Translation files should go into Languages directory.
Contributors & Developers
“GD Security Headers” is open source software. The following people have contributed to this plugin.Contributors
Interested in development?
- New: system requirements: PHP 7.3 or newer
- New: tested with WordPress 6.0 to 6.3
- Edit: various improvements to display escaping and sanitation
- Edit: various improvements to the core code
- Edit: d4pLib 2.8.15
- Fix: reflected XSS vulnerability with error message handling
- New: tested with WordPress 6.0
- New: system requirements: PHP 7.2 or newer
- New: system requirements: WordPress 5.3 or newer
- New: tested with WordPress 5.9
- New: csp addon: send reports to custom log URL
- New: csp addon: support for ‘base-uri’ directive
- New: csp addon: predefined rules list for Instagram
- Edit: csp addon: updated various predefined rules lists
- Edit: csp addon: updated settings information about some rules
- Edit: d4pLib 2.8.14
- Fix: csp addon: few typos in the rules names
- Fix: csp addon: minor issues with saving settings
- New: feature/permissions policy addon: support for ‘interest-cohort’
- New: feature/permissions policy addon: dashboard information widget
- Edit: feature/permissions policy addon: expanded information in the settings panel
- Edit: feature/permissions policy addon: improved values explanations
- Fix: feature/permissions policy addon: few typos in the rules names
- New: csp addon: generate predefined rules for one or more CDN’s
- New: csp addon: predefined rules list for WordPress.org
- New: csp addon: support for ‘prefetch-src’ directive
- New: feature policy addon: support for updated ‘permission-policy’ version
- New: feature policy addon: expanded list of policies that can be included
- Edit: csp addon: improved settings organization showing CSP rule levels
- Edit: feature policy addon: included support information for some policies
- Edit: d4pLib 2.8.13
- Fix: csp addon: problem with generating the rules with ‘all’ basic value
- Fix: feature policy addon: few minor issues with building rules
- Edit: csp addon: expanded some of the google based preset rules
- Edit: d4pLib 2.8.8
- Fix: x-frame policy: invalid headers generated when not using .htaccess
- Fix: strict-transport-security policy: invalid headers generated when not using .htaccess
- Fix: referer policy: invalid headers generated when not using .htaccess
- Fix: feature policy: problem printing empty policy header
- New: support for feature policy header
- New: csp addon: predefined rules list for Google YouTube
- New: csp addon: predefined rules list for Google Tag Manager
- New: csp addon: predefined rules list for Gravatar
- New: csp addon: predefined rules list for Gleam
- New: csp addon: predefined rules list for Vimeo
- New: csp addon: auto generated rules for some special data sources
- Edit: csp addon: expanded some Google based preset rules
- Edit: csp addon: various improvements in the generator
- Edit: d4pLib 2.8.2
- Edit: d4pLib 2.7.6
- Fix: problem with saving the plugin settings in some cases
- New: panel with generated headers for various servers
- New: headers panel: for apache servers
- New: headers panel: for nginx servers
- New: headers panel: for iis servers
- New: new method for building the HTACCESS headers
- Edit: improved additional headers object
- Edit: updated rules for Google Analytics
- Edit: do not run when WordPress runs CRON
- Edit: removed some unused code and strings
- First plugin version