ModSecurity is a plugin for Apache web servers that functions as a web application layer firewall. It is employed to prevent attacks toward script-driven websites by employing security rules which contain particular expressions. That way, the firewall can block hacking and spamming attempts and shield even Internet sites that aren't updated on a regular basis. For instance, numerous unsuccessful login attempts to a script administrative area or attempts to execute a particular file with the intention to get access to the script shall trigger specific rules, so ModSecurity shall block out these activities the minute it discovers them. The firewall is quite efficient as it monitors the whole HTTP traffic to a site in real time without slowing it down, so it could stop an attack before any harm is done. It furthermore maintains an exceptionally detailed log of all attack attempts that includes more information than standard Apache logs, so you can later examine the data and take extra measures to boost the security of your sites if needed.

ModSecurity in Shared Website Hosting

ModSecurity comes by default with all shared website hosting plans that we supply and it shall be activated automatically for any domain or subdomain which you add/create within your Hepsia hosting CP. The firewall has three different modes, so you could switch on and disable it with simply a click or set it to detection mode, so it shall keep a log of all attacks, but it will not do anything to stop them. The log for any of your sites shall feature elaborate information including the nature of the attack, where it came from, what action was taken by ModSecurity, etcetera. The firewall rules that we use are frequently updated and incorporate both commercial ones which we get from a third-party security firm and custom ones which our system admins include in case that they detect a new kind of attacks. In this way, the sites which you host here will be a lot more protected with no action required on your end.

ModSecurity in VPS Web Hosting

Security is essential to us, so we install ModSecurity on all virtual private servers which are made available with the Hepsia CP by default. The firewall can be managed through a dedicated section within 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 will also be able to deactivate it or switch on the so-called detection mode, so it'll maintain a log of possible attacks which you can later study, but won't stop them. The logs in both passive and active modes offer info regarding the kind of the attack and how it was prevented, what IP it originated from and other valuable data which might help you to tighten the security of your Internet sites by updating them or blocking IPs, for instance. Besides the commercial rules we get for ModSecurity from a third-party security firm, we also use our own rules because from time to time we identify specific attacks which are not yet present in the commercial pack. This way, we can easily improve the security of your Virtual private server in a timely manner as opposed to awaiting a certified update.

ModSecurity in Dedicated Servers Hosting

All our dedicated servers that are set up with the Hepsia hosting CP come with ModSecurity, so any program that you upload or install will be secured from the very beginning and you will not have to bother about common attacks or vulnerabilities. A separate section inside Hepsia will allow you to start or stop the firewall for any domain or subdomain, or turn on a detection mode so that it records info about intrusions, but doesn't take actions to stop them. What you will find in the logs shall enable you to to secure your Internet sites better - the IP an attack came from, what website was attacked as well as how, what ModSecurity rule was triggered, etcetera. With this data, you could see if a website needs an update, whether you need to block IPs from accessing your server, and so forth. Aside from the third-party commercial security rules for ModSecurity we use, our admins add custom ones as well whenever they discover a new threat which is not yet included in the commercial bundle.