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.

Maikuolan

CIDRAM (Classless Inter-Domain Routing Access Manager) is a PHP script designed to protect websites by blocking requests originating from IP addresses regarded as being sources of undesirable traffic, including (but not limited to) traffic from non-human access endpoints, cloud services, spambots, scrapers, etc. It does this by calculating the possible CIDRs of the IP addresses supplied from inbound requests and then attempting to match these possible CIDRs against its signature files (these signature files contain lists of CIDRs of IP addresses regarded as being sources of undesirable traffic); If matches are found, the requests are blocked.
<h3>Requirements</h3>
<ul>
<li>PHP >= 7.2.0</li>
<li>PCRE</li>
</ul>
<h3>Updating</h3>
Note: CIDRAM does not interact in any way with your database, and stores its own configuration settings, customisations, and related materials as flatfiles within its own directory. If you’ve not changed any of the default configuration settings and if you’re not using any customisations for this plugin, updating normally via the plugins dashboard, without need for any additional steps, should be sufficient and shouldn’t cause any problems. However, if you’ve modified the configuration settings for CIDRAM, or if you’ve made any customisations, I would recommend making backups of all of these prior to updating, due to that updating will overwrite all settings and customisations (after updating, you can then restore your customisations from your backups). Alternatively, if you update via the CIDRAM front-end updates page, all settings and customisations should be preserved.

CIDRAM

CIDRAM: A PHP-level CIDR/IP-based firewall solution.

Obsyde Aegis vs CIDRAM