Abstract: Sensitive data would be encrypted before uploading to the cloud due to the privacy issue. However, how to compare the encrypted data efficiently becomes a problem. Public Key Encryption with Equality Test (PKEET) provides an efficient way to check whether two ciphertexts (of possibly different users) contain the same message without decryption. As an enhanced variant, Attribute-based Encryption with Equality Test (ABEET) provides a flexible mechanism of authorization on the equality test. Most of the existing ABEET schemes are only proved to be secure in the random oracle model. Their security, however, would not be guaranteed if random oracles are replaced with real-life hash functions. In this work, we propose a construction of CP-ABEET scheme and prove its security based on some reasonable assumptions in the standard model. We then show how to modify the scheme to outsource complex computations in decryption and equality test to a third-party server in order to support thin clients.
Introduction
As sensitive data increasingly migrates to cloud storage, encryption has become a mandatory requirement for privacy. However, standard encryption introduces a significant efficiency hurdle: the difficulty of data deduplication. Cloud providers aim to save storage space by eliminating duplicate files, but if multiple users encrypt the same file with different keys, the provider cannot identify the underlying redundancy.
Public Key Encryption with Equality Test (PKEET) was developed to address this, allowing a server to verify if two ciphertexts represent the same plaintext without decrypting them. Attribute-Based Encryption with Equality Test (ABEET) advances this concept by integrating fine-grained access control. In an ABEET system, only users possessing specific attributes (e.g., "Manager" or "Security Auditor") are authorized to perform the equality test.
System Architecture
The proposed system involves three primary entities: the data sender, the cloud server, and the receivers. The sender encrypts messages under a specific access policy. The cloud server stores these ciphertexts and can perform encrypted data deduplication if authorized. Receivers can only decrypt or test ciphertexts if their personal attribute sets satisfy the policy embedded in the data.
Methodology
This research introduces a Ciphertext-Policy ABEET (CP-ABEET) scheme designed for the Standard Model. Most existing solutions rely on the "Random Oracle Model" (ROM), which assumes hash functions behave like perfectly random functions—a theoretical shortcut that may not hold true when implemented with real-world hashes like SHA-256. By proving security in the Standard Model, this scheme offers more robust guarantees for practical deployment.
Key Technical Components
- Linear Secret Sharing Schemes (LSSS): These are utilized to represent complex access policies and distribute secret "shares" across various attributes.
- Bilinear Pairings: This mathematical framework serves as the engine for the equality test, allowing the server to compute a matching value from two different ciphertexts only if the underlying messages are identical.
- Outsourcing (OCP-ABEET): To support "thin clients" like mobile or IoT devices, the authors developed an outsourced version. A third-party server handles the computationally intensive "transformation" of the ciphertext, leaving the client with only minimal arithmetic operations.
Performance and Security Results
The scheme's security is formally proven under the Decisional $q$-parallel Bilinear Diffie-Hellman Exponent ($q$-BDHE) assumption. It achieves "One-Wayness" (preventing message recovery even with a trapdoor) and "Indistinguishability" (preventing unauthorized users from identifying which message is contained in a ciphertext).
Evaluations using the Java Pairing-Based Cryptography (JPBC) library demonstrated that moving to the more rigorous Standard Model did not compromise efficiency:
- Test Algorithm: The new scheme outperformed leading ROM-based versions as the number of attributes increased.
- Outsourcing Efficiency: In the OCP-ABEET variant, local computation time for the user remained nearly constant regardless of policy complexity, as the cloud server absorbed the scaling workload.
Conclusion and Future Work
This work provides a secure and efficient mechanism for balancing data deduplication with fine-grained privacy. While ABE remains more computationally demanding than symmetric encryption, the outsourcing model makes it viable for resource-constrained devices. Future research will explore Attribute Revocation to handle dynamic user permissions and Multi-Authority models to remove the reliance on a single central key issuer.
Summary updated