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.

te_taipo

<h4>PARETO SECURITY FEATURES</h4>
Had enough of the security theatre presented by the raft of WordPress security plugins? Time to put a stop to the attacks!
Firstly WordPress and most other CMS\’s are built using PHP. PHP is a very insecure programming language, even worse in the hands of amateurs.
WordPress has been plagued by plugins authored by amateurs that bring with them security vulnerabilities.
Security plugin designers mostly focus on cleaning up attacks rather than stopping them dead in their tracks.
Pareto Security class acts as a Central Security Hub checking all inputs from users, preventing bad requests from executing on your website.
<ul>
<li>Real Attack Prevention that can be achieved via a plugin</li>
<li>Automatic Blacklist Management</li>
<li>Easy-To-Use</li>
<li>No customisation needed</li>
<li>Works silently, you only get notified when you really want to be notified</li>
<li>Completely Free</li>
<li>and much more…</li>
</ul>
<h4>PARETO SECURITY PROTECTION</h4>
<ul>
<li>Pareto Security Protection identifies and blocks malicious traffic.</li>
<li>Pareto Security Protection dynamic IP Blacklist protects your site while reducing load.</li>
<li>Protects your site at the entry-point, disabling attack peneration of your WordPress site.</li>
<li>Extends WordPress inbuilt security, defends your website against vulnerabilities added in via bad plugin coding.</li>
<li>[disabled] Optionally prevent Tor users/bots from interacting with login forms and search functions of your site while still allowing them to view your site.</li>
<li>Optionally only allow standard web clients and trusted crawlers to access your website, discouraging others from doing so.</li>
</ul>
<h4>PARETO SECURITY TOOLS</h4>
<ul>
<li>Monitor blocked attack attempts</li>
<li>Optionally receive notifications of REAL attack attempts that Pareto Security has blocked</li>
</ul>
<h4>A Word on Security:</h4>
By the very nature of plugins, no plugin should ever claim to be a Web Application Firewall.
No security plugin can save your website from really-really badly written site, theme and/or plugin code.
No security plugin can save your site from attacks that result from when administrators do not follow basic security practices.
Keeping any CMS as secure as possible is not easy. The very best thing you can do to prevent attacks is to always keep your website code, themes and plugins up to date, and remove any plugins and themes you are not using.

Pareto Security

WordPress Core Security: Secure your website with real security.

Obsyde Aegis vs Pareto Security