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.

jp-secure

You can find docs, FAQ and more detailed information on <a href="https://www.jp-secure.com/siteguard_wp_plugin_en/" rel="nofollow ugc">English Page</a> <a href="https://www.jp-secure.com/siteguard_wp_plugin/" rel="nofollow ugc">Japanese Page</a>.
Simply install the SiteGuard WP Plugin, WordPress security is improved. 
This plugin is a security plugin that specializes in the login attack of brute force, such as protection and management capabilities.
Notes
<ul>
<li>It does not support the multisite function of WordPress.</li>
<li>It only supports Apache 1.3, 2.x for Web servers.</li>
<li>To use the CAPTCHA function, the expansion library “mbstring” and “gd” should be installed on php.</li>
<li>To use the management page filter function and login page change function, “mod_rewrite” should be loaded on Apache.</li>
<li>To use the WAF Tuning Support, WAF ( SiteGuard Server Edition ) should be installed on Apache.</li>
</ul>
There are the following functions.
<ul>
<li>Admin Page IP Filter</li>
</ul>
It is the function for the protection against the attack to the management page (under wp-admin.) 
To the access from the connection source IP address which does not login to the management page, 404 (Not Found) is returned. 
At the login, the connection source IP address is recorded and the access to that page is allowed. 
The connection source IP address which does not login for more than 24 hours is sequentially deleted. 
The URL (under wp-admin) where this function is excluded can be specified.
<ul>
<li>Rename Login</li>
</ul>
It is the function to decrease the vulnerability against an illegal login attempt attack such as a brute force attack or a password list attack. 
The login page name (wp-login.php) is changed. The initial value is “login_<5 random digits>” but it can be changed to a favorite name.
<ul>
<li>CAPTCHA</li>
</ul>
It is the function to decrease the vulnerability against an illegal login attempt attack such as a brute force attack or a password list attack, 
or to receive less comment spam. For the character of CAPTCHA, hiragana and alphanumeric characters can be selected.
<ul>
<li>Login Lock</li>
</ul>
It is the function to decrease the vulnerability against an illegal login attempt attack such as a brute force attack or a password list attack. 
Especially, it is the function to prevent an automated attack. The connection source IP address the number of login failure of which reaches 
the specified number within the specified period is blocked for the specified time. 
Each user account is not locked.
<ul>
<li>Login Alert</li>
</ul>
It is the function to make it easier to notice unauthorized login. E-mail will be sent to a login user when logged in. 
If you receive an e-mail to there is no logged-in idea, please suspect unauthorized login.
<ul>
<li>Fail Once</li>
</ul>
It is the function to decrease the vulnerability against a password list attack. Even is the login input is correct, the first login must fail. 
After 5 seconds and later within 60 seconds, another correct login input make login succeed. At the first login failure, the following error message is displayed.
<ul>
<li>Disable Pingback</li>
</ul>
The pingback function is disabled and its abuse is prevented.
<ul>
<li>Block Author Query</li>
</ul>
Prevents leakage of user names due to “/?author=” access.
<ul>
<li>Updates Notify</li>
</ul>
Basic of security is that always you use the latest version. If WordPress core, plugins, and themes updates are needed , sends email to notify administrators.
<ul>
<li>WAF Tuning Support</li>
</ul>
It is the function to create the rule to avoid the false detection in WordPress (including 403 error occurrence with normal access,) 
if WAF ( SiteGuard Server Edition ) by EG Secure Solutions is installed on a Web server. WAF prevents the attack from the outside against the Web server, 
but for some WordPress or plugin functions, WAF may detect the attack which is actually not attack and block the function. 
By creating the WAF exclude rule, the WAF protection function can be activated while the false detection for the specified function is prevented.
<h4>Translate</h4>
If you have created your own language pack, or have an update of an existing one, you can send <a href="https://codex.wordpress.org/Translating_WordPress" rel="nofollow ugc">gettext PO and MO files</a> to sgdev@jp-secure.com so that We can bundle it into SiteGuard WP Plugin. You can download the latest <a href="https://plugins.svn.wordpress.org/siteguard/trunk/languages/siteguard.pot" rel="nofollow ugc">POT file</a>, and <a href="https://plugins.svn.wordpress.org/siteguard/branches/languages/" rel="nofollow ugc">PO files in each language</a>.

SiteGuard WP Plugin


誰でもユーザーを登録できるサイトを作っているのですが、ログイン保護機能を利用しています。スパムアカウントが減りました。


ログイン保護に利用しています

SiteGurad WP Plugin is the plugin specialized for the protection against the attack to the management page and login.

Obsyde Aegis vs SiteGuard WP Plugin