1. Introducing User’s Role concept Group Name: WG2(ARC) and WG4(SEC) Source: Shingo Fujimoto, FUJITSU, shingo_fujimoto@jp.fujitsu.com Meeting Date: 2013-10-14 Agenda Item: Access Control

2. Introduction Role-Based Access Control had discussed collaborating WG2 and WG4 experts What is ‘Role’ is still not clear This contribution illustrates one thinking on the concept of Role in M2M Service 2

3. oneM2M-ARC-2013-0457-User_Role_Concept Role-based Access Control The permissions to perform certain operations are assigned to specific ‘Role’ Users are not assigned permissions directly RBAC steps: – Define Role: Allowed operations in specific context – Assign Role(s) for user Authorization is minimal requirement – Control user operations by assigned(=authorized) Role 3

4. oneM2M-ARC-2013-0457-User_Role_Concept Discussion What can be Role in M2M System ? How benefits on introducing RBAC ? The way forward … 4

5. oneM2M-ARC-2013-0457-User_Role_Concept User of M2M System Administrator – Responsible to keep system running (But no responsibility on data content) Users – Device Owner: uses system to host the device – Data Provider: uses system to manage data – Application Provider: uses system as data provider – Application User: uses system as one of Web Service 5

6. oneM2M-ARC-2013-0457-User_Role_Concept Characteristics of Data in M2M DataUse of DataOwnerUserNote Measured Value Collecting information for application Device Owner, Data Provider Device Owner, Application Provider, Application User Raw data collected from M2M Device, Note: updating data is only allowed Owner Processed Data Information generated from ‘Measured Value’ Data ProviderDevice Owner, Application Provider, Application User Device Settings Control the behavior of Device or Gateways Device OwnerDevice Owner, Administrator Settings are User Configurable Parameters Device Runtime Manage Device to keep it healthy Device OwnerDevice Owner, Administrator Firmware, Applications on Device 6

7. oneM2M-ARC-2013-0457-User_Role_Concept Some Example for RBAC My home doctor can read my health records, but other doctor cannot. => I can give permission to the hospital This device is not allowed to update firmware by user, but possible to authorized by vendor. => When the user obtained the authorization code from vendor become firmware update 7

8. oneM2M-ARC-2013-0457-User_Role_Concept Conclusion Removing the Access Control Rule attribute from Resource is suggested (Role can be defined within domain scope) Each CSF will determine if the operation is allowed or not by role of user Role can ease access control since access pattern in M2M system is not so vary. 8

9. oneM2M-ARC-2013-0457-User_Role_Concept [FYI]Difference of RBAC with ACL ACL assigns the permission to data object “RBAC differs from access control lists (ACLs), used in traditional discretionary access-control systems, in that it assigns permissions to specific operations with meaning in the organization, rather than to low level data objects. “ ACL does not support semantics: “The assignment of permission to perform a particular operation is meaningful” 9