obsyde

Obsyde Aegis protects your WordPress site with enterprise-grade security monitoring. The plugin intercepts every request, checks it against known attack signatures, and blocks threats in real time. Local protection runs unconditionally — no account required. When connected to the optional Obsyde dashboard service, detected events are additionally reported for centralised monitoring, geo maps, and AI-powered analysis.
Key Features:
<ul>
<li>Real-time local threat detection — SQL injection, XSS, path traversal, remote code execution, and 50+ attack patterns. Works without any account.</li>
<li>WordPress-specific protection — wp-login.php brute force detection, xmlrpc.php abuse blocking, REST API user enumeration prevention. Works without any account.</li>
<li>Automated IP blocking — Local pattern-match blocks and (optionally) a curated blocklist synced from the Obsyde platform</li>
<li>Community threat intelligence — 44,000+ known malicious IPs from 8 free intelligence sources (via the optional Obsyde sync), updated every 6 hours</li>
<li>Centralised dashboard (optional) — When an Obsyde API key is configured, view all security data on obsyde.com with real-time alerts, geo maps, and AI analysis</li>
<li>Zero performance impact — Pattern matching runs in under 5ms; no external API calls during page load (reporting is batched via WP-Cron)</li>
<li>Cloudflare compatible — Proper IP detection behind Cloudflare, nginx, and other reverse proxies</li>
</ul>
How It Works:
<ol>
<li>Install and activate the plugin — local firewall protection starts immediately</li>
<li>The plugin intercepts every HTTP request before WordPress processes it</li>
<li>Requests are checked against local attack signatures and (if an API key is configured) the synced Obsyde blocklist</li>
<li>Threats are blocked with a 403 response</li>
<li>If an Obsyde API key is configured, events are batched and sent to your dashboard every 60 seconds; the Obsyde blocklist syncs every 5 minutes. Without a key, local protection still runs — events are just not reported externally.</li>
</ol>
Protection Levels:
<ul>
<li>Low — Block known attacks only</li>
<li>Medium — Block attacks and suspicious patterns (recommended)</li>
<li>High — Aggressive blocking including empty User-Agent rejection</li>
<li>Paranoid — Maximum protection (may cause false positives)</li>
</ul>
<h3>External services</h3>
This plugin provides local firewall protection that runs entirely in your WordPress installation and does not require any external service.
When you choose to connect the plugin to the optional Obsyde dashboard service by entering an API key, the plugin communicates with the Obsyde API at https://obsyde.com/api/v1/plugin/ for centralised threat monitoring. This service is provided by Obsyde Ltd.
What data is sent, when, and why:
<ul>
<li>Threat events — When the local firewall blocks a request, an event containing the attacker’s IP address, a UTC timestamp, the attack type (e.g. “sqli_probe”), severity, HTTP method, request path (truncated to 2048 characters), and User-Agent string (truncated to 512 characters) is queued. Once per minute (via WP-Cron) any queued events are POSTed in a single batch to <code>/plugin/events</code>. This lets the Obsyde dashboard display, analyse, and correlate threats across all of your sites.</li>
<li>Blocklist sync — Once every 5 minutes (via WP-Cron) the plugin sends a GET request to <code>/plugin/blocklist</code> to retrieve the current curated list of malicious IPs. No site data is sent in this request; only the site API key identifies the request.</li>
<li>Heartbeat — Once every 5 minutes (via WP-Cron) the plugin sends a POST request to <code>/plugin/heartbeat</code> containing your WordPress version, PHP version, and plugin version so the Obsyde dashboard can show whether the site is reachable and up to date.</li>
<li>Connection test — When you click the “Test Connection” button in the settings, a single GET request is sent to <code>/plugin/config</code> to verify your API key.</li>
</ul>
No data is sent to any external service until you configure an API key. If you remove the API key or deactivate the plugin, no further external communication occurs.
This service’s terms and privacy policy:
<ul>
<li>Terms of service: https://obsyde.com/terms</li>
<li>Privacy policy: https://obsyde.com/privacy</li>
</ul>

Obsyde Aegis

Real-time threat detection, automated IP blocking, and AI-powered security analysis.

Cory Marsh

BitFire protects WordPress sites from malicious bots, login attacks, malware, and unauthorized changes to files and database records.
<h3>Free Protection</h3>
Malware Scanner
Scan WordPress core, plugin, and theme files for malware, unexpected changes, and suspicious code.
Real-Time Traffic Monitoring
Review every request to your site, including who visited, what they accessed, and whether the request was blocked.
30 Days of Traffic History
Look back through a full month of traffic data to investigate issues, identify patterns, or better understand how your site is being used.
Login Protection
Browser verification stops automated login attempts, brute-force attacks, password stuffing, and other suspicious authentication activity.
A+ Rated Web Application Firewall
Independent third-party testing by Cloudbric rated BitFire’s WAF at 94% (A+). See how it compares:
<ul>
<li>BitFire: 94% (A+)</li>
<li>Ninja Firewall [PRO]: 67% (D)</li>
<li>Wordfence [PRO]: 41% (D)</li>
<li>MalCare [PRO]: 34% (F)</li>
<li>iThemes Security: 2% (F)</li>
<li>Shield Security [PRO]: 2% (F)</li>
<li>SiteGround Security: 2% (F)</li>
</ul>
<a href="https://labs.cloudbric.com/wafer" rel="nofollow ugc">View the full independent test results at Cloudbric Labs</a>
WP-CLI
Use BitFire’s WP-CLI integration to start malware scans, review scan results, inspect blocking data, and review web requests to your site. CSV, JSON, and table output formats are supported.
<h3>BitFire Pro</h3>
Built for Faster AI-Driven Attacks
AI-assisted exploit generation is reducing the time between vulnerability discovery and active attacks. Traditional defenses must wait for patches, signatures, or firewall rules.
Runtime Application Self-Protection
BitFire’s patented RASP technology monitors sensitive file, database, and network operations during every request.
It can prevent:
<ul>
<li>Unauthorized PHP file changes.</li>
<li>Unexpected administrator creation.</li>
<li>Malicious database modifications.</li>
<li>Outbound connections to malicious servers.</li>
<li>Redirect and JavaScript injection.</li>
</ul>
Automated Malware Scans
Run malware scans up to twice per day, with results emailed to you when a threat is confirmed.
Threat Hunter
Search traffic, files, database content, processes, and scheduled jobs for signs of compromise or reinfection.
360-Degree Coverage
Load BitFire before the WordPress boot process to stop attacks that target plugin and theme files directly.
Human Support
This is what makes BitFire different from the big-name security plugins: when you need help, you talk to a real person.
Our US-based support team is available 12 hours a day. No ticket queues that take days. No chatbots. No copy-and-paste answers. Just experienced people who will help make sure your site is secure.
Whether you need help with setup, have a question about a blocked request, or want someone to examine a suspicious file, we are here.
<h3>Pricing</h3>
<h3>Free</h3>
$0 forever. Bot blocking, malware scanning, login protection, and real-time traffic monitoring. Everything you need to stop the vast majority of automated attacks.
<h3>Pro – Single Site</h3>
$60/year. Full RASP protection, an A+ rated WAF, AI malware analysis, 30-day traffic logs, and priority human support.
<h3>Pro – Multi-Site Volume Pricing</h3>
Managing multiple sites? The more you protect, the less you pay:
<ul>
<li>2-4 sites: $50/site per year</li>
<li>5-9 sites: $45/site per year</li>
<li>10-24 sites: $35/site per year</li>
<li>25-49 sites: $25/site per year</li>
</ul>
Volume pricing is ideal for freelancers, agencies, and anyone managing WordPress sites for clients. <a href="https://bitfire.co/pricing" rel="nofollow ugc">Contact us for volume licensing</a>.
<h3>How BitFire Compares</h3>
<h3>BitFire vs Wordfence</h3>
Wordfence is a solid product with a large team writing custom rules for known vulnerabilities. One important difference is how BitFire handles automated traffic:
<ol>
<li>Bot blocking – WordPress cannot reliably distinguish human traffic from automated traffic on its own. BitFire is designed to identify and block malicious bots before they can exploit or infect your site.</li>
</ol>
If you use Wordfence, we strongly recommend using the paid version.
<a href="https://bitfire.co/en/wordfence-vs-bitfire" rel="nofollow ugc">Read the detailed BitFire vs Wordfence comparison</a>
<h3>Why Do Other Plugins Focus So Much on Cleaning Up Malware?</h3>
Good question. Have you noticed how much other security plugins charge for malware removal and how much of their marketing focuses on finding infections?
BitFire focuses on keeping malware off your site so you do not need to pay someone to remove it.
<h3>Privacy / Monitoring / Data Collection</h3>
We take your privacy seriously. Here is exactly what BitFire does with your data:
<ol>
<li>
Traffic inspection. BitFire inspects web traffic to your site to identify threats. Sensitive data, such as passwords and credit card numbers, is automatically replaced with redacted in logs. You can add additional fields to filter in the settings.
</li>
<li>
Error reporting. If BitFire encounters a software error, it can send a report to our development team so we can fix it in a future release. No visitor data is included in these reports.
</li>
<li>
Malware hash checking. BitFire sends small numeric fingerprints, known as 64-bit hashes, of your files to our hash server to compare them against our database of known-good files. For example, a file might hash to the number <code>812612388126487</code>. We never receive your actual file contents, and file hashes are not stored on our servers.
</li>
<li>
Local data storage. All log data and configuration files are stored locally on your server in a hidden, randomly named directory under <code>wp-content/uploads/</code>. This directory is protected by an <code>.htaccess</code> file and is not accessible from the web.
</li>
</ol>

BitFire Security – Firewall, Malware Scanner, Bot Blocker, Login Protection

Block malicious bots, malware, and exploits with an A+ rated WAF, fast malware scanning, and runtime file and database protection.

Obsyde Aegis vs BitFire Security – Firewall, Malware Scanner, Bot Blocker, Login Protection