Knowledge base

Our job is to provide a quality hosting service, and it is therefore hugely in our interest to provide a swift response to the various attacks to which any Internet player may be subjected. We do our utmost to take maximum precautions.

Should a hacking attack occur, if the culprit can be traced and the computer has been compromised as a result of a security flaw on our part, we will register a complaint wherever necessary. If the responsibility lies with the customer (an out-of-date script or security patch that you failed to apply, for example), we alert the customer, who must then undertake to take the necessary steps as swiftly as possible (more information).

In short, if the integrity of the servers is at stake, we will take the necessary measures ourselves. If only the customer's web site has been compromised, it is up to the customer to take action: this is because we cannot prevent exploits relating to a bug in your PHP or other code which might be exploited, e.g. to compromise a database via SQL injection.It is up to you to perform any necessary validation on CGI variables in your code and ensure that they not exploitable. Conversely, we will take care of keeping the PHP and MySQL versions up to date. Any other application, e.g. a CMS or forum, installed by you must be regularly updated by you.

We have put various default measures in place, e.g. the restriction on deleting or creating files inside the /web directory from PHP scripts.

More detailed documentation on this subject is also available on Internet forums and web sites, which we leave it to the reader to consult. There is no such thing as absolute security in computing. But we strive to offer a reasonable level of security given the software and functionality required by our customers.