Posted by Nir Peled Last Friday, I attended MTBC (Metroplex Technology Business Council) “Solutions in the Cloud” conference in Dalla, Texas.The main event at the conference was a prestigious panel composed of three…
This year, April study conducted by independent research firm Ponemon Institute and sponsored by CA Technologies, surveyed 103 cloud service providers in the U.S. and 24 in Europe representing a mix of cloud service and deployment models. 70% said they allocate 10% or less of IT resources to security and control-related activity.
Who is most responsible for ensuring the security of the cloud resources ?
From an attacker’s perspective, cloud providers aggregate access to many victims’ data into a single point of entry. As the cloud environments become more and more popular, they will increasingly become the focus of attacks. Some organizations think that liability can be outsourced, but no, and I hope that we all understand it cannot. The contract with your cloud vendors basically means nothing, the ISVs or should I say the `SaaS providers` still holds the responsibility, so rather than focusing on contracts and limiting liability in cloud services deals, you should focus on controls and auditability.
Continue from my last post about NIST, I found the IEEE targets Cloud Interoperability Standards and for that matter the organization established 2 work groups
P2301 – Guide for Cloud Portability and Interoperability Profiles (CPIP): ”This guide advises cloud computing ecosystem participants (cloud vendors, service providers, and users) of standards-based choices in areas such as application interfaces, portability interfaces, management interfaces, interoperability interfaces, file formats, and operation conventions. This guide groups these choices into multiple logical profiles, which are organized toaddress different cloud personalities.”