Guard Dog vs Two Factor

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.

The Two-Factor plugin adds an extra layer of security to your WordPress login by requiring users to provide a second form of authentication in addition to their password. This helps protect against unauthorized access even if passwords are compromised. Setup Instructions Important: Each user must individually configure their two-factor authentication settings. For Individual Users Navigate to your profile: Go to “Users” → “Your Profile” in the WordPress admin Find Two-Factor Options: Scroll down to the “Two-Factor Options” section Choose your methods: Enable one or more authentication providers (noting a site admin may have hidden one or more so what is available could vary): Authenticator App (TOTP) – Use apps like Google Authenticator, Authy, or 1Password Email Codes – Receive one-time codes via email Backup Codes – Generate one-time backup codes for emergencies Dummy Method – For testing purposes only (requires WP_DEBUG) Configure each method: Follow the setup instructions for each enabled provider Set primary method: Choose which method to use as your default authentication Save changes: Click “Update Profile” to save your settings For Site Administrators Plugin settings: The plugin provides a settings page under “Settings → Two-Factor” to configure which providers should be disabled site-wide. User management: Administrators can configure 2FA for other users by editing their profiles Security recommendations: Encourage users to enable backup methods to prevent account lockouts Available Authentication Methods Authenticator App (TOTP) – Recommended Security: High – Time-based one-time passwords Setup: Scan QR code with authenticator app Compatibility: Works with Google Authenticator, Authy, 1Password, and other TOTP apps Best for: Most users, provides excellent security with good usability Backup Codes – Recommended Security: Medium – One-time use codes Setup: Generate 10 backup codes for emergency access Compatibility: Works everywhere, no special hardware needed Best for: Emergency access when other methods are unavailable Email Codes Security: Medium – One-time codes sent via email Setup: Automatic – uses your WordPress email address Compatibility: Works with any email-capable device Best for: Users who prefer email-based authentication FIDO U2F Security Keys Deprecated and removed due to loss of browser support. Dummy Method Security: None – Always succeeds Setup: Only available when WP_DEBUG is enabled Purpose: Testing and development only Best for: Developers testing the plugin Important Notes HTTPS Requirement All methods work on both HTTP and HTTPS sites Browser Compatibility TOTP and email methods work on all devices and browsers Account Recovery Always enable backup codes to prevent being locked out of your account If you lose access to all authentication methods, contact your site administrator Security Best Practices Use multiple authentication methods when possible Keep backup codes in a secure location Regularly review and update your authentication settings For more information about two-factor authentication in WordPress, see the WordPress Advanced Administration Security Guide. For more history, see this post. Actions & Filters Here is a list of action and filter hooks provided by the plugin: two_factor_providers filter overrides the available two-factor providers such as email and time-based one-time passwords. Array values are PHP classnames of the two-factor providers. two_factor_providers_for_user filter overrides the available two-factor providers for a specific user. Array values are instances of provider classes and the user object WP_User is available as the second argument. two_factor_enabled_providers_for_user filter overrides the list of two-factor providers enabled for a user. First argument is an array of enabled provider classnames as values, the second argument is the user ID. two_factor_user_authenticated action which receives the logged in WP_User object as the first argument for determining the logged in user right after the authentication workflow. two_factor_user_api_login_enable filter restricts authentication for REST API and XML-RPC to application passwords only. Provides the user ID as the second argument. two_factor_email_token_ttl filter overrides the time interval in seconds that an email token is considered after generation. Accepts the time in seconds as the first argument and the ID of the WP_User object being authenticated. two_factor_email_token_length filter overrides the default 8 character count for email tokens. two_factor_backup_code_length filter overrides the default 8 character count for backup codes. Provides the WP_User of the associated user as the second argument. two_factor_rest_api_can_edit_user filter overrides whether a user’s Two-Factor settings can be edited via the REST API. First argument is the current $can_edit boolean, the second argument is the user ID. two_factor_before_authentication_prompt action which receives the provider object and fires prior to the prompt shown on the authentication input form. two_factor_after_authentication_prompt action which receives the provider object and fires after the prompt shown on the authentication input form. two_factor_after_authentication_input action which receives the provider object and fires after the input shown on the authentication input form (if form contains no input, action fires immediately after two_factor_after_authentication_prompt). two_factor_login_backup_links filters the backup links displayed on the two-factor login form. Redirect After the Two-Factor Challenge To redirect users to a specific URL after completing the two-factor challenge, use WordPress Core built-in login_redirect filter. The filter works the same way as in a standard WordPress login flow: add_filter( 'login_redirect', function( $redirect_to, $requested_redirect_to, $user ) { return home_url( '/dashboard/' ); }, 10, 3 );