ModSecurity in Hosting
ModSecurity is available with each and every hosting package which we offer and it is turned on by default for any domain or subdomain which you add through your Hepsia CP. In case it interferes with any of your programs or you'd like to disable it for some reason, you'll be able to do that through the ModSecurity area of Hepsia with only a mouse click. You could also activate a passive mode, so the firewall will recognize possible attacks and keep a log, but won't take any action. You could view extensive logs in the very same section, including the IP where the attack originated from, exactly what the attacker attempted to do and at what time, what ModSecurity did, and so forth. For maximum safety of our clients we use a group of commercial firewall rules mixed with custom ones which are included by our system admins.
ModSecurity in Semi-dedicated Hosting
All semi-dedicated hosting packages that we offer include ModSecurity and given that the firewall is turned on by default, any site that you build under a domain or a subdomain will be secured right away. An independent section within the Hepsia CP which comes with the semi-dedicated accounts is dedicated to ModSecurity and it will permit you to start and stop the firewall for any website or enable a detection mode. With the latter, ModSecurity won't take any action, but it'll still recognize possible attacks and will keep all information inside a log as if it were completely active. The logs can be found inside the exact same section of the CP and they feature information about the IP where an attack came from, what its nature was, what rule ModSecurity applies to detect and stop it, and so forth. The security rules we use on our servers are a mix of commercial ones from a security business and custom ones made by our system admins. Consequently, we provide increased security for your web apps as we can defend them from attacks even before security companies release updates for completely new threats.
ModSecurity in VPS Hosting
Safety is extremely important to us, so we install ModSecurity on all virtual private servers that are set up with the Hepsia CP as a standard. The firewall can be managed through a dedicated section in Hepsia and is activated automatically when you include a new domain or create a subdomain, so you will not have to do anything by hand. You will also be able to deactivate it or activate the so-called detection mode, so it'll keep a log of possible attacks that you can later analyze, but will not stop them. The logs in both passive and active modes offer information regarding the form of the attack and how it was stopped, what IP address it came from and other valuable information which might help you to tighten the security of your websites by updating them or blocking IPs, for example. Beyond the commercial rules that we get for ModSecurity from a third-party security enterprise, we also use our own rules because every now and then we find specific attacks that are not yet present in the commercial pack. This way, we can easily increase the protection of your Virtual private server in a timely manner as opposed to awaiting a certified update.
ModSecurity in Dedicated Web Hosting
All of our dedicated servers which are set up with the Hepsia hosting CP include ModSecurity, so any app you upload or set up will be properly secured from the very beginning and you'll not need to worry about common attacks or vulnerabilities. An independent section in Hepsia will enable you to start or stop the firewall for each 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 discover in the logs can easily enable you to to secure your Internet sites better - the IP an attack came from, what site was attacked and how, what ModSecurity rule was triggered, and so forth. With this info, you can see whether a site needs an update, whether you ought to block IPs from accessing your hosting server, etcetera. Besides the third-party commercial security rules for ModSecurity we use, our admins include custom ones too whenever they come across a new threat that's not yet a part of the commercial bundle.