Proceedings of the 2002 ACM Workshop on Privacy in the Electronic Society 2002
DOI: 10.1145/644527.644538
|View full text |Cite
|
Sign up to set email alerts
|

E-P3P privacy policies and privacy authorization

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
96
0
1

Year Published

2004
2004
2014
2014

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 107 publications
(106 citation statements)
references
References 7 publications
0
96
0
1
Order By: Relevance
“…Paul Ashley et al [5], defines a fine grained privacy model called as Platform for the Enterprise Privacy Practices (E-P3P). The E-P3P privacy policy defines, on certain data categories the actions to be performed by the data users.…”
Section: Motivation and Related Workmentioning
confidence: 99%
“…Paul Ashley et al [5], defines a fine grained privacy model called as Platform for the Enterprise Privacy Practices (E-P3P). The E-P3P privacy policy defines, on certain data categories the actions to be performed by the data users.…”
Section: Motivation and Related Workmentioning
confidence: 99%
“…Successively, it has been recognized that access decisions cannot depend only on the identity and authorization of the entity requesting the access, but it is also necessary to consider the consequences of an access [42]. The concept of obligation was thus integrated in access control frameworks (e.g., [12,[42][43][44]) to define the actions that must be taken when permissions are granted. Obligations are also used to restrict the set of permissible actions (i.e., actions that do not comply with obligations are not permitted) [13] and to specify the intended usage of data [15].…”
Section: Obligationmentioning
confidence: 99%
“…Privacy Engineering has been tackled by several research communities, such as Privacy Requirements Engineering [51][52][53], Privacy Policy and User Preference Specification [9][10][11], Privacy-Aware Access Control [12][13][14], Identity Management [54][55][56], Digital Rights Management [57], etc. Even though these fields are all important in the development of privacy-aware systems, we choose to only focus on Privacy Requirements Engineering, Privacy Policy and User Preference Specification, and Privacy-Aware Access Control as we see these fields as key topics for this article's intentions.…”
Section: Privacy Engineeringmentioning
confidence: 99%
See 1 more Smart Citation
“…For instance, P3P [17] and E-P3P (and also EPAL) [3] are languages that allow one to specify policies for privacy protection; however, the user can only hope that the private data host follows them.…”
Section: Introductionmentioning
confidence: 99%