Security and vulnerabilities
Updated on
The two main principles of IT security
According to LRob, two main principles, as unavoidable as they are dogmatic, are worth remembering:
- The final security of a system is that of the weakest link in its chain.
- 100% security is illusory (and anyone who claims otherwise is a liar or ignorant).
— Robin LABADIE
Note that users and administrators are part of the security chain.
This is why no aspect of security can be neglected, no link in the IT chain, because even when doing our best, things can slip through and we are never safe from a “0 day” vulnerability, that is, a vulnerability exploited before it is fixed.
LRob security
LRob servers have many levels of security aimed at blocking attacks as high up the server chain as possible. We try to be beyond reproach on every aspect in order to get as close as possible to 100% security. Remember that perfect security never exists, but we can try to get close to it. LRob’s security measures are rigorous and some are unprecedented in the hosting world, to give you the highest possible level of security.
Default security
Ultimate server security “out of the box”!
ModSecurity web application firewall
Effectively blocks malicious requests before they reach your sites. In case of repeat offenses, fail2ban takes care of blocking the attacking IP entirely for more security.
Fail2ban anti-brute-force
Completely blocks repeated unauthorized access on all of the server’s services. IP blocking of brute-force attempts on WordPress, Plesk, e-mail and FTP. Also blocks bots looking for vulnerabilities on the servers.
Site isolation
Each site is isolated in its own system user by default. If there is a problem with one site, it cannot affect the others.
Server antivirus
ImunifyAV scans sites regularly.
PHP updates
If you forget, we take care of it for you!
Daily server updates
Vulnerabilities in server software can also exist (even though hosts deny it across the board). The daily update keeps your hosting as safe as possible from security vulnerabilities.
Daily host backups
Off-site backups with one-year retention for maximum peace of mind.
SSL/TLS certificates included
Automatic TLS certificate generation & HTTPS enforced by default. Free Wildcard certificates available at no cost if you manage your sites’ DNS zones through LRob.
Strong encryption
Exclusive use of secure TLS ciphers.
WordPress security
WordPress security made easy!
Control at a glance
Your hosting panel highlights any anomaly in your WordPress instances.
Automatic WordPress updates
Can be turned on in a few clicks to ensure maximum security at all times.
WordPress login protection
IP blocking of brute-force attacks on your WordPress login.
Server antivirus
ImunifyAV scans sites regularly to check that no known malicious file is present. In case of an anomaly, you receive an e-mail.
WordPress vulnerability detection
Check vulnerabilities manually and receive alerts when a new vulnerability is detected, so you can react quickly.
See the 24 security rules for WordPress
- Change the default administrator user name (admin)
- Block access to .htaccess and .htpasswd
- Block access to potentially sensitive files (logs, scripts, executables)
- Block access to files containing credentials
- Block bots looking for WordPress-specific vulnerabilities
- Change the default database table prefix
- Disable file editing in the WordPress dashboard
- Disable PHP execution in cache directories
- Disable unused scripting languages (Python, Perl, etc.)
- Disable pingbacks
- Disable script concatenation in the WordPress admin panel
- Block access to the wp-config.php file
- Forbid PHP script execution in the wp-content/uploads directory
- Forbid PHP script execution in the wp-includes directory
- Block directory browsing (-indexes)
- Block access to the xmlrpc.php file
- Configure security keys
- Restrict access to files and directories (permissions)
- Block author scans
- Enable automatic updates
- Generate a secure password
- Automatically detect security vulnerabilities
- Scan the site for malicious files
- Set a PHP version with security support
Security vulnerabilities
Server vulnerabilities
Security vulnerabilities that may occur on the server side are handled by the host, LRob.
LRob uses Linux servers (Debian), a very reliable, stable and secure version, ideal for a production web server system. Security vulnerabilities on Linux are generally fixed very quickly, even before they are publicly disclosed.
We have also put in place several measures to avoid server vulnerabilities, notably active monitoring of Linux system vulnerabilities with an immediate manual update in case of a flaw. And also an automatic daily update of all the server software, with a monthly manual check every first Monday of the month.
CMS vulnerabilities
An interactive, dynamic website, such as those built with CMSs, is exposed to security vulnerabilities. This is why it is essential to control and secure the interactions between the user and your site.
CMSs such as WordPress are regularly subject to security vulnerabilities. LRob provides many additional server-side protections and tools to help you stay secure. Nevertheless, when a vulnerability exists, your site may remain exposed. It is therefore important to:
- Keep your CMS and its plugins up to date (turn on automatic updates).
- Use strong, unique passwords.
- Monitor the site’s users and files to prevent intrusions.
- Use Plesk’s tools to check for any vulnerabilities present and fix them (by updating, deactivating or replacing scripts).
- Use Plesk’s tools to add extra security rules to WordPress
Tools such as Plesk’s WordPress Toolkit help you keep your WordPress and other applications more secure than on most hosting providers. Nevertheless, you cannot rely solely on these additional protections: if your application is inherently insecure, it could be hacked.
Note that the PHP software that runs your final application (CMS) can also contain security vulnerabilities when you use an obsolete version that no longer receives security support. We advise checking your PHP version once a year. Vulnerabilities coming from obsolete PHP versions are avoided as far as possible by LRob by pushing, once a year, the new PHP versions used on websites (and warning any hosting owners in case their site is incompatible with the new PHP versions).
If you suspect a hack or an unexpected change on your site, contact your support, who will be able to guide you and help effectively.