ModSecurity in Shared Website Hosting
ModSecurity is offered with each shared website hosting plan that we provide and it is turned on by default for any domain or subdomain that you include through your Hepsia Control Panel. If it disrupts any of your programs or you would like to disable it for whatever reason, you will be able to accomplish that through the ModSecurity section of Hepsia with merely a click. You can also activate a passive mode, so the firewall will identify possible attacks and keep a log, but will not take any action. You could view extensive logs in the same section, including the IP address where the attack originated from, what precisely the attacker attempted to do and at what time, what ModSecurity did, and so on. For maximum security of our customers we use a set of commercial firewall rules mixed with custom ones that are provided by our system admins.
ModSecurity in Semi-dedicated Hosting
All semi-dedicated hosting solutions that we offer feature ModSecurity and because the firewall is enabled by default, any website that you build under a domain or a subdomain shall be protected immediately. An individual section inside the Hepsia Control Panel which comes with the semi-dedicated accounts is devoted to ModSecurity and it shall permit you to start and stop the firewall for any Internet site or activate a detection mode. With the last option, ModSecurity will not take any action, but it shall still identify possible attacks and shall keep all information inside a log as if it were 100% active. The logs can be found inside the same section of the Control Panel and they feature specifics about the IP where an attack came from, what its nature was, what rule ModSecurity applies to identify and stop it, and so forth. The security rules which we use on our machines are a mix between commercial ones from a security business and custom ones made by our system admins. Consequently, we offer greater security for your web apps as we can shield them from attacks even before security corporations release updates for completely new threats.
ModSecurity in VPS Hosting
Security is essential to us, so we set up ModSecurity on all virtual private servers which are set up with the Hepsia Control Panel as a standard. The firewall could be managed through a dedicated section in Hepsia and is turned on automatically when you include a new domain or generate a subdomain, so you'll not need to do anything manually. You'll also be able to deactivate it or switch on the so-called detection mode, so it'll maintain a log of potential attacks that you can later analyze, but shall not stop them. The logs in both passive and active modes contain info about the form of the attack and how it was eliminated, what IP it originated from and other useful info that may help you to tighten the security of your sites by updating them or blocking IPs, for instance. On top of the commercial rules we get for ModSecurity from a third-party security firm, we also use our own rules because occasionally we identify specific attacks which are not yet present inside the commercial group. That way, we can enhance the security of your VPS in a timely manner instead of awaiting an official update.
ModSecurity in Dedicated Web Hosting
All of our dedicated servers that are set up with the Hepsia hosting Control Panel come with ModSecurity, so any program you upload or set up shall be secured from the very beginning and you'll not need to stress about common attacks or vulnerabilities. An individual section in Hepsia will enable you to start or stop the firewall for every domain or subdomain, or activate a detection mode so that it records information about intrusions, but doesn't take actions to prevent them. What you shall find in the logs shall allow you to to secure your Internet sites better - the IP an attack came from, what website was attacked and exactly how, what ModSecurity rule was triggered, etc. With this data, you'll be able to see whether a site needs an update, if you ought to block IPs from accessing your server, etc. In addition to the third-party commercial security rules for ModSecurity that we use, our administrators add custom ones as well when they find a new threat which is not yet a part of the commercial bundle.