Cloud computing is a phenomenal distributed computing paradigm that provides flexible, low-cost on-demand data management to businesses. However, this so-called outsourcing of computing resources causes business data security and privacy concerns. Although various methods have been proposed to deal with these concerns, none of these relates to multi-clouds. This paper presents a practical data management model in a public and private multi-cloud environment. The proposed model BFT-MCDB incorporates Shamir's Secret Sharing approach and Quantum Byzantine Agreement protocol to improve trustworthiness and security of business data storage, without compromising performance. The performance evaluation is carried out using a cloud computing simulator called CloudSim. The experimental results show significantly better performance in terms of data storage and data retrieval compared to other common cloud cryptographic based models. The performance evaluation based on CloudSim experiments demonstrates the feasibility of the proposed multi-cloud data management model.
The area of XML database outsourcing, whereby the data owner enlists an external service provider to manage the storage and retrieval of their database, has been of increasing interest in recent years due to the relatively inexpensive nature of hardware/bandwidth, compared to the higher expense of in-house expert staff/software. As such it has become increasingly practical to use outsourced database solutions. However, as the service provider may not be fully trusted, XML database outsourcing introduces several security concerns that are new or more complex than those encountered in traditional database implementations. These include: data confidentiality, privacy, secure auditing, query assurance and secure and efficient storage. Of particular importance due to its relevance to most outsourced database models is query assurance - ensuring the database responds correctly to queries. In this paper, we propose the use of temporary time stamps and hash granularity to increase the efficiency of query assurance. This approach is tested against real datasets of varying type and size. Further, we consider how best to create time stamps and the issues associated with expiring versus distributed time stamp models.
In Chapter II, we discussed the different features available in Oracle™ that can be used to implement an object-oriented model. We will use those features in this chapter. The discussion in this chapter will be categorized based on the relationship types. There are three distinct relationship types that we have to consider in object-oriented modeling for implementation in object-relational databases: inheritance, association, and aggregation. Some manipulations will be needed in order to accommodate the features of these relationships.
We recall that an object-oriented model consists of two major aspects: the static and dynamic. The former covers the implementation of the data structure, which includes the object's attributes and relationships, whereas the latter is concerned with the object's operations, which is the implementation of object-oriented methods using SQL and PL/SQL. The static and dynamic parts of an object model actually form a nonseparated unit since accesses to the attributes of an object must be done through the available methods. This raises the concept of encapsulation.Request access from your librarian to read this chapter's full text.
A data stream can be considered as a sequence of examples that arrive continuously and are potentially unbounded, such as web page visits, sensor readings and call records. One of the serious and challenging problems that appears in a data stream is concept drift. This problem occurs when the relation between the input data and the target variable changes over time. Most existing works make an optimistic assumption that all incoming data are labelled and the class labels are available immediately. However, such an assumption is not always valid. Therefore, a lack of class labels aggravates the problem of concept drift detection. With this motivation, we propose a drift detector that reacts naturally to sudden drifts in the absence of class labels. In a novel way, the proposed detector reacts to concept drift in the absence of class labels, where the true label of an example is not necessary. Instead of monitoring the error estimates, the proposed detector monitors the diversity of a pair of classifiers, where the true label of an example is not necessary to determine whether components disagree. Using several datasets, an experimental evaluation and comparison is conducted against several existing detectors. The experiment results show that the proposed detector can detect drifts with less delay, runtime and memory usage.
Data security has become an important requirement for clients when dealing with clouds that may fail due to faults in the software or hardware, or attacks from malicious insiders. Hence, building a highly dependable and reliable cloud system has become a critical research problem. This paper presents BFT-MCDB (Byzantine Fault Tolerance Multi-Clouds Database), a practical model for building a system with Byzantine fault tolerance in a multi-cloud environment. The model relies on a novel approach that combines Byzantine Agreement protocols and Shamir's secret sharing approach to detect Byzantine failure in a multi-cloud computing environment as well as ensuring the security of the stored data within the cloud. Using qualitative analysis, we show that adopting the Byzantine Agreement protocols in the proposed BFT-MCDB model increases system reliability and enables gains in regard to the three security dimensions (data integrity, data confidentiality, and service availability). We also carry out experiments to determine the overheads of using the Agreement protocols.