2
AN ANALYTICAL RESEARCH ON IMPLEMENTATION AND RESEARCH ANALYSIS FOR DISTRIBUTED & INDEPENDENT ACCESS TO ENCRYPTED CLOUD
Atul Rana1
Research Scholar, Mansarowar Global University, Bhopal, India Shivshankar Prajapati2
Assistant Professor, Department of Computer Science, Mansarowar Global University, Bhopal, India
Abstract- The present generation prefers to store their data in the cloud, which brings them mobility and ease of extracting data from any device to anywhere in the world. Since data in the cloud is going to be placed online, it is important that these data in the clouds are well secured. The most important security challenge with data in the clouds is that the client was not aware of where the data is stored. Which may be preyed on by 3rd party clients or attackers. The data should be accessible solely by trustworthy parties that don’t embrace cloud suppliers and hence information should be encrypted. We propose Secure DBaaS architecture because this enables cloud tenants to acquire full advantage of DBaaS qualities, like accessibility, scalability and reliability, while not exposing unencrypted information to the cloud supplier.
Keywords: Security, Cloud, Secure, DBaaS, Reliability, Privacy 1 INTRODUCTION
In a cloud context, where basic data is set ion foundations of entrusted third parties.
ensuring information secrecy is of fundamental significance. These prerequisite forces clear information administration choices: original plain information must be available just by trusted parties that do exclude cloud suppliers, intermediaries, and Internet; in any entrusted setting, information must be encrypted. Fulfilling these objectives has distinctive levels of multifaceted nature relying upon the sort of cloud benefit. There are a few arrangements guaranteeing secrecy for the capacity as an administration worldview (e.g., [3], [4], [5]), while guaranteeing privacy in the database as an administration (DBaaS) worldview [6] is as yet an open research territory. In this specific circumstance, we propose Secure DBaaS as the main arrangement that permits cloud occupants to take full favorable position of DBaaS qualities, for example, accessibility, dependability, and versatile adaptability, without presenting decoded information to the cloud supplier. The configuration was inspired by a triple objective: to permit different, autonomous, and topographically appropriated customers to execute simultaneous operations on scrambled information, including SQL articulations that adjust the database structure; to save information confidentiality and consistency at the customer and cloud
level; to kill any middle of the road server between the cloud customer and the cloud supplier. The likelihood of consolidating accessibility, flexibility, and versatility of a run of the mill cloud DBaaS with information privacy is exhibited through a model of Secure DBaaS that backings the execution of simultaneous and autonomous operations to the remote scrambled database from many geologically dispersed customers as in any decoded DBaaS setup. To accomplish these objectives, Secure DBaaS coordinates existing cryptographic schemes, isolation instruments, and novel methodologies for administration of scrambled metadata on the entrusted cloud database. This paper contains a hypothetical dialog about answers for information consistency issues because of simultaneous and free customer gets to scrambled information.
In this specific circumstance, we can't make a difference completely homomorphism encryption plans [7] as a result of their inordinate computational unpredictability. The Secure DBaaS engineering is custom fitted to cloud stages and does not present any mediator intermediary or dealer server between the customer and the cloud supplier. Taking out any trusted middle of the road server enables Secure DBaaS to accomplish a similar accessibility, unwavering quality, and versatility levels of a cloud DBaaS.
Other proposition (e.g., [8], [9], [10], [11])
2
in light of moderate server(s) were viewed as impracticable for a cloud-based arrangement on the grounds that any intermediary speaks to a single point of disappointment and a framework bottleneck that constrains the fundamental advantages (e.g., adaptability, accessibility, and flexibility) of a database benefit sent on a cloud stage. Dissimilar to Secure DBaaS, models depending on a trusted halfway intermediary don't bolster the most regular cloud situation where geologically scattered customers can simultaneously issue read/compose operations and information structure adjustments to a cloud database. A huge arrangement of examinations in light of genuine cloud stages exhibit that Secure DBaaS is quickly material to any DBMS since it requires no alteration to the cloud database administrations. Different examinations where the proposed engineering is liable to the TPC-C standard benchmark for various quantities of customers and system latencies demonstrate that the performance of simultaneous read and compose operations not altering the Secure DBaaS database structure is similar to that of decoded cloud database.
Workloads including adjustments to the database structure are likewise upheld by Secure DBaaS, yet at the cost of overheads that appear to be satisfactory to accomplish the coveted level of information privacy. The inspiration of these outcomes is that system latencies, which are run of the mill of cloud situations, tend to cover the execution expenses of information encryption on reaction time. The general finishes of this paper are critical in light of the fact that out of the blue they exhibit the applicability of encryption to cloud Database benefits regarding attainability and execution. The rest of the piece of this paper is organized as takes after: Section 2 looks at our proposition to existing arrangements identified with privacy in cloud database administrations.
Areas 3 and 4 depict the general design and how it underpins its fundamental operations, individually.
Segment 5 reports some test assessment accomplished through the actualized model. Segment 6 diagrams the primary outcomes. Space constraint expects us to
delay the accepted security demonstrate in Appendix A, which can be found on the Computer Society Digital Library at http://doi. Ieee PC society.
org/10.1109/TPDS.2013.154, to depict our answers for simultaneousness and information consistency issues in Appendix B, accessible in the online supplemental material, to detail the model engineering in Appendix C, accessible in the online supplemental material.
2 COMPARATIVE GRAPH OF PROPOSED SYSTEM AND EXISTING SYSTEM
Fig. 1 Finally, Admin Can Logout from the System
3 ENCRYPTION TIMES OF TPC-C BENCHMARK OPERATIONS GROUPED BY TRANSACTION CLASS
UPDATE operations, the response times of Secured Baas SQL commands is most doubled, while the INSERT operation is, as expected, more critical from the computational point of view and it achieves a tripled response time with respect to the plain version. This higher over- head is motivated by the fact that an NSERT command has to encrypt all columns of a tuple, while an UPDATE operation encrypts just one or few values.
The second set of the experiments is oriented to eval- uate the impact of network latency and concurrency on the use of a cloud database from geographically distant clients. To this purpose, we mutate network latencies through the traffic shaping utilities available in the Linuxkernel by introducing synthetic delays from 20ms to 150ms in the client-server connection.
2
4 MODULES IN JAVA BACKGROUND About Java- At first the dialect was called as "oak" however it was renamed as "java"
in 1995.The essential inspiration of this dialect was the requirement for a stage free (i.e. engineering neutral)language that could be utilized to make programming to be installed in different shopper electronic gadgets. Java is a software engineer's dialect, Java is firm and steady. Aside from those limitation forced by the Internet condition. Java gives the software engineer, full control At long last Java is to Internet Programming where c was to System Programming.
(i) Importance of Java to the Internet- Java has profoundly affected the Internet.
This is on account of; java extends the Universe of items that can move about openly in Cyberspace. In a system, two classifications of articles are transmitted between the server and the PC. They are latent data and dynamic projects. in the territories of Security and likelihood. Be that as it may, Java tends to these worries and thusly, has opened the way to an energizing new type of program called the Applet.
(ii) Applications and Applets -An application is a program that keeps running on our Computer under the working arrangement of that PC. It is pretty much like one making utilizing C or C++ .Java's capacity to make Applets makes it vital. An Applet I san application, intended to be transmitted over the Internet and executed by a Java-good web program. An applet I really a modest Java program, powerfully downloaded over the system, much the same as a picture. Be that as it may, the distinction is, it is a savvy program, not only a media record. It can be respond to the client input and progressively change.
(iii) Java Architecture -Java design gives a convenient, hearty, high performing condition for advancement. Java gives versatility by gathering the byte codes for the Java Virtual Machine, which is then deciphered on every stage by the run-time condition. Java is a dynamic framework, ready to stack code when required from a machine in a similar room or over the planet.
(iv) Compilation of Code-When you aggregate the code, the Java compiler makes machine code (called byte code)for a speculative machine called Java Virtual
Machine(JVM). The JVM is gathered t executed the byte code. The JVM is made for the defeating the issue of likelihood.
The code is composed and gathered for one machine and deciphered on all machines .This machine is called Java Virtual Machine.
(v) Compiling and Interpreting Java Source Code-Amid run-time the Java mediator traps the byte code record into suspecting that it is running on a Java Virtual Machine. As a general rule this could be an Intel Pentium windows 95 orsun SPARCstation running Solaris or Apple Macintosh running framework and all could get code from any PC through web and run the Applets.
(vi) Simple-Java was intended to be simple for the Professional developer to learn and to utilize successfully. In the event that you are an accomplished C++
Programmer. Learning Java will arranged highlights of C++. The vast majority of the confounding ideas from C++ are either let well enough alone for Java or actualized in a cleaner, more congenial way. In Java there are few plainly characterized approaches to fulfill a given undertaking.
(vii) Object Oriented-Java was not intended to be source-code good with some other dialect. This permitted the Java group the opportunity to plan with a clear state. One result of this was a clean usable, practical way to deal with objects.
The question show in Java is basic and simple to broaden, while basic sorts, for example, numbers, are kept as superior non-objects.
(viii) Robust-The multi-stage condition of the web places remarkable requests on a program, on the grounds that the program must execute dependably in an assortment of frameworks. The capacity to make vigorous projects. Was given a
2
high need in the outline of Java. Java is entirely written dialect; it checks your code at assemble time and runtime. Java for all intents and purposes disposes of the issues of memory administration and arrangement area, which is totally programmed. In an elegantly composed Java program, all run-time blunders can and ought to be overseen by your program.
5 ALGORITHM PROCESS
Encryption algorithms are applied to encrypt the database. There are various encryption algorithms symmetric and asymmetric, but we will apply symmetric algorithm which proved key distribution only once to all tenants there will be no different private key related to every user.
1. Creation of database- In this module client creates its database and store data in the form or columns and rows. After creation of Database the client also creates its metadata which will help for later communication instead of whole database.
2. Selection of encryption and decryption algorithm- In this module we select the encryption algorithm to encrypt and decrypt the created database and its metadata. It will provide security to whole data of client which is to be uploaded on the cloud.
3. Cloud Database- Cloud Database is the service provider, which provides services to the tenants. All the encrypted data from data owner is uploaded on cloud which provide concurrent access to cloud DB to the geographically deployed clients.
Cloud DB contains encrypted database and its encrypted metadata.
We describe how to initialize a Secure DBaaS architecture from a cloud database service acquired by a tenant from a cloud provider. We assume that the DBA creates the metadata storage table that at the beginning contains just the database metadata, and not the table metadata. The DBA populates the database metadata through the Secure DBaaS client by using randomly generated encryption keys for any combinations of data types and encryption types, and stores them in the
metadata storage table after encryption through the master key. Then, the DBA distributes the master key to the legitimate users. User access control policies are administrated by the DBA through some standard data control language as in any unencrypted database.
In the following steps, the DBA creates the data of the encrypted database. It must consider the three field confidentiality attributes (COL, MCOL, and DBC). Let us describe this phase by referring to a simple but representative.
6 PROPOSED ALGORITHM STEP: FLOW CHART
7 EXISTING SYSTEM
Original plain data must be accessible only by trusted parties that do not include cloud providers, intermediaries, and Internet; in any entrusted context, data must be encrypted. Satisfying these goals has different levels of complexity depending on the type of cloud service.
There are several solutions ensuring confidentiality for the storage as a service paradigm, while guaranteeing confidentiality in the database as a service (DBaaS) paradigm is still an open research area.
(i) Disadvantages of Existing System- Cannot apply fully homomorphism encryption schemes because of their excessive computational complexity.
(ii) Proposed System-We propose a novel architecture that integrates cloud database services with data confidentiality and the possibility of executing
2
concurrent operations on encrypted data.
This is the first solution supporting geographically distributed clients to connect directly to an encrypted cloud database, and to execute concurrent and independent operations including those modifying the database structure. The proposed architecture has the further advantage of eliminating intermediate proxies that limit the elasticity, availability, and scalability properties that are intrinsic in cloud-based solutions.
Secure DBaaS provides several original features that differentiate it from previous work in the field of security for remote database services.
(iii) Advantages of Proposed System-The proposed architecture does not require modifications to the cloud database, and it is immediately applicable to existing cloud DBaaS, such as the experimented Postgre SQL Plus Cloud Database, Windows Azure and Expound .There are no theoretical and practical limits to extend our solution to other platforms and to include new encryption algorithm.
It guarantees data confidentiality by allowing a cloud database server to execute concurrent SQL operations (not only read/write, but also modifications to the database structure) over encrypted data. It provides the same availability, elasticity, and scalability of the original cloud DBaaS because it does not require any intermediate server.
Fig. 2 Existing System 8 IMPLEMENTATION
(i) Implementation and Testing- Usage is a standout amongst the most vital assignments in venture is the stage in which one must be alerts since every one of the endeavors attempted amid the task will be exceptionally intelligent. Execution
is the most vital stage in accomplishing fruitful framework and giving the clients certainty that the new framework is workable and successful. Each program is tried independently at the season of advancement utilizing the specimen information and has checked that these projects interface together in the path indicated in the program determination.
The PC framework and its condition are tried as per the general inclination of the client.
(ii) Implementation- The execution stage is less innovative than framework plan. It is basically worried about client preparing, and document transformation.
The framework might require broad client preparing. The underlying parameters of the framework ought to be changes because of a programming. A straightforward working system is given so the client can comprehend the distinctive capacities plainly and rapidly.
The distinctive reports can be gotten either on the inkjet or speck framework printer, which is accessible at the transfer of the client. The proposed framework is anything but difficult to actualize. As a rule usage is utilized to mean the way toward changing over another or updated framework outline into an operational one.
(iii) Testing - Testing is where the test information is arranged and is utilized for testing the modules separately and later the approval given for the fields. At that point the framework testing happens which ensures that all parts of the framework property works as a unit. The test information ought to be picked with the end goal that it went through all conceivable condition. As a matter of fact testing is the condition of execution which went for guaranteeing that the framework works precisely and proficiently before the genuine operation initiate. The accompanying is the depiction of the testing systems, which were done amid the testing time frame.
(iv) System Testing- Testing has turned into a basic piece of any framework or task particularly in the field of data innovation. The significance of testing is a technique for advocating, on the off chance that one is prepared to move further, be it to be check on the off chance that one is skilled to with stand the rigors of a specific circumstance can't
2
be underplayed and that is the reason testing before improvement is so basic. At the point when the product is created before it is given to client to client the product must be tried whether it is explaining the reason for which it is created. This testing includes different sorts through which one can guarantee the product is solid. The program was tried consistently and example of execution of the program for an arrangement of information are rehashed.
Therefore the code was comprehensively checked for all conceivable right information and the results were additionally checked.
(v) Module Testing - To find mistakes, every module is tried separately. This empowers us to distinguish blunder and right it without influencing some other modules. At whatever point the program isn't fulfilling the required capacity, it must be adjusted to get the required outcome. In this way every one of the modules are separately tried from base up beginning with the littlest and most reduced modules and continuing to the following level. Every module in the framework is tried independently. For instance the activity characterization module is tried independently. This module is tried with various occupation and its estimated execution time and the aftereffect of the test is contrasted and the
outcomes that are arranged physically.
The correlation demonstrates that the outcomes proposed framework works effectively than the current framework.
Every module in the framework is tried independently. In this framework the asset grouping and occupation booking modules are tried independently and their relating comes about are gotten which decreases the procedure holding up time.
Coordination Testing
(vi) Integration Testing- After the module testing, the coordination testing is connected. While connecting the modules there might be chance for blunders to happen, these mistakes are adjusted by utilizing this testing. In this framework all modules are associated and tried. The testing comes about are extremely right.
Hence the mapping of occupations with assets is done accurately by the framework.
(vii) Acceptance Testing- At the point when that client fined no significant issues with its precision, the framework passers through a last acknowledgment test. This test affirms that the framework needs the first objectives, destinations and necessities set up amid examination without real execution which end wastage of time and cash acknowledgment tests on the shoulders of clients and administration, it is at last satisfactory and prepared for the operation.
Table 1 Test Cases
2
9 CONCLUSION
We propose a creative design that ensures secrecy of information put away in broad daylight cloud databases. Dissimilar to cutting edge approaches, our answer does not depend on a moderate intermediary that we consider a solitary purpose of disappointment and a bottleneck constraining accessibility and versatility of run of the mill cloud database administrations. A huge piece of the examination incorporates answers for help simultaneous SQL operations (counting proclamations changing the database structure) on scrambled information issued by heterogeneous and potentially topographically scattered customers. In the first set of experiments, we evaluate the overhead introduced when one SecureDBaaS client executes SQL operations on the encrypted database. Client and database server are connected through a LAN where no network latency is added. To evaluate encryption costs, the client measures the execution time of the 44 SQL commands of the TPC-C benchmark. TPC-C operations are grouped on the basis of the class of transaction: Order Status, Delivery, Stock Level, Pay-ment, and New Order. From this figure, we can appreciate that the encryption time is below 0.1 ms for the majority of operations and below 1 ms for almost all operations but two. The exceptions are represented by two opera- tions of the Stock Level and Payment transactions where the encryption time is two orders of magnitude higher.
This high overhead is caused by the use of the order pre-serving encryption that is necessary for range queries. We focus on the most frequently executed SELECT, INSERT, UPDATE, and DELETE commands of the TPC-C bench- marking order to evaluate the performance overhead of encrypted SQL operations.
REFERENCES
1. M. Armbrust et al., "A View of Cloud Computing," Comm. of the ACM, vol. 53, no. 4, pp. 50-58, 2019.
2. W. Jansen and T. Grance, "Rules on Security and Privacy in Public Cloud Computing,"
Technical Report Special Publication 800-144, NIST, 2019.
3. A.J. Feldman, W.P. Zeller, M.J. Freedman, and E.W. Felten, "SPORC: Group Collaboration Using Untrusted Cloud Resources," Proc. Ninth
USENIX Conf. Working Systems Design and Implementation, Oct. 2020.
4. J. Li, M. Krohn, D. Mazie` res, and D. Shasha,
"Secure Untrusted Data Repository (SUNDR),"
Proc. 6th USENIX Conf. Opearting Systems Design and Implementation, Oct. 2018.
5. P. Mahajan, S. Setty, S. Lee, A. Lenient, L.
Alvisi, M. Dahlin, and M. Walfish, "Terminal:
Cloud Storage with Minimal Trust," ACM Trans. PC Systems, vol. 29, no. 4, article 12, 2017.
6. H. Hacigu¨ mu¨ s¸, B. Iyer, and S. Mehrotra,
"Giving Database as a Service," Proc.
eighteenth IEEE Int'l Conf. Information Eng., Feb. 2019.
7. C. Nobility, "Completely Homomorphic Encryption Using Ideal Lattices," Proc. 41st Ann. ACM Symp. Hypothesis of Computing, May 2019.
8. R.A. Popa, C.M.S. Redfield, N. Zeldovich, and H. Balakrishnan, "CryptDB: Protecting Confidentiality with Encrypted Query Processing," Proc. 23rd ACM Symp. Working Systems Principles, Oct. 2019.
9. H. Hacigu¨ mu¨ s¸, B. Iyer, C. Li, and S.
Mehrotra, "Executing SQL over Encrypted Data in the Database-Service-Provider Model," Proc.
ACM SIGMOD Int'l Conf. Administration Data, June2020.
10. J. Li and E. Omiecinski, "Productivity and Security Trade-Off in Supporting Range Queries on Encrypted Databases," Proc.
nineteenth Ann. IFIP WG 11.3 Working Conf.
Information and Applications Security, Aug.
2019.
11. M. Armbrust et al., “A View of Cloud Computing,” Comm. of the ACM, vol. 53, no. 4, pp. 50-58, 2019.
12. W. Jansen and T. Grance, “Guidelines on Security and Privacy in Public Cloud Computing,” Technical Report Special Publication800-144, NIST, 2019.
13. A.J. Feldman, W.P. Zeller, M.J. Freedman, and E.W. Felten, “SPORC: Group Collaboration Using Untrusted Cloud Re-sources,” Proc.
Ninth USENIX Conf. Operating Systems Design and Implementation, Oct. 2018.
14. J. Li, M. Krohn, D. Mazie`res, and D. Shasha,
“Secure Untrusted Data Repository (SUNDR),”Proc. Sixth USENIX Conf. Opearting Systems Design and Implementation, Oct.
2019.
15. P. Mahajan, S. Setty, S. Lee, A. Clement, L.
Alvisi, M. Dahlin, and M. Walfish, “Depot:
Cloud Storage with Minimal Trust,” ACM Trans. Computer Systems, vol. 29, no. 4, article 12, 2019.
16. H. Haciguimüş, B. Iyer, and S. Mehrotra,
“Providing Database as a Service,” Proc. 18th IEEE Int’l Conf. Data Eng., Feb. 2020.
17. C. Gentry, “Fully Homomorphic Encryption Using Ideal Lattices,” Proc. 41st Ann. CM Symp. Theory of Computing, May 2019.
18. R.A. Popa, C.M.S. Redfield, N. Zeldovich, and H. Balakrishnan, “CryptDB: Protecting Confidentiality with Encrypted Query Processing,” Proc. 23rd ACM Symp. Operating Systems Principles, Oct. 2021.
19. H. Hacigümüş, B. Iyer, C. Li, and S. Mehrotra,
“Executing SQL over Encrypted Data in the Database-Service-Provider Model,” Proc. ACM
2
SIGMOD Int’l Conf. Management Data, June2021.
20. J. Li and E. Omiecinski, “Efficiency and Security Trade-Off in Supporting Range Queries on Encrypted Databases,” Proc.
19thAnn. IFIP WG 11.3 Working Conf. Data and Applications Security, Aug. 2020.
21. E. Mykletun and G. Tsudik, “Aggregation Queries in the Database-as-a-Service Model,”
Proc. 20th Ann. IFIP WG 11.3Working Conf.
Data and Applications Security, July/Aug.
2016.
22. D. Agrawal, A.E. Abbadi, F. Emekci, and A.
Metwally, “Database Management as a Service:
Challenges and Opportunities,”Proc.25th IEEE Int’l Conf. Data Eng., Mar.-Apr. 2019.
23. V. Ganapathy, D. Thomas, T. Feder, H. Garcia- Molina, and R. Motwani, “Distributing Data for Secure Database Services,” Proc .Fourth ACM Int’l Workshop Privacy and Anonymity in the Information Soc., Mar. 2019.
24. A Shamir, “How to Share a Secret,” Comm. of the ACM, vol. 22, no. 11, pp. 612-613, 2019.
25. M. Hadavi, E. Damiani, R. Jalili, S. Cimato, and Z. Ganjei, “AS5: A Secureearchable Secret Sharing Scheme for Privacy Preserving Database Outsourcing,” Proc. Fifth Int’l Workshop Autonomous and Spontaneous Security, Sept. 2019.
26. “Oracle Advanced Security,” Oracle Corporation, Apr. 2019.
27. G. Cattaneo, L. Catuogno, A.D. Sorbo, and P.
Persiano, “The Design and Implementation of a Transparent Cryptographic File System For Unix,” Proc. FREENIX Track: 2001 USENIX Ann. Technical Conf., Apr. 2021.
28. E. Damiani, S.D.C. Vimercati, S. Jajodia, S.
Paraboschi, and P. Samarati, “Balancing Confidentiality and Efficiency in Untrusted Relational Dbmss,” Proc. Tenth ACM Conf.
Computer and Comm. Security, Oct. 2021.
29. L. Ferretti, M. Colajanni, and M. Marchetti,
“Supporting Securityand Consistency for Cloud Database,” Proc. Fourth Int’l Symp.
Cyberspace Safety and Security, Dec. 2021.
30. “Transaction Processing Performance Council,”
TPC-C, http://www.tpc.org, Apr. 2021.
31. H. Berenson, P. Bernstein, J. Gray, J. Melton, E. O’Neil, and P.O’ Neil, “A Critique of AnsiSql Isolation Levels,” Proc. ACMSIGMOD, June 2019.
32. “Xeround: The Cloud Database,” Xeround, Apr.
2019.“ Postgres Plus Cloud Database,”
Enterprise DB,
http://enterprisedb.com/cloud-database, Apr.
2019.
33. “Windows Azure,” Microsoft corporation, http://www.windowsazure.com, Apr. 2019.
34. “Amazon Elastic Compute Cloud (Amazon Ec2),”Amazon Web Services (AWS), http://aws.amazon.com/ec2, Apr. 2021.
35. B. White, J. Lepreau, L. Stoller, R. Ricci, S.
Guruprasad, M. Newbold, M. Hibler, C. Barb, and A. Joglekar, “An Integrated Experimental Environment for Distributed Systems and Net- works,” Proc. Fifth USENIX Conf. Operating Systems Design and Implementation, Dec.
2020.
36. Fekete, D. Liarokapis, E. O’Neil, P. O’Neil, and D. Shasha, “Making Snapshot solation Serializable,” ACM Trans. Database Systems, vol. 30, no. 2, pp. 492-528, 2020.
37. Boldyreva, N. Chenette, and A. O’Neill, “Order- Preserving Encryption Revisited: Improved Security Analysis and Alternative Solutions,”
Proc. 31st Ann. Conf. Advances in Cryptology (CRYPTO’11),Aug. 2021
38. M. Armbrust et al., “A View of Cloud Computing,” Comm. of the ACM, vol. 53, no.
4, pp. 50 -58, 2020.
39. A.J. Feldman, W.P. Zeller, M.J. Freedman, and E.W. Felten, “SPORC: Group Collaboration Using Untrusted Cloud Resources,” Proc.
Ninth USENIX Conf. Operating Systems Design and Implementation, Oct. 2020.
40. J. Li, M. Krohn, D. Mazie` res, and D. Shasha,
“Secure Untrusted Data Repository (SUNDR),”Proc. Sixth USENIX Conf. Operating Systems Design and Implementation, Oct.
2020.
41. P. Mahajan, S. Setty, S. Lee, A. Clement, L.
Alvisi, M. Dahlin, and M. Walfish, “Depot:
Cloud Storage with Minimal Trust”, ACM Trans. Computer Systems, vol. 29, no. 4, article 12, 2021.
42. H. Hacigü mu ̈s ̧, B. Iyer, and S. Mehrotra,
“Providing Database as a Service Proc. 18th IEEEInt’l Conf. Data Eng. Feb.2021.
43. C. Gentry, “Fully Homomorphic Encryption Using Ideal Lattices”, Proc. 41st Ann. ACM Symp. Theory of Computing May 2019.
44. R.A. Popa, C.M.S. Redfield, N. Zeldovich, and H. Balakrishnan, “Crypt DB: Protecting Confidentiality with Encrypted Query Processing,” Proc. 23rd ACM Symp. Operating Systems Principles, Oct.2021.
45. J. Li and E. Omiecinski, “Efficiency and Security Trade- Off in Supporting Range Queries on Encrypted Databases,”Proc.19th Ann. IFIP WG11.3 Working Conf. Data and Applications Security, Aug. 2019.
46. V. Ganapathy, D. Thomas, T. Feder, H. Garcia- Molina, and R. Motwani, “Distributing Data for Secure Database Services,” Proc. Fourth ACM Int’l Workshop Privacy and Anonymity in the Information Soc., Mar. 2021.
