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 applies WordPress security best practices based on the <a href="https://developer.wordpress.org/advanced-administration/security/hardening/" rel="nofollow ugc">WordPress Advanced Administration / Security / Hardening</a> documentation and widely accepted hardening measures. It uses WordPress core functions and follows best practices without modifying core files.
<h4>Key Features</h4>
File Security: 
* Disable file editor in WordPress admin 
* Optionally disable all file modifications (blocks updates – use with caution)
XML-RPC Protection: 
* Disable XML-RPC completely (enabled by default) 
* Remove pingback methods when XML-RPC is enabled
Pingback Protection: 
* Disable self-pingbacks 
* Remove X-Pingback header 
* Block incoming pingbacks
User Enumeration Protection: 
* Block <code>/?author=N</code> queries (returns 404) 
* Secure REST API user endpoints (require authentication) 
* Remove users from XML sitemaps 
* Prevent canonical redirects that expose usernames 
* Optionally block author feed pages (<code>/author/username/feed/</code>)
Login Security: 
* Generic error messages (no username/password hints) 
* Login honeypot — silently blocks bots before any credential check 
* IP-based rate limiting with configurable thresholds 
* Security event logging (last 100 events) 
* Automatic blocking after failed attempts
Security Headers: 
* <code>X-Frame-Options: SAMEORIGIN</code> (clickjacking protection) 
* <code>X-Content-Type-Options: nosniff</code> (MIME sniffing protection) 
* <code>Referrer-Policy: strict-origin-when-cross-origin</code> 
* <code>Permissions-Policy</code> (restricts geolocation, microphone, camera) 
* Optional HSTS (HTTP Strict Transport Security) for HTTPS sites — max-age set to 1 year
Additional Hardening: 
* Hide WordPress version (meta generator tag and asset query strings) 
* Remove obsolete wp_head items (RSD, WLW manifest, shortlink, emoji scripts) 
* Security event logging system 
* Optionally disable Application Passwords for API authentication
<blockquote>
⚠️ Important: Always test security settings in a staging environment first. Some features may affect third-party integrations or plugins.
</blockquote>
Privacy: This plugin does not send data to external services and does not create custom database tables. It stores plugin settings and a security event log in the WordPress options table, and uses transients for temporary login attempt tracking. All data is preserved on uninstall by default and only deleted if the “Delete all data on uninstall” option is explicitly enabled.

Security Hardener

Basic hardening: secure headers, login honeypot, user enumeration blocking, generic login errors, rate limiting, and more.

Secure HTTP Headers vs Security Hardener