Guard Dog vs SiteFort Security – Malware Scanner, Firewall, Login Security & Hardening

Guard Dog is a focused WordPress security plugin for the login door, authentication, sessions, and practical access workflows. With custom login URLs, two-factor authentication, passkeys, CAPTCHA providers, access control, and activity logging, Guard Dog helps site owners tighten the parts of WordPress that get bothered most. Key Features: Custom Login URLs – Hide your wp-admin and wp-login.php from attackers Two-Factor Authentication (2FA) – TOTP-based authentication with recovery codes Social Login (OAuth) – Sign in with Google, Microsoft, or Apple Passkeys – Use device-based biometric authentication like Face ID, Touch ID or Windows Hello Multiple CAPTCHA Providers – Support for Google reCAPTCHA v2/v3, hCaptcha, and Cloudflare Turnstile Login Attempt Limiting – Prevent brute-force attacks with intelligent lockout Access Control – IP-based whitelist/blacklist protection Activity Monitoring – Comprehensive logging of security events Temporary User Access – Create temporary WordPress users with time-limited, secure access Frontend Account Security – Shortcodes and blocks for login, passkeys, 2FA, and session controls Why Choose Guard Dog? Privacy-Focused – Multiple CAPTCHA options including privacy-first providers WordPress.org Compliant – Built following WordPress coding standards Site-Owned Controls – Protections run inside your WordPress site User-Friendly – Intuitive interface with helpful documentation Regular Updates – Actively maintained and updated Perfect For: Business websites requiring enhanced security WordPress sites handling sensitive data Multi-user sites with complex access requirements Anyone wanting practical login and account protection without a central SaaS dependency Frontend Shortcodes: [guard_dog_login_form] renders a public Guard Dog-managed login form [guard_dog_passkey_login] renders a standalone passkey sign-in button for custom login pages [guard_dog_two_factor] renders logged-in 2FA management [guard_dog_passkeys] renders logged-in passkey management [guard_dog_sessions] renders logged-in active-session management [guard_dog_account_security] renders the composite logged-in account security widget for 2FA, passkeys, and sessions [guard_dog_2fa] remains supported as the legacy alias for the account security widget Block-based themes can use the matching Guard Dog Login Form, Passkey Login, Two-Factor Auth, Passkeys, Sessions, and Account Security blocks. Additional Information Support: For support questions, please use the WordPress.org support forums. Privacy: Guard Dog respects user privacy and offers multiple privacy-focused options. Third-party services are only contacted when you enable features that need them, such as CAPTCHA, email delivery, social login, IP reputation, or geolocation. Security: Guard Dog follows WordPress security best practices. User input is sanitized and output is escaped throughout the plugin. Third-Party Services Guard Dog integrates with the following third-party services to provide CAPTCHA protection. These services are optional and only used when CAPTCHA features are enabled. Google reCAPTCHA (v2 and v3) What it is: Google’s CAPTCHA service that helps protect websites from spam and abuse. What it’s used for: – Verifying that login, registration, and password reset attempts are made by humans – Preventing automated bot attacks on your WordPress forms What data is sent and when: – User interaction data (mouse movements, time spent on page) when CAPTCHA is solved – IP address of the user – Site domain for verification – CAPTCHA response token Privacy and Terms: – Google reCAPTCHA Privacy Policy – Google reCAPTCHA Terms of Service – Google reCAPTCHA Data Usage Cloudflare Turnstile What it is: Cloudflare’s privacy-first CAPTCHA alternative that doesn’t require user interaction. What it’s used for: – Invisible verification of human users during login, registration, and password reset – Privacy-focused protection without tracking or cookies What data is sent and when: – Non-interactive browser signals when forms are submitted – IP address for verification – Site domain for validation Privacy and Terms: – Cloudflare Privacy Policy – Cloudflare Terms of Service – Turnstile Documentation hCaptcha What it is: A privacy-focused CAPTCHA service that doesn’t track users across websites. What it’s used for: – Human verification during login, registration, and password reset forms – Privacy-conscious alternative to Google reCAPTCHA What data is sent and when: – User interaction with CAPTCHA challenge – IP address for verification – Site domain for validation Privacy and Terms: – hCaptcha Privacy Policy – hCaptcha Terms of Service – hCaptcha Data Processing Google OAuth (Social Login) What it is: Google’s OAuth 2.0 service that allows users to sign in using their Google account. What it’s used for: – Authenticating WordPress users via their Google account – Retrieving basic profile information (name, email) to link or create accounts What data is sent and when: – User is redirected to Google’s authorization server when clicking “Sign in with Google” – An authorization code is exchanged for an access token on your server – Basic profile information (name, email, Google user ID) is retrieved from Google’s API – No ongoing data sharing – data is only retrieved during the login process Privacy and Terms: – Google OAuth Privacy Policy – Google OAuth Terms of Service – Google API Services User Data Policy Microsoft Azure AD (Social Login) What it is: Microsoft’s OAuth 2.0 service via Azure Active Directory that allows users to sign in using their Microsoft account. What it’s used for: – Authenticating WordPress users via their personal Microsoft account or organizational (work/school) account – Retrieving basic profile information (name, email) to link or create accounts What data is sent and when: – User is redirected to Microsoft’s authorization server when clicking “Sign in with Microsoft” – An authorization code is exchanged for an access token and ID token (JWT) on your server – Basic profile information (name, email, Azure object ID) is extracted from the ID token – No ongoing data sharing – data is only retrieved during the login process Privacy and Terms: – Microsoft Privacy Statement – Microsoft Services Agreement – Microsoft Identity Platform Documentation Apple Sign In (Social Login) What it is: Apple’s OAuth 2.0 / OpenID Connect service that allows users to sign in using their Apple ID. What it’s used for: – Authenticating WordPress users via their Apple ID – Retrieving basic profile information (name, email) to link or create accounts What data is sent and when: – User is redirected to Apple’s authorization server when clicking “Sign in with Apple” – An authorization code is exchanged for an access token and ID token (JWT) on your server – Basic profile information (email, user ID) is extracted from the ID token – User’s name is only provided on first authorization; subsequent logins return only the user ID – Apple may provide a private relay email address instead of the user’s real email – No ongoing data sharing – data is only retrieved during the login process Privacy and Terms: – Apple Privacy Policy – Sign in with Apple Guidelines – Apple Developer Program License Agreement TOTP (Time-based One-Time Password) Standard What it is: An open standard (RFC 6238) for generating time-based one-time passwords used in two-factor authentication. What it’s used for: – Generating secure, time-limited authentication codes for 2FA – Providing backup authentication when primary 2FA methods are unavailable – Enabling compatibility with popular authenticator apps (Google Authenticator, Authy, Microsoft Authenticator, etc.) What data is sent and when: – No external data transmission – TOTP codes are generated locally using the TOTP algorithm – Secret key generation – A unique secret key is generated locally when 2FA is enabled for a user – QR code generation – QR codes are generated locally for easy setup with authenticator apps – Code verification – Generated codes are verified locally against the stored secret key Privacy and Terms: – RFC 6238 – TOTP Standard – Google Authenticator Privacy Policy (if using Google Authenticator app) – Authy Privacy Policy (if using Authy app) – Microsoft Authenticator Privacy Policy (if using Microsoft Authenticator app) Data Handling Summary When CAPTCHA is disabled: No data is sent to any third-party services. When CAPTCHA is enabled: Only the specific provider you choose receives verification data. Data is not shared between providers or stored by Guard Dog beyond the verification process. When 2FA is disabled: No external data transmission occurs. When 2FA is enabled: – All TOTP operations (code generation, verification) happen locally on your server – No data is transmitted to external services for 2FA functionality – Authenticator apps only receive the initial setup QR code or secret key – Recovery codes are generated locally and stored securely When Social Login is disabled: No data is sent to any OAuth provider. When Social Login is enabled: – Data is only sent to the configured providers (Google, Microsoft, Apple) during the login process – Only basic profile information (name, email, user ID) is retrieved – Social account links are stored locally in your WordPress database – Users can unlink their social accounts from their profile at any time User control: Users can choose which CAPTCHA provider to use, or disable CAPTCHA entirely. 2FA can be enabled/disabled per user, and users can choose their preferred authenticator app. Social login can be enabled/disabled by administrators, and users can manage their linked social accounts. All security features are optional and configurable.

SiteFort is a prevention-first WordPress security plugin that combines security hardening, firewall and bot protection, login security and 2FA, vulnerability scanning, and malware detection in one protection layer. It blocks common attack paths early, before they turn into compromises, while supported firewall rules can sync to Cloudflare for enforcement at the edge. SiteFort’s cloud-assisted malware scanner verifies trusted files by hash and sends only unknown or suspicious files for deep threat analysis, keeping scans reliable even on shared and lower-resource hosting. Security hardening, firewall protection, login security, 2FA, and vulnerability scanning are free forever. Try the Live Demo | Features | Try Online Scanner Core WordPress Security Features WordPress Security Hardening: Reduces common exposure through XML-RPC, user enumeration, sensitive files, direct PHP execution, REST access, security headers, and other WordPress security controls. Firewall & Bot Protection: Blocks vulnerability probes, abusive requests, malicious traffic, and unwanted automation with IP, country, rate limiting, and configurable bot controls. Supported rules can also sync to Cloudflare for edge enforcement. Login Security & 2FA: Protects WordPress login, WooCommerce customer accounts, and membership account access with two-factor authentication, CAPTCHA, brute-force lockouts, a custom login URL, breached-password checks, and password policies. Vulnerability Scanner: Checks WordPress core, plugins, and themes for known vulnerabilities, affected versions, severity, CVE references where available, and remediation guidance. Cloud-Assisted Malware Scanner: Detects backdoors, web shells, injected code, malicious redirects, SEO spam, and suspicious file changes, with deep threat analysis in the cloud to reduce server load. Compromise & Reputation Checks: Detects suspicious administrator accounts, injected content, unsafe URLs, exposed sensitive files, malicious redirects, and domain or server reputation issues. WordPress Security Hardening SiteFort provides simple, toggle-based WordPress hardening controls to reduce common security exposure and shrink the attack surface. Sensitive File Protection: Blocks public access to WordPress configuration backups, database dumps, debug logs, backup files, installer files, and other sensitive resources, including exposed .env or .git data when present. PHP Execution Protection: Blocks PHP execution in uploads and restricts direct access to PHP files in plugin and theme directories. XML-RPC Controls: Disable XML-RPC, restrict authentication, or block pingback abuse. User Enumeration Blocking: Reduces username exposure through author archives, REST endpoints, and common discovery paths. REST & Application Password Controls: Restricts REST API access and controls WordPress Application Passwords based on site requirements. File Editor Protection: Disables the built-in WordPress theme and plugin file editor. Directory Browsing Protection: Disables directory listing to reduce file discovery and unintended information exposure. Security Headers: Analyze and manage CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, and disclosure headers. Version & Metadata Cleanup: Reduces exposed WordPress version, generator, and header information. Protection Verification: Confirms supported hardening protections are active and identifies items that require manual hosting or server configuration. WordPress Malware Scanner SiteFort combines hash-first file verification with cloud-assisted deep threat analysis to detect malware while reducing scan workload on the WordPress server. Hash-First File Verification: Known WordPress core, plugin, and theme files are verified against trusted hashes. Deep Threat Analysis: Files that cannot be verified by hash or show suspicious indicators are sent to the SiteFort cloud for deep threat analysis, including backdoors, web shells, injected PHP or JavaScript, malicious redirects, SEO spam, and obfuscated code. File Integrity: Detects modified WordPress core, plugin, and theme files, along with unexpected files that do not belong in trusted packages. Account & Content Checks: Checks administrator accounts, WordPress content, options, URLs, and redirects for suspicious changes and indicators of compromise. Sensitive File Exposure: Identifies publicly accessible backups, logs, configuration files, debug files, and other sensitive files commonly targeted by attackers. Domain & IP Reputation: Checks the site domain and server IP against supported blocklists and abuse intelligence. Database and content checks run on the protected site and are not uploaded to the SiteFort cloud. Login Security & 2FA SiteFort protects WordPress login and account access against brute-force attacks, credential abuse, and unauthorized access. Brute-Force & CAPTCHA Protection: Limits repeated login attempts and adds CAPTCHA protection to WordPress, WooCommerce, and supported custom login and registration forms. Two-Factor Authentication: Adds role-based 2FA with authenticator apps, email codes, recovery codes, grace periods, and trusted devices. WooCommerce & Membership 2FA: Lets customers and members manage 2FA from WooCommerce My Account or supported custom account pages. Custom Login URL: Move the WordPress login page to a private URL and control requests to the default wp-login.php address. Password Security: Detects weak and breached passwords, enforces password strength, prevents reuse, and supports optional expiration policies. WordPress Firewall SiteFort filters malicious and abusive traffic early, with clear controls for IPs, countries, rate limits, sensitive paths, bots, and optional Cloudflare edge enforcement. IP, CIDR & Country Rules: Block or allow individual IP addresses, CIDR ranges, and countries, including an allow-only mode. Sensitive Path Probe Protection: Blocks requests probing for commonly targeted sensitive paths, including WordPress configuration backups, database dumps, debug logs, installer files, .env, and .git. Rate Limiting & 404 Controls: Reduces abusive request bursts, repeated missing-page requests, and automated scanning activity. Bot & User-Agent Controls: Block or allow selected bots, crawlers, scanners, and user agents with configurable firewall rules. Community Threat Intelligence: Blocks known malicious IPs identified across the SiteFort network, helping stop repeat bad actors before they reach the site. Vulnerability Probe Protection: Blocks automated requests searching for vulnerable plugins, themes, backup files, and configuration leaks. Cloudflare Sync: Synchronizes supported IP, country, and user-agent rules to Cloudflare, with temporary edge blocks for repeat attackers where supported. Traffic Log: Review firewall traffic, blocked requests, bot activity, rate-limit events, and rule matches from the firewall dashboard. Bot Protection Policy SiteFort provides three bot protection presets for straightforward setup, with the option to allow or block specific bots and crawlers individually. Basic: Blocks known hacking tools and bots probing for vulnerable files and common attack paths. Balanced: Adds protection against scraping bots and automated scripts. Recommended for most WordPress sites. Maximum: Extends filtering to unrecognized bot traffic for sites that require stricter automation controls. AI Training Crawlers: Optionally block training-focused crawlers such as GPTBot, ClaudeBot, CCBot, and Bytespider while supported AI assistants and AI search crawlers remain allowed. Supported search crawlers are verified using reverse DNS and published IP ranges and are allowed through bot protection, while bots impersonating known search engines are detected and blocked. Vulnerability Scanner SiteFort checks installed WordPress core, plugins, and themes against vulnerability intelligence and identifies affected versions, severity, and available remediation. Affected Components: Identifies vulnerable WordPress core, plugins, and themes with installed versions, severity, and CVE references where available. Fix Guidance: Shows fixed versions and recommended actions when remediation information is available. Vulnerability Probe Protection: Firewall controls block automated discovery attempts targeting vulnerable plugins, themes, and known component paths while affected software is being updated, replaced, or removed. SiteFort does not virtually patch vulnerable code. Vulnerable components should be updated, replaced, or removed using the available remediation guidance. Malware Repair & Quarantine Delete or Quarantine (Free): Remove malicious or unwanted files from scan results, with optional quarantine for recovery when needed. One-Click Repair (Pro): Repairs malicious or modified files directly from scan results when a trusted clean source is available. Clean-File Restore (Pro): Restores supported WordPress core, plugin, and theme files, including selected commercial plugins and themes when verified clean sources are available. For active WordPress compromises requiring hands-on investigation, Securewp expert cleanup is available for malware removal, root-cause remediation, blocklist assistance, and post-cleanup review. WordPress Security Audit Log SiteFort records important security and administrative activity, providing a clear history for review and investigation. Login Activity: Successful and failed logins, lockouts, 2FA events, and account-related activity. User Changes: User creation, updates, role changes, and other account actions. Plugin & Theme Activity: Installations, activations, deactivations, updates, and other recorded changes. Security & Settings Changes: Hardening, login security, firewall configuration, and other sensitive administrative changes. SiteFort Console SiteFort Console provides a central panel for managing security across multiple WordPress sites. No separate add-on is required; Console connectivity can be enabled or disabled directly from the SiteFort plugin. Run security scans and review findings across sites. Monitor vulnerabilities and update hardening settings remotely. Review security status, scan history, uptime, and SSL expiry. Route alerts and download reports for individual sites or clients. Manage team access and support workflows from one place. All site-level security features remain available directly in WordPress; Console adds centralized management for multiple sites. Hosting Compatibility SiteFort supports shared hosting, managed WordPress hosting, VPS, and dedicated servers across Apache, Nginx, and LiteSpeed. Cloudflare: Works with Cloudflare-proxied sites and supports optional firewall rule sync for edge enforcement. Lower-Resource Hosting: Hash-first file verification and cloud-assisted deep analysis reduce scan workload on the hosting server. Flexible Server Support: Does not require a specific web server stack or managed hosting environment. Free vs Pro SiteFort Free includes security hardening, firewall and bot protection, login security and 2FA, vulnerability scanning, activity logging, and 3,000 monthly cloud scan credits. Pro removes the cloud analysis limit and adds automation, repair, monitoring, alerts, and reporting. SiteFort Pro adds: Unlimited deep threat analysis Scheduled malware scans and automated vulnerability alerts One-click malware repair and clean-file restore Uptime and SSL expiry monitoring Slack, Discord, email, and webhook alerts Remote scan history and detailed security reports White-label options for agencies Managed adds hands-on monitoring, incident response workflows, and expert cleanup coverage from the Securewp team. See the WordPress Security Plugin Comparison for a feature-by-feature comparison with other WordPress security plugins. External services SiteFort uses external services only for features that require them, including license activation, cloud-assisted malware analysis, vulnerability and firewall intelligence, reputation checks, optional Console sync, CAPTCHA, GeoIP, Cloudflare Sync, and administrator-configured notifications. Optional integrations are not contacted unless they are enabled or used. SiteFort Cloud Servers: securewp.net, intel.securewp.net, console.securewp.net Used for: License activation, service metadata, cloud malware analysis, vulnerability intelligence, firewall intelligence, reputation checks, community blocklist sync, clean-file repair, and optional Console sync. Data sent: Email address, license key or token, site URL, WordPress and plugin versions, installed plugin and theme names and versions, file hashes, scan results, vulnerability findings, reputation status, firewall metadata, blocked IP addresses, and security configuration metadata. Malware scanning: File hashes are sent first. Only unknown or suspicious files may be uploaded for deeper analysis and are deleted after processing. Database and content checks run on the protected site and are not uploaded to the SiteFort cloud. If wp-config.php requires analysis, sensitive configuration values are removed before upload. Temporary storage: SiteFort Cloud may return temporary *.amazonaws.com upload or download URLs for malware analysis or clean-file repair. Privacy: https://securewp.net/privacy-policy/ Terms: https://securewp.net/terms-and-conditions/ Storage provider policies: AWS privacy https://aws.amazon.com/privacy/ and terms https://aws.amazon.com/service-terms/; Cloudflare privacy https://www.cloudflare.com/privacypolicy/ and terms https://www.cloudflare.com/website-terms/ Optional integrations MaxMind GeoLite2 (download.maxmind.com): Used only when an administrator downloads or updates the local GeoIP database. The configured MaxMind account ID and license key are sent to MaxMind. Visitor IP addresses are resolved locally and are not sent to MaxMind during normal requests. Privacy: https://www.maxmind.com/en/privacy-policy Terms: https://www.maxmind.com/en/geolite2/eula Have I Been Pwned Passwords (api.pwnedpasswords.com): Used for breached-password checks when enabled. SiteFort sends only the first 5 characters of the SHA-1 password hash. Full passwords and full hashes are not sent. Privacy: https://haveibeenpwned.com/Privacy Terms: https://haveibeenpwned.com/TermsOfUse Google reCAPTCHA (www.google.com) and Cloudflare Turnstile (challenges.cloudflare.com): Used only when selected and configured for CAPTCHA protection. The selected provider receives the challenge token, site key, and visitor or browser data required to process the challenge. Policies: https://policies.google.com/privacy https://policies.google.com/terms https://www.cloudflare.com/turnstile-privacy-policy/ https://www.cloudflare.com/website-terms/ Cloudflare API (api.cloudflare.com): Used only when Cloudflare Sync is enabled. SiteFort sends the Zone ID, API token or credentials, zone details, blocked IP addresses, country rules, selected user-agent rules, and firewall rule data required for synchronization. Privacy: https://www.cloudflare.com/privacypolicy/ Terms: https://www.cloudflare.com/website-terms/ Notification webhooks: Security alerts may be sent to Slack (hooks.slack.com), Discord (discord.com, discordapp.com), or a custom HTTPS webhook configured by the administrator. Payloads may include site name, site URL, event type, severity, scan counts, vulnerability names, CVE identifiers, firewall counts, usernames, IP addresses, browser names, action URLs, timestamps, and event details. Slack policies: https://slack.com/trust/privacy/privacy-policy https://slack.com/terms-of-service/user Discord policies: https://discord.com/privacy https://discord.com/terms Local site checks Some SiteFort checks send loopback requests to the protected site’s own public URL, including security-header checks, public-file exposure checks, and homepage link collection. These requests contact the protected site itself, not a third-party service.