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.

Guido Schad

Lockora Security Audit helps site owners and agencies review a WordPress site’s security posture from the admin area.
Current prototype features include:
<ul>
<li>Manual security scans.</li>
<li>Weighted security score out of 100.</li>
<li>WordPress core file integrity checks using official checksums.</li>
<li>WordPress authentication key and salt checks, with an explicit action to generate missing salts.</li>
<li>Must-use plugin directory presence checks.</li>
<li>PHP version status using WordPress.org Serve Happy data.</li>
<li>HTTPS and HTTP security header checks.</li>
<li>WordPress core, plugin, and theme update posture checks.</li>
<li>Administrator account posture checks for default usernames, excess admins, inactive admins, user ID 1 exposure, and an admin username/email inventory.</li>
<li>Optional known vulnerability matching with a configured Wordfence Intelligence API key.</li>
<li>Optional AI client reports on WordPress 7.0+ when the site’s AI Connector is configured.</li>
<li>Reversible hardening toggles for XML-RPC, REST user routes, generator tag output, and basic security headers.</li>
</ul>
<h3>External Services</h3>
Lockora Security Audit may connect to external services only when the administrator runs a scan or generates an AI client report.
WordPress.org APIs: 
* Used for WordPress core checksums, PHP version support status, and WordPress core/plugin/theme update data. 
* Data sent: the site’s WordPress version and locale for core checksums and PHP compatibility; WordPress itself may send installed plugin and theme slugs/versions to WordPress.org when update data is refreshed. 
* WordPress.org terms: https://wordpress.org/about/terms/ 
* WordPress.org privacy policy: https://wordpress.org/about/privacy/
Wordfence Intelligence: 
* Optional. 
* Used only when a Wordfence Intelligence API key is configured and an administrator runs a scan that includes vulnerability matching. 
* Used to retrieve vulnerability data and match it locally against installed WordPress core, plugin, and theme versions. 
* Data sent: the configured Wordfence Intelligence API key is sent in an Authorization header when requesting the vulnerability feed. Installed software details are not sent by this plugin to the Wordfence Intelligence endpoint; matching is performed locally after the feed is retrieved. 
* Wordfence Intelligence terms: https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/ 
* Wordfence privacy policy: https://www.wordfence.com/privacy-policy/
WordPress AI Client / Connectors: 
* Optional. 
* Used only when the administrator clicks Generate Client Report. 
* Data sent: sanitized scan findings, score, counts, and recommendations needed to generate a client-facing report. The plugin is designed not to send passwords, salts, API keys, raw logs, full user lists, or file contents. 
* The configured AI provider is controlled by the site owner’s WordPress Connector settings. 
* Terms and privacy policy: these depend on the AI provider configured by the site owner in WordPress. Site owners should review the selected provider’s terms and privacy policy before enabling AI reports.

Lockora Security Audit

Lockora Security Audit checks WordPress security posture, hardening, core integrity, vulnerabilities, and optional AI reports.

ShadowScan Security Link vs Lockora Security Audit