Posted on October 28th, 2011
The infotech community’s latest buzzword is cloud. However, the whole concept of basically storing all essential data, at one online destination, is too scary a proposition for some businesses to embrace fully. Regardless of its apparent advantages-ease and economy, the systems’ supposed defense mechanism, its security firewall, remains a point of contention. A recent survey conducted by CSO reveals that these so-called security concerns are paramount in withholding senior managements from making the move to cloud-related technologies.
Cloud services are popularly believed to be no different than usual web hosting; thus, are expected to be susceptible to similar security lapses. Another fact, favoring the said argument, is that the cloud is maintained by service providers, akin to those that host websites; thus, the security and functionality of any system would inherently depend upon the quality of the providers’ network. Understandably, companies are then wary of losing all visible control over the security of their cloud-held information.
The cloud service, however, has amassed a significant following with millions worldwide, using the technology to host their personal and work-related information. Irrespective of the clouds ever-increasing use and popularity, the service largely remains under the service provider’s control – the provider then acts as chief regulator of all hosted data and is primarily responsible, deciding what kinds and types of security to employ to protect the said data. In an attempt to better standardize and fortify cloud security, certain officials are now suggesting that both providers and governments work towards drafting and enforcing a universal cloud security regulatory code.
The factors underlying a particular decision to go cloud are case specific. Users are advised to review various service providers and the respective strength of their networks before basically handing over complete protection of their hosted data – an analysis similar to the one they would conduct prior to incorporating any new system changes.