Aggregate Searchable Encryption With Result Privacy

Aggregate Searchable Encryption With Result Privacy

Dhruti P. Sharma, Devesh C. Jinwala
Copyright: © 2020 |Pages: 21
DOI: 10.4018/IJISP.2020040104
(Individual Articles)
No Current Special Offers


With searchable encryption (SE), the user is allowed to extract partial data from stored ciphertexts from the storage server, based on a chosen query of keywords. A majority of the existing SE schemes support SQL search query, i.e. 'Select * where (list of keywords).' However, applications for encrypted data analysis often need to count data matched with a query, instead of data extraction. For such applications, the execution of SQL aggregate query, i.e. 'Count * where (list of keywords)' at server is essential. Additionally, in case of semi-honest server, privacy of aggregate result is of primary concern. In this article, the authors propose an aggregate searchable encryption with result privacy (ASE-RP) that includes ASearch() algorithm. The proposed ASearch() performs aggregate operation (i.e. Count *) on the implicitly searched ciphertexts (for the conjunctive query) and outputs an encrypted result. The server, due to encrypted form of aggregate result, would not be able to get actual count unless having a decryption key and hence ASearch() offers result privacy.
Article Preview


Searchable Encryption (SE) is a cryptographic mechanism to store encrypted data onto a cloud storage server in the way that the data can further be searched at the server side without compromising privacy. In typical SE schemes (Boneh, Di Crescenzo, Ostrovsky, & Persiano, 2004; Goh, 2003; Song, Wagner, & Perrig, 2000), data owner computes searchable ciphertexts and uploads them onto server. To enable search, data user issues a search token to server who then executes the defined search algorithm on ciphertexts without learning any information about original data (Figure 1).

Figure 1.

Searchable encryption


In SE, a searchable ciphertext comprises of an encrypted payload along with a list of encrypted keywords (to be searched). On the other hand, a search token consists of keyword(s) involved in search query chosen by data user. Practically, any SQL select query, i.e. 'Select * where (list of Values)' could be considered as a search query where 'Value' represents a keyword. With search operation (that implicitly applies token on ciphertext), the server marks '1' to all ciphertexts matching with query and '0' to all unmatched ciphertexts. Subsequently, data user offloads ciphertexts and performs decryption as per the requirements. However, in practice, there exist several applications concerning encrypted data analysis where data user requires fetching only a count of ciphertexts matched with the issued search token, instead of offloading all ciphertexts. One of such applications is given below.

Complete Article List

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