Who is responsible for hacking the site if the customer did not transfer it from the test hosting?

ALexxxD2015-11-02 17:36:14

Freelance

ALexxxD, 2015-11-02 17:36:14

I made a website for a customer on my test hosting. After the completion of the work, the customer did not transfer the site to him for 8 months. During this time, the site was hacked, backups are all crooked. Who is responsible for what in this situation?

Does the customer owe me hosting for 8 months + recovery work or do I have to answer to him for the fact that the site was hacked while it was not on his domain and hosting? We did not have any prior arrangements for such a case.

UPD
The site was restored and transferred to the customer.
I agreed that this work would be paid to me (the customer paid).
I did not take money for hosting, because something else of mine was hosted on it.
Conclusions made.

Answer the question

In order to leave comments, you need to log in

11 answer(s)

xmoonlight, 2015-11-05
@ALexxxD

Who is responsible for hacking the site if the customer did not transfer it from the test hosting?

I would reformulate the question:
1. You did not transfer a copy (archive of the finished site) of the work performed to the Customer - your fault.
2. You do not have a copy of the work done to restore the site - your fault.
3. You did not follow and warn the Customer about the possible consequences of continuing to use the test hosting - your fault.
4. You did not stop the work on the test hosting you paid for after receiving money for the work from the Customer - your fault.
5. You have not taken organizational measures to prevent a “point of no return” in case of hacking, failure of storage media, access policies (including password complexity, access from certain IP addresses, etc.), programmer errors and omissions when encoding a block verification of data coming from the user - your fault.
----------
From now on, keep an eye on these points.
And at this stage - help restore work and figure out how exactly the site was hacked and fix the vulnerability. This work should be FREE for the Customer in this current situation.

mukizu, 2015-11-02
@mukizu

Logically, the customer owes one way or another for hosting. (If, of course, he knew about the need to transfer, otherwise it’s not at all clear why you hosted some project. Did it - gave it away.)
The cracker (your cap) is responsible for hacking. Maintainability is the responsibility of the maintainer.
PS: If there were no agreements, then it is not at all clear how you want to negotiate (which ones, by the way, were there at all? Where and how are they fixed?) I
will leave the question of restoration work open.

Denis Ineshin, 2015-11-02
@IonDen

In general, this is your jamb. The customer may not even know the difference between test hosting and combat hosting.
Basically, you haven't done the job. Posting a site on a test hosting with passwords like admin+password is just for viewing and testing. Where is the next step?

Optimus, 2015-11-02
Pyan @marrk2

Your hosting, and even this site you made which was hacked.
Backups of your site on your hosting.
Who is to blame here? Finished customer! ))

Saboteur, 2015-11-02
@saboteur_kiev

Your mistake was that there were no clear agreements on the support of the site.
But if there was no agreement between you and the customer to support the site (regular backups, settings), then naturally you do not bear any responsibility, and it was the fault of the customer. Unfortunately, many customers do not even suspect that this needs to be done. So right now you need to agree on who is responsible for what. You can take these arguments that the contract was to create a site and give it to the customer, and not maintain it.

hostwell, 2015-11-02
@hostwell

If you did not agree on this, then no one is responsible. In general, for 8 months. could be agreed. A little nuisance, a lesson for the future

Ruslan Fedoseev, 2015-11-02
@martin74ua

Has the customer been given access to hosting management?

ALexxxD, 2015-11-02
@ALexxxD

I mean, I had to transfer it myself, and not he get access to the hosting or transfer it myself

Puma Thailand, 2015-11-03
@opium

well, if you developed a site and your hosting, then the jamb is also yours, or you left holes in the code or there are holes in your hosting.

Vlad Zhivotnev, 2015-11-03
@inkvizitor68sl

The correct answer is "close the test site from public access X days after the show". You can close it completely, you can hide it behind authorization.
Now the customer owes you for 8 months of hosting, but not for restoration. And it’s better not to lose face and transfer it to its hosting now and don’t demand money.

zooks, 2015-11-04
@zooks

Of course, you. Why host someone else's site without having backups.
Moreover, you charge for hosting, which means you are responsible for the safety of data.