|Cloud in Flask|
Let’s take a look at the Electronic File versus Paper trust considerations. So in the simplest form you have a file on your local drive or a file folder with a paper inside. Both are easily accessible and both have points of failure (I will keep it simple).
- Hard-Drive could fail
- Someone without permission can gain access to the file
- You may delete the file unintentionally
- Could misplace or lose the file unintentionally
- Someone without permission may get access to the file
- May spill water on the file or some other type of medium failure
Countermeasures are easy for both types of situations and once you are comfortable with the base technology you can assign your team to provide protections for the electronic files that surpass the capabilities of the paper easily. In fact you know and trust your team and have direct accountability and monitoring. If necessary you still keep the paper but add electronic copies of it as well for easy access. This access could be on your private network or local computer. You are responsible for all standards, practices, policies and security of your information.
With this simple example it should be getting very clear what the problem is with “the Cloud” and why I was uneasy with the conversation. However, let’s take a look at the cloud. First we have to define it; Cloud computing is a marketing term/metaphor to represent a service to a community that provides one or more of the following:
- Computing Power
- Identity management
- Financial Controls
Again, I am keeping it simple and keeping that in mind we can imagine one or more server rooms being managed on or off premises for one or many groups of customers, and where access can be from any connectable device. For the purpose of this post I will assume that we are talking about a cloud provider versus your company creating a private cloud. In this model your employees connect through the Internet to the cloud and complete your companies business.
Let’s take a look at points of failure and again I am keeping it simple and I will put next to each point of failure a remedy:
- Local desktop system fails – your staff repairs the system
- Your network fails – your staff corrects the issue
- Your internet connection fails locally – your staff corrects the issue
- Your internet Service provider goes down – you place a trouble call in and they attempt to fix the problem within the service agreement. (If you have a backup internet service provider great and perhaps you need to keep everything local and on “the cloud”)
- Hard Drive fails on “the cloud” – the cloud provider has a backup and recovery plan that they manage and assure that it is followed ethically and in accordance to terms of service
- Network Connection for Cloud service provider fails – they place service call to internet service provider and attempt to get everything back online
- Local internet connectivity hardware fails for cloud service provider – provider works to correct issue in accordance to terms of service
- Someone without permission gains access to your companies cloud – service provider is responsible for keeping content secure within terms of service