Deze plugin is niet getest met de laatste 3 grotere versies van WordPress. Mogelijk wordt het niet meer onderhouden of ondersteund. Ook kunnen er compatibiliteitsproblemen ontstaan wanneer het wordt gebruikt met recentere versies van WordPress.

Security Headers

Omschrijving

TLS is growing in complexity. Server Name Indication (SNI) now means HTTPS sites may be on shared IP addresses, or otherwise restricted. For these servers it is handy to be able to set desired HTTP headers without access to the web servers configuration or using .htaccess file.

This plug-in exposes controls for:

  • HSTS (Strict-Transport-Security)
  • HPKP (Public-Key-Pins)
  • Disabling content sniffing (X-Content-Type-Options)
  • XSS protection (X-XSS-Protection)
  • Clickjacking mitigation (X-Frame opties in hoofdsite)
  • Expect-CT

HSTS is used to ensure that future connections to a website always use TLS, and disallowing bypass of certificate warnings for the site.

HPKP is used if you don’t want to rely solely on the Certificate Authority trust model for certificate issuance.

Disabling content sniffing is mostly of interest for sites that allow users to upload files of specific types, but that browsers might be silly enough to interpret of some other type, thus allowing unexpected attacks.

XSS protection re-enables XSS protection for the site, if the user has disabled it previously, and sets the “block” option so that attacks are not silently ignored.

“Clickjacking” bescherming is normaal alleen aan de orde als iemand is ingelogd. Echter is deze optie door gebruikers aangevraagd. Waarschijnlijk omdat zij “rich content” willen beschermen die buiten de WordPress Authenticatie valt.

Expect-CT wordt gebruikt om ervoor te zorgen dat de “Certificate Transparency” correct geconfigureerd is.

Installatie

  1. Upload “security_headers.php” naar de “/wp-content/plugins/” folder.
  2. Activeer de plugin via het “Plugins” menu in WordPress.

Beoordelingen

14 mei 2020
Just a quick warning: if you enable this plugin, the Tawk.to widget is no longer displayed in Chrome, Firefox and Safari. Edge is not affected (yet?).
11 februari 2019
Works great and makes security much easier. Thanks for this great plugin!
19 juni 2017
Works really well! Tested with [link removed] For the future releases it would be good to include Content-Security-Policy and the forthcoming Expect-CT options.
Lees alle 8 beoordelingen

Bijdragers & ontwikkelaars

“Security Headers” is open source software. De volgende personen hebben bijgedragen aan deze plugin.

Bijdragers

Vertaal “Security Headers” naar jouw taal.

Interesse in ontwikkeling?

Bekijk de code, haal de SVN repository op, of abonneer je op het ontwikkellog via RSS.

Changelog

1.1

Fix missing close anchor which breaks recent WordPress

1.0

Add support for wp-login.php page

Add support for Expect-CT header

0.9

Removed unnecessary whitespace in HSTS header (thanks Thomas)

Added Referrer-Policy header

Corrected plugins name from “HTTP Headers” to “Security Header” (thanks Jamie)

Removed trailing semi-colon from X-XSS-Protection (it worked but not needed)

0.8

Add headers to admin section of WordPress

Added option to set the X-Frame-Options headers to main site

Added HSTS Preload header (thanks to Jamie)

0.7

Add report-uri

Fix handling of non-numeric blank strings for HPKP max-age

0.6

HPKP support

Check for TLS before emitting HSTS or HPKP headers

0.5

Change h2 for h1 for accessibility per #31650

0.4

License change
Clarify wording for XSS protection in readme

0.3

Prepare for release

0.2

Added Sonarqube file and formatting changes

0.1

  • Eerste release.