FreelanceBo Sentra Control vs XO Security

FreelanceBo Sentra Control is a comprehensive WordPress security plugin that connects your site to the Sentra central console, providing enterprise-grade protection. Features Web Application Firewall (WAF) – Block malicious requests, SQL injection, XSS, and other common attacks Malware Scanner – Scan WordPress core files, themes, and plugins for known malware signatures Vulnerability Scanner – Check installed plugins and themes against known vulnerability databases Brute Force Protection – Limit login attempts and block attackers automatically File Integrity Monitoring – Detect unauthorized changes to WordPress core files IP Blocklist – Manage blocked IPs manually or automatically based on threat detection Security Events Log – Track all security events with detailed logging Central Console – Manage multiple WordPress sites from a single dashboard How It Works Install and activate the plugin on your WordPress site Connect to your Sentra central console by entering the server URL and API key in Settings The plugin automatically starts monitoring your site and reporting to the console View scan results, manage firewall rules, and review security events from either the WordPress admin panel or the central console Requirements WordPress 5.8 or higher PHP 7.4 or higher A Sentra central console account (available at freelancebo.it) External Services This plugin relies on the following external services: FreelanceBo Sentra Control Console This plugin connects to a self-hosted FreelanceBo Sentra Control central console for centralized security monitoring and management. This connection is essential for the plugin to function. What data is sent: * Site URL, WordPress version, PHP version, and installed plugins/themes list (during heartbeat and scans) * Security events (firewall blocks, failed login attempts, malware detections, file integrity changes) * Scan results (malware scan, vulnerability scan, integrity scan findings) When data is sent: * On plugin activation and periodically via heartbeat (every 5 minutes) * When security events occur (login attempts, firewall blocks) * When scans are triggered (manually or via scheduled cron) * When the admin manages firewall rules, blocklists, or settings Service provider: FreelanceBo Group S.r.l.s., Bologna, Italy * Service URL: https://sentra.freelancebo.it * Terms of Service: https://sentra.freelancebo.it/terms * Privacy Policy: https://sentra.freelancebo.it/privacy The console server URL is configurable by the user in the plugin settings. All data is transmitted over HTTPS. Data is stored on EU-based servers in compliance with GDPR. WordPress.org API The vulnerability scanner module uses the official WordPress.org API to retrieve information about installed plugins, themes, and WordPress core version. This is necessary to check for known vulnerabilities and outdated software. What data is sent: * Plugin slugs, theme slugs, and WordPress core version When data is sent: * When a vulnerability scan is triggered (manually or via scheduled cron) Service provider: WordPress.org * API endpoint: https://api.wordpress.org * Terms of Service: https://wordpress.org/about/privacy/ * Privacy Policy: https://wordpress.org/about/privacy/

XO Security is a plugin to enhance login related security. This plugin does not write to .htaccess file. Besides Apache, LiteSpeed, Nginx and IIS also work. Functions Record login log. Limit login attempts. Add Captcha to the login form and comment form. Change the URL of the login page. Enable two-factor authentication (2FA) for login. Login Alert. Disable login by mail address. Disable login by user name. Change login error message. Disable XML-RPC and XML-RPC Pingback. Disable REST API. Disable author archive page. Remove comment author class of comments list. Remove the username from the oEmbed response data. WooCommerce login page protection. Anti-spam comment. Hide WordPress version information. Edit the author slug. Disable RSS and Atom feeds. Activate maintenance mode. Delete the readme.html file. WordPress multisite considerations If you set the login page separately for the main site and the subsite, you will not be able to use the password loss function of the subsite. We recommend that you set the login page to be common to all sites.