Contextual Privacy Management in Extended Role Based Access Control Model

Abstract

Abstract. Typically, informational privacy aims to protect personal data from unauthorized access. In this paper, we propose to use the OrBAC model enhanced by some concepts to model privacy policies. We will take into account the concepts of consent, accuracy, purposes of the access and provisional obligation within role-based access control model. First, we focus on modelling of the requirement of the data owner consent before delivering the sensitive data. The subscriber defines that he must be notified before terminating the access. The access is delayed until the satisfaction of this condition.On the other hand, the accuracy of the sensitive data is usually underestimated within privacy models. We design an object hierarchy based on predefined accuracy levels. For this, we propose a derivation rule of sensitive objects. So, data owner can define authorisations based on different object accuracies.Furthermore, access control models usually permit the access to the stored data based on the role of the requester. We propose to extend this concept to take into account the purpose of the access. For this, we take advantage of the OrBAC user-declared context.Finally, we propose in this work to model the provisional obligations after accessing personal information. Third parties must notify data controller about further usage over collected data.To validate our approach, we show how the resulting model can be used to model the privacy policy for a location-based service. This can be applied within a mobile operator organization.

Fine-grained privacy control for the RFID middleware of EPCglobal networks

“…The approach we apply in the EPCglobal middleware is policy-driven. It ensures the following features: (i) enforcing a privacy policy without interfering with the standard middleware interface, (ii) using an existing privacy-aware model [1] to store and manage privacy policy preferences, and (iii) taking into account the declared purpose, the accuracy and the consent dimensions as privacy requirements. To show the feasibility of our approach, we provide a proof-ofconcept prototype that we apply on the open-source software for track and trace Fosstrak [7].…”

KAPUER: A Decision Support System for Privacy Policies Specification

“…We defined the notion of meta-criterion to represent abstractions of access control models like the role in RBAC [11], views and activities in OrBAC [15], purposes hierarchies in PRBAC [12], etc. The prefix meta in the scientific vocabulary allows to designate a higher level of abstraction.…”

“…The abstraction of roles limits the number of rules. Other notions and abstractions have been introduced in access control models to facilitate the definition and management of authorization policies especially for privacy like the concept of purpose [12], sensitivity of a resource [13], trust [14], accuracy or consent [15]. These access control models offer the possibility to write high level rules that are suited to complex environment.…”

A privacy-aware access control model for distributed network monitoring

“…OrBAC provides a mature framework for managing contextual policies, and several extensions, e.g., for dynamically deploying security policies [40], whereas a privacy-enhancing version of OrBAC is presented in [43]. However, the contextual representation of privacy concepts decreases the flexibility of the resulting model, since it limits the integration of complex structures of actions (e.g., paths or subworkflows) that may benefit from automatically being evaluated at design time.…”

“…Although this could be modelled as a special context (like in [43]), we have chosen to treat purpose as a stand-alone concept, in order to highlight its significance regarding privacy-awareness, as well as distinguish it from realtime parameters and events. Thus, the Purposes (Pu) set is defined, with its members forming hierarchies by means of OR (isA) relations modelling particularisation of a high level purpose to more specific ones; for instance, a purpose PerimeterSecurity specialises the more general purpose NetworkSecurity.…”