Content deleted Content added
No edit summary Tag: Reverted |
→Relationship to Role-based Encryption: MOS:HEAD |
||
(41 intermediate revisions by 15 users not shown) | |||
Line 1:
'''Attribute-based encryption''' is a
A crucial security aspect of attribute-based encryption is
==Description==
Attribute-based encryption is provably<ref name="Herranz2017">{{cite journal | last1 = Herranz | first1 = Javier | title = Attribute-based encryption implies identity-based encryption | journal = IET Information Security | date = November 2017 | volume = 11 | issue = 6 | pages = 332–337 | issn = 1751-8709 | eissn = 1751-8717 | doi = 10.1049/iet-ifs.2016.0490 | pmid = | hdl = 2117/111526 | s2cid = 20290716 | url = | hdl-access = free }}</ref> a generalisation of [[identity-based encryption]].
==History==
== Types of attribute-based encryption schemes ==
There are mainly two types of attribute-based encryption schemes: Key-policy attribute-based encryption (KP-ABE)<ref name=":0" /> and ciphertext-policy attribute-based encryption (CP-ABE).<ref>{{Cite book|last1=Bethencourt|first1=J.|last2=Sahai|first2=A.|last3=Waters|first3=B.
In KP-ABE, users' secret keys are generated based on an access tree that defines the privileges scope of the concerned user, and data are encrypted over a set of attributes. However, CP-ABE uses access trees to encrypt data and users' secret keys are generated over a set of attributes.
== Relationship to role-based encryption ==
The related concept of [[role-based encryption]]<ref name="SuryakantBhise R.N pp. 15–20">{{cite journal | last1=SuryakantBhise | first1=Avdhut | last2=R.N | first2=Phursule | title=A Review of Role based Encryption System for Secure Cloud Storage | journal=International Journal of Computer Applications | publisher=Foundation of Computer Science | volume=109 | issue=14 | date=2015-01-16 | issn=0975-8887 | doi=10.5120/19255-0986 | pages=15–20| bibcode=2015IJCA..109n..15S | doi-access=free }}</ref> refers exclusively to access keys having roles that can be validated against an authoritative store of roles. In this sense, Role-based encryption can be expressed by Attribute-based encryption and within that limited context the two terms can be used interchangeably. Role-based Encryption cannot express Attribute-based encryption.
==Usage==
Attribute-based encryption (ABE) can be used for log encryption.<ref>Vipul Goyal, Omkant Pandey, Amit Sahai and Brent Waters, Attribute-Based Encryption for Fine-Grained Access Control of Encrypted Data ''[
===Challenges===
Although the ABE concept is very powerful and a promising mechanism, ABE systems suffer mainly from two drawbacks:
Other main challenges are:
Line 27 ⟶ 34:
A simple but constrained solution is to include a time attribute. This solution would require each message to be encrypted with a modified access tree {{samp|T0}}, which is constructed by augmenting the original access tree {{samp|T}} with an additional time attribute. The time attribute, {{samp|ζ}} represents the current ‘time period’. Formally, the new access structure {{samp|T0}} is as follows: {{samp|T0 = (T AND ζ)}}. For example, {{samp|ζ}} can be the ‘date’ attribute whose value changes once every day. It is assumed that each non-revoked user receives his fresh private keys corresponding to the ‘date’ attribute once each day directly from the mobile key server MKS (which is the central authority) or via the regional delegates. With a hierarchical access structure, the key delegation property of CP-ABE can be exploited to reduce the dependency on the central authority for issuing the new private keys to all users every time interval. There are significant trade-offs between the extra load incurred by the authority for generating and communicating the new keys to the users and the amount of time that can elapse before a revoked user can be effectively purged. This above solution has the following problems:
# Each user X needs to periodically receive from the central authority the fresh private key corresponding to the time attribute, otherwise X will not be able to decrypt any message.
# It is a lazy revocation technique.
# This scheme requires an implicit time synchronization (a loose time synchronization may be sufficient) among the authority and the users.
Line 41 ⟶ 48:
==Further reading==
*{{Cite journal|last1=Attrapadung|first1=Nuttapong|last2=Herranz|first2=Javier|last3=Laguillaumie|first3=Fabien|last4=Libert|first4=Benoît|last5=de Panafieu|first5=Elie|last6=Ràfols|first6=Carla|date=March 2012|title=Attribute-based encryption schemes with constant-size ciphertexts|journal=Theoretical Computer Science|language=en|volume=422|pages=15–38|doi=10.1016/j.tcs.2011.12.004|doi-access=free|hdl=10230/42258|hdl-access=free}}
*Herranz, Javier; Laguillaumie, Fabien; Ràfols, Carla (2010), Nguyen, Phong Q.; Pointcheval, David (eds.), "[https://link.springer.com/chapter/10.1007/978-3-642-13013-7_2 Constant Size Ciphertexts in Threshold Attribute-Based Encryption]", ''Public Key Cryptography – PKC 2010'', Springer Berlin Heidelberg, 6056, pp. 19–34, [[Doi (identifier)|doi]]:[https://link.springer.com/chapter/10.1007/978-3-642-13013-7_2 10.1007/978-3-642-13013-7_2], {{ISBN|978-3-642-13012-0}}, retrieved 2020-05-13
[[Category:Public-key cryptography]]
[[Category:Pairing-based cryptography]]
|