Detecting Malicious Third-Party Auditor and Privacy Preserving Protocol for Public Cloud
B. Rajani2, V. Purna Chandra Rao2

1B.Rajani, Research Scholar, Shri Jagdishprasad Jhabarmal Tibrewala University, Churela, Rajasthan.
2Purna Chandra Rao, Professor, Department of Computer Science and Engineering, SVIT, Hyderabad, India.

Manuscript received on 20 August 2019. | Revised Manuscript received on 01 September 2019. | Manuscript published on 30 September 2019. | PP: 1640-1644 | Volume-8 Issue-11, September 2019. | Retrieval Number: K18730981119/2019©BEIESP | DOI: 10.35940/ijitee.K1873.0981119
Open Access | Ethics and Policies | Cite | Mendeley | Indexing and Abstracting
© The Authors. Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open access article under the CC-BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/)

Abstract: Cloud computing is an anticipated and an inevitable solution for large storage capacities, the virtual presence of ownership and universal accessibility which extends the boundaries of a user today. These benefits also open up a challenge for being too exposed for welcoming attackers to steal potential information from those cloud environments. Irrespective of types of data, information stored on these cloud environments vary from databases to the coding of software and raw and processed information of various organizations, including governments. To ensure confidentiality and integrity of data input from various users, cloud service providers employ third-party auditors to verify the safety measures are intact and maintained. As the name predicts, an auditor may not possess a responsibility to protect the data after their intended verification is over. Third-Party Auditors have the function of confirming that the saved data has the same integrity as of original data, does not seek any information shortly to disturb the integrity and finally do not introduce any loopholes for new attacking attempts from external sources. This proposal intends to derive a mechanism to limit the resources provided to third party auditors in the architecture. The location of data and users protected in this approach along with locking of data segments to enhance the security of the architecture. The simulation results compare the technique and prove that this method outperforms the previous techniques when addressing the sturdiness, communication complexity, and time consumption concerns.
Keywords: Public auditing, Privacy-preserving, third party auditor (TPA),
Scope of the Article: