ModSecurity in Cloud Web Hosting
ModSecurity can be found with every single cloud web hosting package which we offer and it's turned on by default for every domain or subdomain that you include via your Hepsia CP. If it disrupts any of your apps or you'd like to disable it for some reason, you'll be able to accomplish that through the ModSecurity area of Hepsia with just a click. You could also activate a passive mode, so the firewall will recognize potential attacks and maintain a log, but won't take any action. You'll be able to see detailed logs in the exact same section, including the IP address where the attack came from, what precisely the attacker attempted to do and at what time, what ModSecurity did, etcetera. For optimum protection of our clients we use a collection of commercial firewall rules blended with custom ones that are included by our system admins.
ModSecurity in Semi-dedicated Hosting
ModSecurity is a part of our semi-dedicated hosting packages and if you decide to host your sites with us, there won't be anything special you'll need to do since the firewall is activated by default for all domains and subdomains that you include via your hosting CP. If required, you could disable ModSecurity for a given website or activate the so-called detection mode in which case the firewall shall still function and record information, but shall not do anything to stop potential attacks against your websites. In depth logs will be available inside your Control Panel and you'll be able to see which kind of attacks occurred, what security rules were triggered and how the firewall addressed the threats, what IP addresses the attacks originated from, etc. We employ two types of rules on our servers - commercial ones from a firm that operates in the field of web security, and custom made ones that our admins occasionally add to respond to newly identified risks promptly.
ModSecurity in VPS Web Hosting
Protection is essential to us, so we set up ModSecurity on all virtual private servers which are set up with the Hepsia CP by default. The firewall could be managed through a dedicated section in Hepsia and is turned on automatically when you include a new domain or create a subdomain, so you won't have to do anything manually. You shall also be able to deactivate it or activate the so-called detection mode, so it'll keep a log of potential attacks which you can later examine, but will not prevent them. The logs in both passive and active modes contain info about the kind of the attack and how it was prevented, what IP it originated from and other useful info which may help you to tighten the security of your Internet sites by updating them or blocking IPs, for example. Beyond the commercial rules we get for ModSecurity from a third-party security enterprise, we also implement our own rules as from time to time we identify specific attacks that aren't yet present within the commercial package. That way, we can easily boost the security of your Virtual private server immediately rather than awaiting an official update.
ModSecurity in Dedicated Servers Hosting
ModSecurity is offered by default with all dedicated servers that are set up with the Hepsia Control Panel and is set to “Active” automatically for any domain that you host or subdomain you create on the web server. Just in case that a web app does not operate properly, you could either turn off the firewall or set it to operate in passive mode. The latter means that ModSecurity shall maintain a log of any possible attack that might happen, but will not take any action to stop it. The logs created in active or passive mode will provide you with more details about the exact file that was attacked, the type of the attack and the IP it originated from, and so forth. This data shall allow you to determine what actions you can take to improve the security of your sites, including blocking IPs or performing script and plugin updates. The ModSecurity rules which we use are updated constantly with a commercial bundle from a third-party security provider we work with, but occasionally our administrators include their own rules too in the event that they discover a new potential threat.