Protection Shield explained: login, attack and file protection
The Protection Shield reads every website's access log about once a minute, with no extra load on the websites, and protects all of them at once. Open it in the administrator panel (https://<server>:2087): Protection Shield (section Security).
What it does
| Part | What it does | Default |
|---|---|---|
| Login protection | Blocks addresses that guess passwords on WordPress, Joomla, Drupal and similar sites | On, 20 failed logins per minute, blocked 60 minutes |
| Web application firewall | Recognises SQL injection, reading server files, command injection, script injection, attack tools and searches for secret files (.env, .git, configuration backups) | Monitor — record only |
| File watcher | Checks new and changed website files for malicious code every 2 minutes | On |
On top of this, every website refuses to run scripts from upload folders and sends security headers. Customers can turn these off per site.
The page
- Attacks on websites (24 h), Malicious files found (24 h), Login attacks stopped (24 h) and Addresses blocked now.
- Blocked now — addresses the shield blocked, with the time the block ends, and Unblock.
- Most active attackers (7 days) and Recent events: Password guessing, Attack, Address blocked, Script in upload folder, Malicious file.
How blocking works
- A blocked address is blocked in the server firewall, for every service (websites, email, FTP, the panel), not only the website.
- The first block lasts Block for (minutes) (60 by default). An address that comes back within a day is blocked for 24 hours.
- Never blocked: the server's own addresses, addresses on the Firewall allow list, and anyone who signed in to the panel in the last day.
Good to know
- Start the web application firewall in monitor mode, check Recent events for a few days, then switch to protect. See turn on the web application firewall.
- Found malicious files are reported or quarantined, depending on Quarantine detected files automatically in the Malware Scanner. The customer is emailed.
- Customers see the attacks on their own sites in Access Control and can switch protections per site. See turn website protection on or off.
Common questions
Does the shield slow websites down?
No. It works from the access logs that are already read for bandwidth statistics; in protect mode the live rules check requests in the web server itself.
A customer was blocked. How do I free them?
Click Unblock next to the address under Blocked now. See how to unblock an IP address for blocks made elsewhere.
Is this the same as Brute Force Protection?
No. The shield protects the websites' own logins. Brute Force Protection protects logins to the admin panel, control panel and API. See brute force protection.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- How to turn on the web application firewall (WAF)
Switch the server's web application firewall from monitor to protect mode, choose its sensitivity, and see which attacks it refuses and blocks.
- How to stop WordPress login attacks (brute force) on all sites
Block addresses that guess passwords on wp-login.php, xmlrpc.php, Joomla and Drupal across every website on the server, and set the limit and block time.
- How to unblock an IP address (customer can't connect)
A customer or you cannot reach the server or log in: find which protection blocked the IP address and unblock it in the right place in the admin panel.
- How to scan websites for malware (and schedule scans)
Scan one account or the whole server for malware, web shells and cryptominers, schedule daily or weekly scans and turn on automatic quarantine.