Fast-Sec: an approach to secure Big Data processing in the cloud

Abstract

Fast-Sec: an approach to secure Big Data processing in the cloud http://researchonline.ljmu.ac.uk/7269/ Article LJMU has developed LJMU Research Online for users to access the research output of the University more effectively. Copyright © and Moral Rights for the papers on this site are retained by the individual authors and/or other copyright owners. Users may download and/or print one copy of any article(s) in LJMU Research Online to facilitate their private study or for non-commercial research. You may not engage in further distribution of the material or use it for any profit-making activities or any commercial gain.The version presented here may differ from the published version or from the version of the record. Please see the repository URL above for details on accessing the published version and note that access may require a subscription. Security is an important concern in computer systems, which is especially remarkable when the system has to handle large amounts of data and a number of different users accessing this data with different accessing permissions. Observing this demand, this work proposes an innovative approach to provide a security infrastructure support to Big Data Analytic in Cloud-based systems named Fast-sec. Fast-Sec handles systems with large volumes of data from heterogeneous sources, in which users may access the system by different platforms, consuming or providing data. The security infrastructure proposed in Fast-Sec provides an authentication mechanism for users and data access control adapted to high demands from cloud-based Big Data environment. The reported results show the adequacy of the proposed safety infrastructure to the cloud-based systems processing Big Data. LJMU Research OnlineApril 19, 2017 13:7 The International Journal of Parallel, Emergent and Distributed Systems Smart-

Raw Data Security by Using Elgamal and Sha 256 Public Key Algorithm

“…As for the decryption process, it should be matched hash first that sent by the sender with the aim to find out if the encrypted data has changed at the time of sender or is the original data of the sender [9]. Because if the data received does not have the same hash value it means that the data received (which has been encrypted) is not the original data or has changed [2], [20]. Therefore it could not be decrypted and to be read by unauthorized receiver [21].…”