Opis
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:
- Real-time local threat detection — SQL injection, XSS, path traversal, remote code execution, and 50+ attack patterns. Works without any account.
- WordPress-specific protection — wp-login.php brute force detection, xmlrpc.php abuse blocking, REST API user enumeration prevention. Works without any account.
- Automated IP blocking — Local pattern-match blocks and (optionally) a curated blocklist synced from the Obsyde platform
- Community threat intelligence — 44,000+ known malicious IPs from 8 free intelligence sources (via the optional Obsyde sync), updated every 6 hours
- 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
- Zero performance impact — Pattern matching runs in under 5ms; no external API calls during page load (reporting is batched via WP-Cron)
- Cloudflare compatible — Proper IP detection behind Cloudflare, nginx, and other reverse proxies
How It Works:
- Install and activate the plugin — local firewall protection starts immediately
- The plugin intercepts every HTTP request before WordPress processes it
- Requests are checked against local attack signatures and (if an API key is configured) the synced Obsyde blocklist
- Threats are blocked with a 403 response
- 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.
Protection Levels:
- Low — Block known attacks only
- Medium — Block attacks and suspicious patterns (recommended)
- High — Aggressive blocking including empty User-Agent rejection
- Paranoid — Maximum protection (may cause false positives)
External services
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:
- 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
/plugin/events. This lets the Obsyde dashboard display, analyse, and correlate threats across all of your sites. - Blocklist sync — Once every 5 minutes (via WP-Cron) the plugin sends a GET request to
/plugin/blocklistto retrieve the current curated list of malicious IPs. No site data is sent in this request; only the site API key identifies the request. - Heartbeat — Once every 5 minutes (via WP-Cron) the plugin sends a POST request to
/plugin/heartbeatcontaining your WordPress version, PHP version, and plugin version so the Obsyde dashboard can show whether the site is reachable and up to date. - Connection test — When you click the “Test Connection” button in the settings, a single GET request is sent to
/plugin/configto verify your API key.
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:
- Terms of service: https://obsyde.com/terms
- Privacy policy: https://obsyde.com/privacy
Instalacija
- Upload the
obsyde-aegisfolder to/wp-content/plugins/ - Activate the plugin through the Plugins menu — local firewall protection begins immediately
- (Optional) Go to Settings > Obsyde Aegis to enable centralised reporting
- (Optional) Enter your API key — get one at obsyde.com/dashboard/sites/new
- (Optional) Click “Test Connection” to verify
- Choose your protection level
ČPP
-
Do I need an Obsyde account?
-
No. The plugin's local firewall — pattern matching, brute-force detection, User-Agent checks — works unconditionally after activation with no account, no API key, and no external communication.
An Obsyde account is only needed if you want the additional centralised dashboard features: cross-site threat reporting, the community-intelligence blocklist sync, geo maps, and AI threat analysis. Those are optional add-ons to the core local protection.
-
Will this slow down my site?
-
No. The firewall check runs in under 5ms. No external API calls are made during page load — events are batched and sent via WP-Cron in the background (and only when an Obsyde API key is configured).
-
Does it work with Cloudflare?
-
Yes. The plugin automatically detects the real visitor IP from Cloudflare's CF-Connecting-IP header.
-
The plugin continues to block threats locally using its cached blocklist and pattern matching. Events are queued and sent when the API is available again. Local protection is never affected by API availability.
-
Can I whitelist IPs?
-
Yes. Add trusted IPs to the whitelist in Settings > Obsyde Aegis. Whitelisted IPs bypass all checks.
Recenzije
Nema recenzija za ovaj dodatak.
Saradnici i programeri
“Obsyde Aegis” is open source software. The following people have contributed to this plugin.
DoprinositeljiPrevedi “Obsyde Aegis” na vaš jezik.
Zainteresirani za razvoj?
Pregledajte kôd, pogledajte SVN spremišteili se pretplatite na dnevnik razvoja od RSS.
Zapis promijena
1.0.1
- Local firewall protection (pattern matching, brute-force detection, method filtering, User-Agent checks) now runs unconditionally without any account or API key required. Obsyde dashboard reporting remains an optional add-on service.
- Inline
<style>block on the 403 block page replaced with element-level style attributes (no<style>tag). - Settings-page
<script>moved to a separate file atassets/js/settings.jsand enqueued viawp_enqueue_scriptwithwp_localize_scriptsupplying the AJAX URL and nonce. - API key sanitization no longer uses
sanitize_text_field()which could alter valid secrets — input is now trimmed and validated against the expected key format, with invalid submissions rejected viaadd_settings_error()without overwriting the stored key. - Documented the optional Obsyde external service in the readme (data flows, terms, privacy policy links).
1.0.0
- Initial release
- Real-time threat detection with 50+ attack patterns
- Automated IP blocking with blocklist sync
- WordPress-specific protections (brute force, xmlrpc, user enumeration)
- Background event reporting via WP-Cron
- Admin settings page with connection testing
- Cloudflare and reverse proxy IP detection