+ All Categories
Home > Documents > UCON Model

UCON Model

Date post: 16-Feb-2016
Category:
Upload: lavi
View: 52 times
Download: 0 times
Share this document with a friend
Description:
UCON Model. 51000448 - Huỳnh Châu Duy. OUTLINE. UCON MODEL. Traditional access control. Mandatory Access Control (MAC) Discretionary Access Control (DAC) Role Based Access Control (RBAC) Focus in a closed system environment - PowerPoint PPT Presentation
Popular Tags:
29
UCON MODEL 51000448 - Huỳnh Châu Duy
Transcript
Page 1: UCON Model

UCON MODEL

51000448 - Huỳnh Châu Duy

Page 2: UCON Model

OUTLINEUCON

MODELWhat?

What for?When?Why?

CORE MODELS

16 basic models Example

COMPARISONTraditional

access control

DRM

CONCLUSION

Page 3: UCON Model

UCON MODEL

UCON MODEL

WHAT?

WHEN?

WHAT FOR?

WHY?

Page 4: UCON Model

TRADITIONAL ACCESS CONTROL Mandatory Access Control (MAC) Discretionary Access Control (DAC) Role Based Access Control (RBAC)

Focus in a closed system environment Not adequate for today’s distributed, network-

connected digital environment. Authorization only Decision is made before access No consumable rights Rights are pre-defined and granted to subjects

Page 5: UCON Model

DIGITAL RIGHT MANAGEMENT(DRM) Controlling and tracking access to and use of

digital information objects at client-side. Mainly focus on intellectual property

rights protection. Lack of access control model.

Page 6: UCON Model

PROBLEM

Page 7: UCON Model

UCON MODEL

UCON MODEL

WHAT?

WHEN?

WHAT FOR?

WHY?

Page 8: UCON Model

UCONABC MODEL COMPONENTS

Page 9: UCON Model

UCONABC MODEL COMPONENTSSubjects

Attributes Consumer Subjects Provider Subjects Identifiee Subjects

Objects Attributes

Rights

Page 10: UCON Model

WHAT IS UCONABC MODEL?

OBLIGATIONSAUTHORIZATIONSCONDITIONS

Page 11: UCON Model

AUTHORIZATIONS Functional predicates that have to be

evaluated for usage decision. Return whether the subject(requester) is

allowed to perform the requested rights on the object.

Authorizations can be either pre-authorizations (preA) or ongoing-authorizations (onA).

Page 12: UCON Model

OBLIGATIONS Functional predicates that verify mandatory

requirements a subject has to perform before or during a usage exercise.

Obligations can be either pre-obligations (preB) or ongoing-obligations (onB)

Page 13: UCON Model

CONDITIONS Environmental or system-oriented decision

factors. Unlike authorizations or obligations, condition

variables cannot be mutable. Evaluation of conditions cannot update any

subject or object attributes.

Page 14: UCON Model

OUTLINEUCON

MODELWhat?

What for?When?Why?

CORE MODELS

16 basic models Example

COMPARISONTraditional

access control

DRM

CONCLUSION

Page 15: UCON Model

CORE MODEL

The 16 basic UCONABC models

0immutable

1pre_update

2ongoing_updat

e

3post_updat

epreA Y Y N YonA Y Y Y YpreB Y Y N YonB Y Y Y YpreC Y N N NonC Y N N N

Page 16: UCON Model

CORE MODEL

AUTHORIZATIONS preA

onA

Page 17: UCON Model

CORE MODELpreApreA0

preA1

preA3

Example : - Pay-per-view (preUpdate) - Metered payment

(postUpdate)

Page 18: UCON Model

CORE MODELonAonA0

onA1

onA2

onA3

Example : Pay-per-Minutes

Page 19: UCON Model

CORE MODELOBLIGATIONS

preB

onB

Page 20: UCON Model

CORE MODELpreBpreB0

preB1

preB3

Example : Free Internet Service

Page 21: UCON Model

CORE MODELonBonB0

onB1

onB2

onB3

Page 22: UCON Model

CORE MODELCONDITIONS

preC

onC

Page 23: UCON Model

CORE MODEL Example :

Healthcare Education Long-distance phone Pre-paid phone card Click Ad within every 30 minutes Business Hour

Page 24: UCON Model

OUTLINEUCON

MODEL What? What for? When?Why?

CORE MODELS 16 basic models Example

COMPARISON Traditional access control DRM

CONCLUSION

Page 25: UCON Model

COMPARISON

TraditionalAccess Control

•RBAC•MAC•DAC

UCON MODEL

•Authorizations•Obligations•Conditions

Page 26: UCON Model

COMPARISON

DRM•pay-per-use•multiple credits

UCON MODEL

•Authorizations•Obligations•Conditions

Page 27: UCON Model

OUTLINEUCON

MODEL What? What for? When?Why?

CORE MODELS 16 basic models Example

COMPARISON Traditional access control DRM

CONCLUSION

Page 28: UCON Model

CONSLUSION UCONABC leaves open the architecture and

mechanisms for providing trusted attributes.

Page 29: UCON Model

Recommended