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.

Shankaranand Maurya

This plugin is used to protect the content.Content protection is done by three ways :
<ul>
<li>Content protection by logged in user.</li>
<li>Content protection by password.</li>
<li>Content protection by User roles.</li>
</ul>
It will works for any post, page and custom post type also.
Feature :
<ul>
<li>You can add content protection module on any page,post or custom post type.</li>
<li>You can apply any one mechanism or all in one post.</li>
<li>
When content will protected then a message will displayed.Now you can update the message from admin area.
Follow : Settings => wp content protection .
</li>
</ul>
<a href="https://shankaranandmaurya.wordpress.com/my-developed-plugin/wp-content-protection/" rel="nofollow ugc">Click here </a> for plugin settins.
New Feature :
I have added the two new Feature.
1: Using by shortcode :
<blockquote>`[wpcp_content_protection is_logged_in=’#enter 0 or 1 #’ is_password=’#enter password#’ is_user_roles=’#enter editor roles#’]…….. content …..[/wpcp_content_protection] `</blockquote>
For more detailed describe of all the paramater, how can we use, please visit .<a href="https://shankaranandmaurya.wordpress.com/my-developed-plugin/wp-content-protection/wp-content-protection-by-shortcode/" rel="nofollow ugc">Click Here</a>
2: By using functions
print this function :
<blockquote>` echo wpcp_protection_with_advanced_custom_field(‘#Enter customfield key#’,’#Enter value 0 or 1#’,’#enter editor roles#’,’#enter password#’);`</blockquote>
For more detailed describe of all the paramater, how can we use, please visit .<a href="https://shankaranandmaurya.wordpress.com/my-developed-plugin/wp-content-protection/wp-content-protection-by-shortcode/" rel="nofollow ugc">Click Here</a>
2.1 : For password security : <a href="https://shankaranandmaurya.wordpress.com/my-developed-plugin/wp-content-protection/wp-content-protection-feature-password-protection/" rel="nofollow ugc">click here </a>
For any doubts, please email me with my email id : shankranand.mca@gmail.com : or visit :https://shankaranandmaurya.wordpress.com:

WP Content Protection

WP Content Protection plugin is used to protect the content.No membership required for this protection.

Security Hardener vs WP Content Protection