Dear Daniel, please find below some text that I compiled based on the white parts in your document and a discussion with a cloud security expert at NSN. Kind regards, Gábor Trusted resources As resources (CPU, storage, netowork) are hosted by a different party, usually called the cloud provider, there must be methods to ensure that the client can safely use and rely on these resources, i.e. they can trust these resources, as if they would be under its physical control. Confidentiality. For storage resources, the data should in many cases be stored in an encrypted form, and if the data is deleted it must not be possible to restore it for any other party than the client (irrevocable erasure). Irrevocable erasure is not only needed for storage services but it is also needed for secured VM provisioning/deprovisioning, client/user management (regarding customer data, temporary memory, object storage), released memory (in increasing/decreasing context), shared-memory servers (cloud sevice hosting user). Besides encryption, proper partitioning also (even better) serves confidentiality, for example secured partitioning between public and private clouds, partitioning of resources (in context of isolation between VM), customer data isolation, disk resource partitioning, shared-memory servers. Integrity. Naturally, integrity of data and components related to resources should also be ensured by proper measures. Such data cover Virtual Appliance description, Elasticity Rules defined by Cloud users or Cloud administrators, Final Application Deployment Description, Component that will be in charge of the Iaas provider and Cloud service provisioning, VM image repository, Scripting and advanced toolkits provided for administrators and advanced users (interfaces and interoperability), collected data (Monitoring and metering). Authenticity. The authenticity of (the identity of) the resources should be ensured. For example, the identity of VMs should always be verified (with different passwords and authentication keys on different on different VMs to prevent from VM impersonation), the provisioning of the VM identity should be designed secure (e.g. if it relies on a key embedded into the VM, then special attention must be payed to the security of key distribution), The architecture of Cloud Hosting and the interconnection between the elements should also be designed with keeping security in mind. For example, firewalls and/or security gateways should be established on the border of corporate/administration domains. Furthermore, proper risk analysis approaches should also be applied during design, for example VM vulnerability analysis (for secured VM provisioning / deprovisioning) and security breach research. ________________________________ From: ext GIDOIN Daniel [mailto:daniel.gidoin at thalesgroup.com] Sent: Wednesday, June 29, 2011 12:46 AM To: Marton, Gabor (NSN - HU/Budapest); Seidl, Robert (NSN - DE/Munich); JULIAN PEREZ VILA Cc: BISSON Pascal Subject: FI-WARE - Security issues identified in WP4 input doc Dear NSN qand TID partn ers, Could you please urgently send me and the mailing list the security issues you identified and also text you proposed to be inserted by WP4. I send you my personal compilation. Thank you for focusing primarily on the text not highlighted in yellow in the attached document. I will write the text about the part highlighted in yellow. Naturally, if you find another security issues, please to complete my document. Hearing from you. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20110630/12aa2657/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy