Ciphertext-policy attribute based encryption supporting access policy update

Yinhao Jiang, Willy Susilo, Yi Mu, Fuchun Guo

Research output: Book chapter/Published conference paperConference paperpeer-review

6 Citations (Scopus)


Attribute-based encryption (ABE) allows one-to-many encryption with static access control. In many occasions, the access control policy must be updated and the original encryptor might be required to re-encrypt the message, which is impractical, since the encryptor might be unavailable. Unfortunately, to date the work in ABE does not consider this issue yet, and hence this hinders the adoption of ABE in practice. In this work, we consider how to efficiently update access policies in Ciphertext-policy Attribute-based Encryption (CP-ABE) systems without re-encryption. We introduce a new notion of CP-ABE supporting access policy update that captures the functionalities of attribute addition and revocation to access policies. We formalize the security requirements for this notion, and subsequently construct two provably secure CP-ABE schemes supporting AND-gate access policy with constant-size ciphertext for user decryption. The security of our schemes are proved under the Augmented Multi-sequences of Exponents Decisional Diffie-Hellman assumption.
Original languageEnglish
Title of host publicationProvable Security
Subtitle of host publicationLecture Notes in Computer Science
Number of pages20
ISBN (Electronic)9783319474229
ISBN (Print)9783319474212
Publication statusE-pub ahead of print - 13 Oct 2016
EventProvable Security 10th International Conference: ProvSec 2016 - Nanjing, China
Duration: 10 Nov 201611 Nov 2016 (Conference proceedings) (Front matter)

Publication series

NameLecture Notes in Computer Science
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349


ConferenceProvable Security 10th International Conference
Internet address


Dive into the research topics of 'Ciphertext-policy attribute based encryption supporting access policy update'. Together they form a unique fingerprint.

Cite this