shadowscan

ShadowScan Security Link gives you ShadowScan Guard local WordPress hardening for plugin auto-updates, username enumeration reduction, version/plugin exposure reduction, sensitive-file blocking, and basic connection/self-check diagnostics.
The plugin supports dual backend pairing with both Guard and ShadowScan. Pair with Guard backend for Guard-specific features, or connect to ShadowScan Portal to sync heartbeat status and unlock managed features for sites with an active Essential or Premium plan, or an approved reviewed pricing path. Basic Hosting can stay hosting-only, while ShadowScan Guard local hardening remains available in the plugin until managed entitlements are active.
Pairing the plugin and enabling remote diagnostics each require an explicit administrator acknowledgment in WP Admin. Those checkpoints are covered by the <a href="https://shadowscan.com.au/plugin-addendum" rel="nofollow ugc">ShadowScan Plugin Addendum</a>.
ShadowScan does not install, activate, or configure third-party security tools. If another security plugin is present, the connector only records its presence as metadata.
<h3>External services</h3>
This plugin can connect to external services to sync status, process security workflows, and support optional diagnostics after an admin pairs the site to ShadowScan.
<ul>
<li>Service: ShadowScan API (hosted at Supabase Edge Functions)</li>
<li>URL: <a href="https://axuhxgeafczsoctlzycz.supabase.co/functions/v1/" rel="nofollow ugc">ShadowScan API</a></li>
<li>Used for: ShadowScan pairing, heartbeat sync, command polling, command-result upload, subscription/policy sync, and support contact submissions.</li>
<li>Data sent and when: site URL, WordPress version, PHP version, connector version, Guard Layer/control status, heartbeat timestamps, and command execution metadata whenever the connector syncs with ShadowScan; contact form fields only when an admin submits support contact.</li>
<li>Terms: <a href="https://shadowscan.com.au/terms" rel="nofollow ugc">shadowscan.com.au/terms</a></li>
<li>Privacy: <a href="https://shadowscan.com.au/privacy" rel="nofollow ugc">shadowscan.com.au/privacy</a></li>
<li>
Plugin Addendum: <a href="https://shadowscan.com.au/plugin-addendum" rel="nofollow ugc">shadowscan.com.au/plugin-addendum</a>
</li>
<li>
Service: Guard API (hosted at Supabase Edge Functions)
</li>
<li>URL: <a href="https://dzaidjskedmlrtyqdobg.supabase.co/functions/v1/" rel="nofollow ugc">Guard API</a></li>
<li>Used for: Guard pairing validation, migration token validation, and Guard backend operations.</li>
<li>Data sent and when: pairing codes, migration tokens, and site metadata only when pairing with Guard backend or processing migration scenarios.</li>
<li>Terms: <a href="https://shadowscan.com.au/terms" rel="nofollow ugc">shadowscan.com.au/terms</a></li>
<li>Privacy: <a href="https://shadowscan.com.au/privacy" rel="nofollow ugc">shadowscan.com.au/privacy</a></li>
<li>
Plugin Addendum: <a href="https://shadowscan.com.au/plugin-addendum" rel="nofollow ugc">shadowscan.com.au/plugin-addendum</a>
</li>
<li>
Service: Have I Been Pwned Passwords API
</li>
<li>URL: <a href="https://api.pwnedpasswords.com" rel="nofollow ugc">api.pwnedpasswords.com</a></li>
<li>Used for: optional breached-password checks in password policy enforcement.</li>
<li>Data sent and when: k-anonymity password hash prefix (first 5 SHA-1 characters, no raw passwords) only when a password is checked by the policy flow.</li>
<li>Terms: <a href="https://haveibeenpwned.com/TermsOfUse" rel="nofollow ugc">haveibeenpwned.com/TermsOfUse</a></li>
<li>
Privacy: <a href="https://haveibeenpwned.com/Privacy" rel="nofollow ugc">haveibeenpwned.com/Privacy</a>
</li>
<li>
Service: Sentry
</li>
<li>URL: <a href="https://sentry.io" rel="nofollow ugc">sentry.io</a></li>
<li>Used for: optional error and fatal-event telemetry to assist troubleshooting.</li>
<li>Data sent and when: error event metadata (such as exception messages, stack traces, and runtime context) only after an admin explicitly enables Sentry telemetry in plugin settings and a Sentry DSN is configured; the optional MU diagnostics helper can send early-startup fatal errors only while both Sentry telemetry and remote diagnostics are enabled.</li>
<li>Terms: <a href="https://sentry.io/terms/" rel="nofollow ugc">sentry.io/terms</a></li>
<li>Privacy: <a href="https://sentry.io/privacy/" rel="nofollow ugc">sentry.io/privacy</a></li>
</ul>
<h3>Third-Party Libraries</h3>
This plugin bundles: 
* <a href="https://github.com/antonioribeiro/google2fa" rel="nofollow ugc">pragmarx/google2fa</a> (MIT License) 
* <a href="https://github.com/Bacon/BaconQrCode" rel="nofollow ugc">bacon/bacon-qr-code</a> (BSD-2-Clause; Copyright (c) 2017-present, Ben Scholzen “DASPRiD”)
<h3>Hooks</h3>
<code>shadowscan_log</code> 
Fires when the plugin emits an internal log message. You can hook this in a must-use plugin or theme if you want to capture logs.

ShadowScan Security Link

ShadowScan Guard local WordPress hardening and basic diagnostics, with optional Guard or ShadowScan portal connection for managed features.

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
XML-RPC Protection: 
* Disable XML-RPC completely 
* 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>) 
* Optionally anonymize the author name in oEmbed responses
Login Security: 
* Generic error messages (no username/password hints) 
* Login honeypot 
* Block unsafe usernames 
* Application Passwords disabled by default 
* IP-based rate limiting with configurable thresholds 
* Security event logging
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) 
* System Status — monitors file permissions, WP_DEBUG, user registration, PHP version, administrator accounts, and database version
<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.

ShadowScan Security Link vs Security Hardener