Resilient cloud data storage services

Hemayamini Kurra, Youssif Al-Nashif, Salim Hariri

Research output: Chapter in Book/Report/Conference proceedingConference contribution

2 Scopus citations


With the advance of cloud computing technologies, there is a huge demand for computing resources and storage. Many organizations prefer to outsource their storage and other resources. As the data reside on the third parties data centers, security is becoming a major concern. In this paper we propose a Resilient Cloud Storage (RCS) architecture that addresses the major security issues for cloud storage such as access control confidentiality, integrity, and secure communications. Our resilient approach is based on moving target defense and key hopping techniques. Data is partitioned into a random number of partitions where different keys are used to encrypt each partition. We also show that by using key hopping technique, we can reduce smaller key length that is normally used to improve performance without compromising the security. Our experimental results show that we can improve performance by 50% when we use a key of length 512 when compared with certificate technique that uses key length of 2048.

Original languageEnglish (US)
Title of host publicationProceedings of the 2013 ACM Cloud and Autonomic Computing Conference, CAC 2013
StatePublished - 2013
Event2013 ACM International Conference on Cloud and Autonomic Computing, CAC 2013 - Miami, FL, United States
Duration: Aug 5 2013Aug 9 2013

Publication series

NameACM International Conference Proceeding Series


Other2013 ACM International Conference on Cloud and Autonomic Computing, CAC 2013
Country/TerritoryUnited States
CityMiami, FL


  • cloud computing
  • cloud storage
  • decryption
  • encryption
  • resilience

ASJC Scopus subject areas

  • Software
  • Human-Computer Interaction
  • Computer Vision and Pattern Recognition
  • Computer Networks and Communications


Dive into the research topics of 'Resilient cloud data storage services'. Together they form a unique fingerprint.

Cite this