Xiuping Li, Kaiwen Wang, Xiaolin Chang
4 min
Cloud storage allows users to outsource data, but searching encrypted data without revealing content remains a challenge. While Public Key Encryption with Equality Test (PKEET) allows servers to compare ciphertexts from different users without decryption, existing schemes often lack granular authorization, public verifiability, or the features required for a full-scale searchable encryption (SE) system. The authors propose a new primitive, AVPKEET, to address these gaps, and subsequently develop AVSE, a practical searchable encryption scheme built upon this primitive.
The authors demonstrate that AVPKEET is the first scheme to simultaneously provide ciphertext-file-level authorization and public verifiability. By binding authorization tokens to specific users, keywords, and unique nonces, the scheme ensures that tokens are non-transferable and non-replayable. The AVSE scheme extends this by adding:
Formal security analysis proves that the scheme satisfies OW-CCA2 security, token unforgeability, and verification soundness. Experimental results indicate that AVSE achieves the most compact token size (168 bytes) among comparative schemes, with performance overheads suitable for cloud deployment.
This research bridges the gap between theoretical cryptographic primitives and practical cloud storage needs. By enabling public verifiability, it removes the need to blindly trust cloud providers, while the fine-grained, non-transferable authorization mechanism prevents common security pitfalls like unauthorized token sharing and replay attacks. These improvements make PKEET-based searchable encryption significantly more viable for real-world, multi-user enterprise environments.
Cloud storage revolutionizes data management but raises conflicts between functionality and privacy. Public Key Encryption with Equality Test (PKEET), an advanced cryptographic technique, can enable multi-user searchable encryption (SE) through cross-key ciphertext comparison without shared keys. However, existing PKEET-based SE schemes lack ciphertext-file-level authorization, public verifiability, or SE-level support. This paper first proposes a novel PKEET scheme, AVPKEET (Authorized and Verifiable PKEET). It enables non-transferable and non-replayable authorization of ciphertext files, while supporting public verifiability, all without the need for trusted third parties. Then we propose an AVPKEET-based SE scheme, denoted as AVSE (Authorized and Verifiable SE), featuring one-time non-transferable tokens bound to users and nonces, batch operations, and fine-grained access control (ALL, PARTIAL, SINGLE). We prove OW-CCA2 security, token unforgeability, and verification soundness under standard assumptions. Experiment results demonstrate that AVSE achieves the most compact token size (168 bytes) while uniquely providing both ciphertext-file-level authorization and public verification, with acceptable overhead for cloud storage deployment.
Sam: That's the critical question. Their experiments show the search token—the permission slip the system generates—is notably compact. The paper reports this as the smallest token size in the current research literature, which suggests the system is practical for real cloud deployment despite the complexity underneath.
Alex: Any drawbacks? It sounds like a lot of problems solved at once.
Sam: Every design involves trade-offs. Right now, the system only supports searching for a single keyword at a time, and it works best when the file collection isn't changing constantly. There's also a more subtle limitation: the server can still observe which keywords you're searching for, even though it can't read the files themselves.
Alex: So the server knows what I'm looking for, even if it can't see what I find.
Sam: Exactly. Researchers refer to this as "pattern leakage"—it's a known challenge across this whole area of research. The paper points to a technique called Oblivious RAM as a potential direction for future work. The idea is to disguise real search requests by mixing them with decoy requests, so an observer can't tell what you're actually looking for.
Alex: So it's a solid foundation, but the problem of total search privacy isn't fully closed yet.
Sam: That's a fair summary. The system meaningfully advances what's possible—linking authorization tightly to the user, the keyword, and a one-time nonce, and doing so without a middleman. But the researchers are clear that further work remains, particularly on hiding search patterns entirely. It's a meaningful step, not a final answer.
Alex: Thanks for walking us through it, Sam. And thanks to everyone listening to ResearchPod.