A Continuous Sampling Method for Batch Data Auditing in Cloud Storage

A Continuous Sampling Method for Batch Data Auditing in Cloud Storage

Esther Daniel, Durga S., Vijila M.
Copyright: © 2021 |Pages: 12
DOI: 10.4018/IJISSS.2021040101
OnDemand:
(Individual Articles)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

Cloud storage offers online storage services to back up data and enables easy access to real-time data at any time and on the fly. The primary issue of security arises as the data is outsourced to remote servers that cause data loss and modifications to occur. Data corruptions or misbehaviours in the cloud service providers (CSP) have to be detected at low cost and promptly. The data outsourced to CSP by the data owners might suffer from cloud service provider misbehaviour, in particular unauthorized deletion of data by CSP to save storage space towards attracting potential clients. Adapting continuous sampling of random blocks as batches reduce the computation workload on the servers, thus detecting the modifications or corruptions if any without time delays. The corrupted data blocks are located with continuous sampling methods and the probability of detection is high.
Article Preview
Top

Introduction

Cloud Storage is the virtualized network of online storage servers that is progressively predominant with all its advantages in terms of agility, scalability, elasticity and multi-tenancy. Outsourcing data storage in the cloud environment has become an apparent service that can facilitate Data Owners (DO) to store their sensitive and non-sensitive data on to the remote servers. Outsourcing financial, health, multimedia, educational data to cloud storage server is beneficial as it eliminates the implications involved in the setup of primary storage infrastructure and its maintenance costs (Mell et al., 201; Yang et al., 2012). The Cloud Storage imposes various security issues which include: Trusting data stored in the cloud, insufficiency of provable security in Cloud Service Provider agreements, Data history, Provable Data Possession, Storage service of cloud used as online slack space, Data integrity, Lock-in, Data Remanence, Provenance, Confidentiality, Absence of User Control and Training Expertise, Addressing Trans-border Restrictions of data flow, Uncertain legal issues, Data disclosure to a government agency, Leaks of Breaches, Data Accessibility, Location of Data, Transfer and Retention (Geeta et al., 2018). Outsourcing data to Cloud Storage Service Provider is the best choice as it will provide gargantuan storage capacity, stable performance, high availability, and economical efforts on data maintenance and management. However, outsourcing data is not trustworthy and raises various security concerns over the data stored. In particular, the integrity of clients’ data is of great concern.

The Data Owners (DO) store enormous data on to the remote cloud servers. The Data Owners stores their sensitive data without holding a copy of the data trusting the storage provided by the Cloud Service Providers (CSP). To verify the data stored and to assure the data owners the soundness of their data there is a need for an integrity verification mechanism. It becomes a cumbersome task for the owners to keep verifying the soundness of their data. So, a Third-Party Auditor (TPA) is employed to carry out the integrity verification mechanism. It is of critical importance to assure the data owners' data are not misused or granted any unauthorized access. Also, the data stored are more vulnerable to drive crashes and can be deleted from the storage servers of the cloud. Data loss can occur in any infrastructure, no matter what kind of committed procedures the CSP’s would take. Several breaches can occur for the data stored. Unauthorized external users may try to achieve access privileges of the stored data. The internal attacks caused by CSPs are to gain control over the data as well as to delete the data to save storage resources. The CSPs to attract more users may delete the data that is less frequently accessed or not at all accessed for a prolonged period. The storage infrastructure can be prone to unexpected hardware faults that lead to data loss. Therefore, assurance to the DO concerning their data are stored without any modifications is critical. Hence there is a significant need for continuously monitoring the correctness of the data stored. The data stored in the cloud needs to be protected. The CSPs who maintains the data should not be able to sense any information form the stored encrypted data. The integrity verification mechanism must ensure privacy. The privacy of the data is ensured by using encryption, hashing and pseudo random functions. Figure 1 shows the entities involved in the cloud storage auditing as a service. The Data Owner (DO) who possess large data file to be stored on the remote cloud storage. There are several cloud servers (CS) that are maintained and managed by the cloud service provider (CSP). The servers maintained by CSPs are highly capable of computational resources as well as processes a large amount of storage space. The third party auditor has rich expertise and capability that the Users and Data Owners do not possess. The TPA is a semi-trusted entity to assess the cloud storage service securely on behalf of the user. The required updates by the users for their dynamic data are given continuously based on the application request. The DO encrypts the data and stores it on the servers at CSP and so the TPA relies only on the metadata and abstract information of the data thus preserving privacy.

Figure 1.

Architecture of Cloud Storage Auditing System

IJISSS.2021040101.f01

Complete Article List

Search this Journal:
Reset
Volume 15: 1 Issue (2024)
Volume 14: 4 Issues (2022): 3 Released, 1 Forthcoming
Volume 13: 4 Issues (2021)
Volume 12: 4 Issues (2020)
Volume 11: 4 Issues (2019)
Volume 10: 4 Issues (2018)
Volume 9: 4 Issues (2017)
Volume 8: 4 Issues (2016)
Volume 7: 4 Issues (2015)
Volume 6: 4 Issues (2014)
Volume 5: 4 Issues (2013)
Volume 4: 4 Issues (2012)
Volume 3: 4 Issues (2011)
Volume 2: 4 Issues (2010)
Volume 1: 4 Issues (2009)
View Complete Journal Contents Listing