Atomic Edge Security – Firewall, Malware Scan and Login Security vs Two Factor

Atomic Edge Security is a WordPress firewall plugin that protects your site with cloud-based WAF rules, malware scanning, 2FA, vulnerability checks, IP blocking, and real-time security logs. It blocks malicious traffic before it reaches WordPress while giving site owners firewall controls directly inside the WordPress admin. WordPress Firewall Protection Atomic Edge includes a cloud-based WordPress firewall that helps block malicious traffic before it reaches your website. The firewall protects against common attacks such as SQL injection, cross-site scripting (XSS), local file inclusion, remote file inclusion, brute-force login attempts, and suspicious bot activity. Web Application Firewall (WAF) The Atomic Edge WAF uses OWASP Core Rules and WordPress-specific security rules to protect high-risk areas such as wp-login.php, wp-admin, XML-RPC, REST API endpoints, vulnerable plugin paths, and common exploit patterns. Features Two-Factor Authentication (2FA) – Protect WordPress logins with TOTP authenticator apps (Google Authenticator, Authy, etc.) 2FA Enforcement Policies – Require 2FA for specific user roles with configurable grace periods 2FA Audit Logging – Complete security audit trail for all 2FA events Adaptive Defense – AI-powered threat detection that automatically identifies and blocks malicious actors Web Application Firewall (WAF) – Block SQL injection, XSS, and other attacks with OWASP Core Rules Content Delivery Network (CDN) – Serve static assets from global edge servers for faster page loads Real-time Analytics – Monitor traffic, blocked threats, and security events in real-time IP Access Control – Easily whitelist or blacklist IP addresses and CIDR ranges Geographic Blocking – Block or allow access based on visitor country Malware Scanner – Scan WordPress files for modifications and suspicious code patterns Vulnerability Scanner – Check WordPress core, plugins, and themes for known vulnerabilities (requires Atomic Edge connection) WAF Log Viewer – See exactly what threats are being blocked WP-CLI Integration – Run security scans from the command line How It Works Sign up for an Atomic Edge account at atomicedge.io Add your site to Atomic Edge and get your API key Install this plugin and enter your API key Manage your security settings directly from WordPress Vulnerability scanning is available when connected and uses Atomic Edge’s vulnerability data feed. Requirements PHP 7.4 or higher WordPress 5.8 or higher An Atomic Edge account (free tier available) OpenSSL PHP extension External Services This plugin connects to external services provided by Atomic Edge to deliver WAF, CDN, and security features. Below is a detailed explanation of each service, what data is transmitted, and when. Atomic Edge API The primary external service this plugin connects to is the Atomic Edge API at https://dashboard.atomicedge.io/api/v1. What it does: * Manages your site’s Web Application Firewall (WAF) settings * Retrieves real-time analytics and traffic data * Fetches WAF security logs showing blocked threats * Manages IP whitelist/blacklist and geographic access controls * Retrieves CDN configuration and status * Provides vulnerability scanning data for WordPress core, plugins, and themes * Powers the Adaptive Defense AI-powered threat detection system What data is sent: * Your site’s API key (for authentication) * IP addresses you add to whitelist/blacklist * Country codes for geographic blocking rules * CDN optimization settings (asset types, minification preferences) * Site URL and domain information * Adaptive Defense settings and blocked IP information When data is sent: * When you save settings in the plugin admin pages * When you view analytics or WAF logs (to fetch data) * When you run a vulnerability scan * When you manage IP access control rules * When Adaptive Defense checks or updates threat status * Background sync of CDN settings (when CDN is enabled) Service links: * Service website: https://atomicedge.io * Terms of Service: https://atomicedge.io/terms-of-service * Privacy Policy: https://atomicedge.io/privacy-policy Malware Signature API The malware scanner fetches signature patterns from a public API endpoint. What it does: * Provides up-to-date malware detection signatures * Allows scanning without requiring an API key What data is sent: * No personal or site-specific data is sent * Only a GET request to retrieve signature patterns When data is sent: * When you initiate a malware scan (if cached signatures have expired) * Signatures are cached locally for 24 hours Service links: * This service is provided by Atomic Edge (same terms and privacy policy as above) Data Storage All API responses are cached locally using WordPress transients to minimize external requests. Malware signature data is cached for 24 hours. Analytics data is fetched fresh on each page load but displayed quickly via JavaScript pagination.

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 );