FreelanceBo Sentra Control vs Lockora Security Audit

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/

Lockora Security Audit helps site owners and agencies review a WordPress site’s security posture from the admin area. Works well with Who Changed It? Lockora finds security weaknesses. Who Changed It? – Activity Log shows what changed, who changed it, and when, with severity classification, field-level diffs, and alerts. Use both together to connect a security finding to the activity that caused it. Current prototype features include: Manual security scans. Weighted security score out of 100. Bounded scan history with current-versus-previous finding comparisons. WordPress core file integrity checks using official checksums, with CSV and TXT exports. Bounded wp-content anomaly scanning for executable uploads, unexpected PHP files outside standard code directories, runtime executables, and exposed backup or secret-like files, with CSV/TXT exports and clipboard copying. WordPress authentication key and salt checks, with explicit actions to generate missing salts or rotate the keys stored in wp-config.php. Must-use plugin directory presence checks. PHP version status using WordPress.org Serve Happy data. HTTPS and HTTP security header checks. WordPress core, plugin, and theme update posture checks. Administrator account posture checks for default usernames, excess admins, inactive admins, user ID 1 exposure, and an admin username/email inventory. Public exposure checks: debug.log and readme.html reachability, uploads directory listing, PHP execution inside uploads, and author archive user enumeration. SSL certificate expiry check, database table prefix check, automatic update posture check, and detection of login protection / two-factor plugins. Site Health integration: scan summary plus key configuration checks appear under Tools > Site Health > Status. WP-CLI support: wp lockora scan and wp lockora report, with --format=json and a --strict flag for CI pipelines. Optional known vulnerability matching with a configured Wordfence Intelligence API key. Optional AI client reports on WordPress 7.0+ when the site’s AI Connector is configured. Reversible hardening toggles for XML-RPC, REST user routes, generator tag output, and basic security headers. A lockora_scan_completed action for integrations that need scan scores and finding counts. External Services Lockora Security Audit may connect to external services only when the administrator runs a scan or generates an AI client report. During a scan the plugin also sends HTTP requests to the site’s own public URL (loopback requests) to inspect response headers, debug.log and readme.html reachability, uploads directory behavior, and author archive redirects, and it opens a TLS connection to the site’s own hostname to read the SSL certificate expiry date. These requests stay within the site being scanned and send no data to third parties. 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.