shasha310

Harden your web applications.
HTTP header fields are components of the header section of request and response messages. The headers define the operating parameters of an HTTP transaction.
Securing HTTP headers will improve the resilience of your web application against many common attacks including those that are on the OWASP top 10 list.
Securing headers can also improve your SEO rank and in addition to preventing websites from being marked as dangerous by browsers and antivirus applications.
Protect sensitive user information and be compliant with privacy regulations. Defend users from stealing private data by protecting website cookies. Use the proper directive such as “secure”, “httponly” and “samesite”, all of those will be applied automatically by “Secure HTTP Headers” plugin.
Secure HTTP Headers will automatically analyze any website and will build up secure headers directives, by the latest best practice.
In addition, Secure HTTP Headers offers fully configurable options, apply or skip any header directive as needed.
Install and activate Secure HTTP Headers with full confidence, the deactivation of this plugin will return your website header directives to their original state.
<h3>Main plugin functionality</h3>
<ol>
<li>
HTTP Strict Transport Security – helps to protect websites against man-in-the-middle attacks and cookie hijacking
</li>
<li>
X-Frame-Options – helps to protect users against ClickJacking attacks
</li>
<li>
X-Content-Type-Options – helps to prevent the browser from MIME-sniffing
</li>
<li>
Referrer-Policy – helps to control how much referrer information should be included with requests
</li>
<li>
Clear-Site-Data – helps to ensure that data is deleted from the browser if the user logs out
</li>
<li>
X-Download-Options – helps to control how IE 8 will handle downloaded HTML files
</li>
<li>
Access-Control-Allow-Origin – helps to ensure whether the response can be shared with requesting code from the given origin
</li>
<li>
Cross-Origin-Embedder-Policy – helps to prevent a document from loading any cross-origin resources that don’t explicitly grant the document permission
</li>
<li>
Permissions-Policy – helps to allow and deny the use of browser features in its own frame, and in content within any iframe elements in the document
</li>
<li>
Cross-Origin-Opener-Policy – helps to protect websites against a set of cross-origin attacks dubbed XS-Leaks
</li>
<li>
Cross-Origin-Resource-Policy – helps to protect websites against speculative side-channel attacks, like Spectre, as well as Cross-Site Script Inclusion attacks
</li>
<li>
X-Permitted-Cross-Domain-Policies – helps to control how cross-domain requests from Flash and PDF documents are handled
</li>
<li>
Cookie Http-Only flag – helps to protect websites against Cross-Site Scripting, or XSS attacks
</li>
<li>
Cookie Secure flag – helps to ensure that cookie is sent over a secure connection
</li>
<li>
Cookie Samesite Lax flag – helps to protect websites against CSRF and XSSI attacks
</li>
<li>
Expect-CT – helps to prevent the use of misissued certificates for a website. Note: The Expect-CT will likely become obsolete in June 2021
</li>
</ol>
<h3>What are the optional extras?</h3>
Magnisec is offering “Secure HTTP Headers enhanced”
A plugin that contains, in addition, an engine that watches and builds in any website changes a CSP – Content Security Policy that is best practice and recommended by all professional securities experts, that mitigate XSS -Cross site Scripting, one of the most common and destructive attacks.
Price: 50$ /year for a domain.
More details and installation <a href="https://magnisec.com" rel="nofollow ugc">here</a>

Secure HTTP Headers

Secure HTTP headers - Essential, and easy.

Marc Armengou

Security Hardener is inspired by the official WordPress hardening guide (Advanced Administration / Security / Hardening). It uses the platform’s standard functions and does not override core. Applies a prudent set of defenses:
<ul>
<li>Security headers: <code>X-Frame-Options</code>, <code>X-Content-Type-Options</code>, <code>Referrer-Policy</code>, <code>Permissions-Policy</code>, <code>COOP/CORP</code>. </li>
<li>HSTS (optional; HTTPS only). </li>
<li>Basic nonce-based CSP (optional; requires testing). </li>
<li>Disable XML-RPC and pingbacks (optional; enabled by default). </li>
<li>Hide the WordPress version in the <code><head></code>. </li>
<li>Block user enumeration via <code>/?author=</code> by returning 404. </li>
<li>Generic login errors (prevents information leakage). </li>
<li>IP-based login rate limiting with transients (configurable threshold and window). </li>
<li>Restrict the REST API to authenticated users, with a minimal allowlist for oEmbed/index.</li>
</ul>
<blockquote>
⚠️ Important: The restrict REST API option and CSP can affect integrations and plugins. Test it in staging first.
</blockquote>
Privacy: the plugin does not send data to external services or create new tables. It only uses transients to count failed login attempts.

Security Hardener

Basic hardening: secure headers, enumeration blocking, generic login errors, IP-based rate limiting, and optional restriction of the REST API.

Secure HTTP Headers vs Security Hardener