Contextual Privacy Management in Extended RBAC Model Nabil Ajam, - - PowerPoint PPT Presentation

contextual privacy management in extended rbac model
SMART_READER_LITE
LIVE PREVIEW

Contextual Privacy Management in Extended RBAC Model Nabil Ajam, - - PowerPoint PPT Presentation

Contextual Privacy Management in Extended RBAC Model Nabil Ajam, Nora Cuppens, Frdric Cuppens 24 september 2009 page 1 Workshop DPM Nabil Ajam Plan Introduction Motivation to use RBAC models Privacy requirements as OrBAC


slide-1
SLIDE 1

Nabil Ajam

page 1 Workshop DPM

Contextual Privacy Management in Extended RBAC Model

Nabil Ajam, Nora Cuppens, Frédéric Cuppens 24 september 2009

slide-2
SLIDE 2

Nabil Ajam

page 2 Workshop DPM

Plan

Introduction Motivation to use RBAC models Privacy requirements as OrBAC contexts Use case Conclusion

slide-3
SLIDE 3

Nabil Ajam

page 3 Workshop DPM

Background

Enhanced services extensively use sensitive

information

New services threaten user’s privacy

  • More and more acceptance of such services:

community service, location service...

International organisations tend to institute

privacy principles

  • Common acceptance of the OECD requirements

(1980)

slide-4
SLIDE 4

Nabil Ajam

page 4 Workshop DPM

Privacy definition

Sensitive data

  • Any data that can be used to identify directly or

indirectly a physical person

Privacy is

  • The demands from individuals, groups and

institutions to determine by themselves when, how and to what extent information about them is to be communicated to others

Data owner

  • The subject, who the sensitive data is referred to
slide-5
SLIDE 5

Nabil Ajam

page 5 Workshop DPM

Context of work: Three actors for LBS

Operator is the organization that collects, stores and

discloses private information about subscribers

Assumption: Subscribers trust the operator organisation Subscribers can define the privacy policy

  • Authorized service providers
  • Different object accuracies
  • Purpose as user-declared context
  • A set of access objectives declared by the data owner
  • Provisional obligation
  • Consent requirement before delivering data
slide-6
SLIDE 6

Nabil Ajam

page 6 Workshop DPM

Motivation

Location services are able to track subscribers

continuously

Idea: Define one model for access control and

privacy control

Access Control Model

slide-7
SLIDE 7

Nabil Ajam

page 7 Workshop DPM

Plan

Introduction Motivation to use RBAC models Privacy requirements as OrBAC contexts Use case Conclusion

slide-8
SLIDE 8

Nabil Ajam

page 8 Workshop DPM

Related works

P-RBAC (Purpose-based RBAC)

  • A dedicated langage to express privacy conditions
  • Definition of obligations

Purpose-Based Access Control and PuRBAC (Purpose-

Aware RBAC)

  • Intended purposes
  • Access purposes
  • Three types of conditions: Constraints, pre-obligations, post-
  • bligations
slide-9
SLIDE 9

Nabil Ajam

page 9 Workshop DPM

Motivation

Common acceptance of RBAC model to express security

policy

  • Reuse existing model
  • One model for access and privacy control

Extension of RBAC model

  • Support of dynamic and environment parameters through

contexts

  • Possibility to integrate the majority of privacy requirements
  • Example: OrBAC model

Integrate privacy for NGN services

slide-10
SLIDE 10

Nabil Ajam

page 10 Workshop DPM

OrBAC model

Two abstraction levels

  • Concrete: subject, action, object
  • Abstract: role, activity, view

Policy specification based on the abstract entities:

permission, prohibition, obligation, dispensation

  • Permission(org, role, activity, view, context)

Five context types:

  • Spatial
  • Temporal
  • Provisional
  • User-declared
  • Prerequisite
slide-11
SLIDE 11

Nabil Ajam

page 11 Workshop DPM

Plan

Introduction Motivation to use RBAC models Privacy requirements as OrBAC contexts Use case Conclusion

slide-12
SLIDE 12

Nabil Ajam

page 12 Workshop DPM

Privacy requirements

OECD guidelines (initially concern transborder

flow), which are adopted by western countries

  • Collection limitation (owner consent)
  • Data quality (need to know)
  • Purpose specification
  • Use limitation (owner consent)
  • Security safeguards
  • Openess
  • Individual participation
  • Accountability
slide-13
SLIDE 13

Nabil Ajam

page 13 Workshop DPM

Privacy requirements : Consent

Data owner can require his consent before

delivering his location by the operator

Consent is needed either :

  • Before data collection
  • After data collection

User preference is stored within the « consent

preference » view by the operator

slide-14
SLIDE 14

Nabil Ajam

page 14 Workshop DPM

Privacy requirements : Consent

Consent object attributes are :

  • Requestor
  • Target
  • Data-owner
  • NeedConsent

User consent is triggered when

slide-15
SLIDE 15

Nabil Ajam

page 15 Workshop DPM

Privacy requirements: Accuracy

Users can define several accuracies for the same

sensitive data

Sensitive data are modelled by an object hierarchy

based on the accuracy

Object derivation: compute objects based on the

accurate root object

Two accuracy levels

  • Anonymity level
  • Cloaked sensitive data (position)
  • K-anonymity algorithm
slide-16
SLIDE 16

Nabil Ajam

page 16 Workshop DPM

Privacy requirements: Accuracy

Anonymity is considered part of the object

accuracy

  • K-anonymity algorithm

Anonymity level depends on requestors

  • Each data owner can define several objects
slide-17
SLIDE 17

Nabil Ajam

page 17 Workshop DPM

Privacy requirements: Accuracy

slide-18
SLIDE 18

Nabil Ajam

page 18 Workshop DPM

Privacy requirements : purpose definition

Purpose as user-declared context Definition of purpose context:

  • Recipient: who takes advantage of the declared

purpose

  • Service providers
  • Data owner defines purposes
slide-19
SLIDE 19

Nabil Ajam

page 19 Workshop DPM

Provisional obligation

Enforce usage control after delivering locations Obligation

  • Activate condition: when obligation is needed
  • Violation condition

Obligation is triggered by a provisional context

activation

slide-20
SLIDE 20

Nabil Ajam

page 20 Workshop DPM

Plan

Introduction Motivation to use RBAC models Privacy requirements as OrBAC contexts Use case Conclusion

slide-21
SLIDE 21

Nabil Ajam

page 21 Workshop DPM

Location based service

Cellular network: Location data User: Data owner Requestor: service provider Role: fleet_management_1 Purpose: Optimise_route Consent: Yes Accuracy: Anonymous data Obligation: User notification

slide-22
SLIDE 22

Nabil Ajam

page 22 Workshop DPM

Plan

Introduction Motivation to use RBAC models Privacy requirements as OrBAC contexts Use case Conclusion

slide-23
SLIDE 23

Nabil Ajam

page 23 Workshop DPM

Conclusion

Contribution

  • Several privacy requirements
  • Accuracy
  • Consent
  • Purpose
  • Modelling privacy requirements
  • Consent context
  • Provisional context
  • User-declared context

Future works

  • Model other privacy principles
  • Remedies, retention, user participation
  • Policy administration
  • Privacy policy deployment
slide-24
SLIDE 24

Nabil Ajam

page 24 Workshop DPM

Thanks