14 ms·
With a co-lo, there are well defined demarcation points between customer and provider with regards to access privileges and security responsibilities. In the cl
by extension 17y ago
With a co-lo, there are well defined demarcation points between customer and provider with regards to access privileges and security responsibilities. In the cloud, those points are vague to non-existent, depending on the category of cloud service in question.
- anamax 17y ago> With a co-lo, there are well defined demarcation points between customer and provider with regards to access privileges and security responsibilities. And which of those keeps rackspace from installing rootkits before the OS?
- extension 17y agoTowards the less "cloudy" end of the service spectrum, such a practice becomes professionally embarassing, a breach of contract and ultimately criminal. At the other end, you have things like Google App Engine which, as far as I can tell, are free to do whatever they like with your data and offer no service level or security guarantees. If criminal law doesn't put you at ease, run your own servers, as I originally suggested.
- anamax 17y ago> ultimately criminal In other words, the answer to my question about which of the demarkation points provides security is "none of the above". Contract and criminal law apply to the cloud as well. As with every other kind of hosting, you must decide whether the contracts offered by a specific service suit your purposes.