Issues of Current Access Control Rule and New Proposal Introduction Group Name: ARC 21 Source: Wei Zhou, Datang, Meeting Date: 2016-01-18.

Slides:



Advertisements
Similar presentations
CMDH Refinement Contribution: oneM2M-ARC-0397
Advertisements

Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: Agenda Item:
Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.
Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.
Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:
OneM2M-MP Data_Model_Repository Establishing Data Model Repository for oneM2M Group Name: Method and Procedure Sub-commitee Source: WG3 chair.
Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: Agenda Item: TBD.
Mechanism to support establishment of charging policies Group Name: WG2-ARC Source: InterDigital Meeting Date: TP8 Agenda Item:
In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:
Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.
Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:
In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:
Answer the Questions Regarding Pending Issues on Access Control Group Name: WG4 SEC Source: LG Electronics Meeting Date: Agenda Item: SEC#11.4.
Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.
TS0001 Identifiers way forward Group Name: WG2 Source: Elloumi, Foti, Scarrone, Lu (tbc), Jeong (tbc) Meeting Date: Agenda Item: ARC11/PRO11.
App-ID Discussion Group Name: ARC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 31 July 2014 Agenda Item: TBD.
Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.
Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.
Access Control Status Report Group Name: ARC/SEC Source: Dragan Vujcic, Oberthur Technologies, Meeting Date: 09/12/2013 Agenda Item:
Status Report on Access TP8 Group Name: WG2 Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:
Node-Specific Resource Group Name: ARC&MAS Source: LGE, Meeting Date: Agenda Item: Contribution.
Introducing WI Proposal about Authorization Architecture and Policy Group Name: WG4 Source: Wei Zhou, Datang, Meeting Date: Agenda Item:
Introducing WI Proposal about Authorization Architecture and Policy Group Name: WG4 Source: Wei Zhou, Datang, Meeting Date: Agenda Item:
Interworking with an External Dynamic Authorization System Group Name: SEC WG Source: Qualcomm Inc., Wolfgang Granzow & Phil Hawkes Meeting Date: SEC#20.2,
Access Control Status Report Group Name: ARC/SEC Source: Dragan Vujcic, Oberthur Technologies, Meeting Date: 09/12/2013 Agenda Item:
OIC INTERWORKING OPERATIONAL PROCEDURE (ADDRESSING AND DISCOVERY) Group Name: Architecture WG Source: Kiran Vedula, Samsung Electronics,
Process for Documenting Resources related services and Alignment with Service Components Group Name: WG2-ARC-( ) Source: Ericsson Meeting Date:
E2EKey Resource Group Name: SEC WG Source: Qualcomm Inc., Wolfgang Granzow & Phil Hawkes Meeting Date: SEC#20.3, Agenda Item: End-to-End Security.
Routing Problem of the Current Architecture Group Name: ARC Source: Hongbeom Ahn, LG Electronics, Meeting Date: Agenda.
Different planes for the resource structure Group Name: WG5 – MAS and WG2 – ARC Source: Nicolas Damour, Sierra Wireless
M2M Service Subscription Profile Discussion Group Name: oneM2M TP #19.2 Source: LG Electronics Meeting Date: Agenda Item:
SE abstraction scenarios Group Name: SEC Source: Claus Dietze, Giesecke & Devrient Meeting Date: Agenda Item: WI SE abstraction.
ARC R02 Modelling operations – problem statement and proposal Group Name: ARC#19.3 Source: Joerg Swetina, NEC,
PRO/ARC and TST/PRO joint sessions at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:
Protocol Issues related to Plugtest Group Name: TST Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date: Agenda.
App End-to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date:
M2M Service Layer – DM Server Security Group Name: OMA-BBF-oneM2M Adhoc Source: Timothy Carey, Meeting Date:
LWM2M Interworking Proxy Procedures ARC Considerations
Attribute-level access control Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 16 Agenda Item: TBD.
Template proposal Group Name: PRO Source: Barbara PAreglio, NEC, Meeting Date: Agenda Item: input contribution.
Clarification of Access Control Mechanism on Rel-1 & Rel-2 Group Name: SEC ( ARC & PRO for information) Source: FUJITSU Meeting Date: Agenda.
Adding Non-blocking Requests Contribution: oneM2M-ARC-0441R01R01 Source: Josef Blanz, Qualcomm UK, Meeting Date: ARC 7.0,
Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.
Draft way Forward on Access Control Model and associated Terminology Group Name: SEC Source: Dragan Vujcic, Oberthur Technologies,
Subscription and Notification Issue Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: ~23 Agenda Item:
DM Execute Group Name: WG2/WG5 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.
Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.
Interworking with an External Dynamic Authorization System Group Name: SEC WG Source: Qualcomm Inc., Wolfgang Granzow & Phil Hawkes Meeting Date: SEC#20.1,
Resource subscription using DDS in oneM2M
oneM2M interop 3 issues and optimizations
Service Framework Proposal
CSE Retargeting to AE, IPE, and NoDN Hosted Resources
CSE Retargeting to AE, IPE, and NoDN Hosted Resources
Service Enabled AE (SAE)
Group multicast fanOut Procedure
2nd Interoperability testing issues
Possible options of using DDS in oneM2M
Issues of <locationPolicy> Discussion
Proposed design principles for modelling interworked devices
Discussion to clarify online/offline behavior
oneM2M Versioning Next Steps
ARC Proposed design principles for modelling services, datapoints and operations Group Name: ARC Source: Joerg Swetina, NEC
Considering issues regarding handling token
LWM2M Interworking with <mgmtObj> Resources
Summary of Access Control Rules Processing
CMDH Refinement Contribution: oneM2M-ARC-0397R01
Service Layer Dynamic Authorization [SLDA]
Summary of the MAF and MEF Interface Specification TS-0032
oneM2M interop 6 action point
Notification Target Discussion
Presentation transcript:

Issues of Current Access Control Rule and New Proposal Introduction Group Name: ARC 21 Source: Wei Zhou, Datang, Meeting Date: Agenda Item:

What are the Differences between Computer File and oneM2M Resource Tree in Access Control Access Control List (ACL):  Designed for Computer File System  File does not have sub-structure  ACL is OK for file access control oneM2M Resource Tree:  Designed for oneM2M System  Node in tree may have complicated sub-structure, e.g.,,  Currently using ACL for access control  ACL is not OK for the access control of oneM2M resource tree

Evaluation of Current ACP Rule : Example Scenario Scenario: AE1 and AE2 register to CSE1 AE1 and AE2 share data via Basic procedures: 1.AE2 makes a subscription to in order to get Notifications 2.AE1 creates in 3.CSE1 notifies the AE2 after AE1 creates a in 4.AE2 retrieves from

Evaluation of Current ACP Rule : Example Rules Access Control Rules: Rule-1: [(AE1, AE2), (Create), ()] Rul2-2: [(AE2), (Retrieve), ()] What we expect in access control are:  AE1 can only create in  AE2 can only create for notification about the change of in  AE2 can only retrieve in  AE1 and AE2 shall not create in

Evaluation of Current ACP Rule : Evaluation Rule-1: [(AE1, AE2), (Create), ()]: We expect AE1 can only create We expect AE2 can only create However what we get are: AE1 and AE2 can create any child resources in Rul2-2: [(AE2), (Retrieve), ()]: We expect AE2 can only retrieve However what we get are: AE2 can retrieve any attributes and child resources in

Evaluation of Current ACP Rule : Conclusion Current oneM2M access control rule is too weak. It cannot meet the security requirements of the oneM2M System in the aspect of access control. More powerful access control rules should be developed so that fine grained access control could be supported by the oneM2M System.

New Proposal : Rule Format Current access control rule format (3-tuple): [accessControlOriginators, accessControlOperations, accessControlContexts] Proposed access control rule format (6-tuple): [accessControlResources, permittedAttributes, permittedChildResources, accessControlOriginators, accessControlOperations, accessControlContexts]  accessControlResources: mandatory parameter, representing the set of address of the resources that shall be protected by this access control rule.  permittedAttributes: optional parameter, representing the set of permitted attributes under the resources defined in the accessControlResources.  permittedChildResources: optional parameter, representing the set of permitted child resources under the resources defined in the accessControlResources.  accessControlOriginators: same as the existing definition.  accessControlOperations: same as the existing definition.  accessControlContexts: same as the existing definition.

New Proposal : Example Rules and Evaluation New Access Control Rule Examples: New Rule-1: [( ); (); ( ); (AE1); (Create); ()] New Rule-2: [( ); (); ( ; (AE2); (Create); ()] New Rule-3: [( ); (); ( ); (AE2); (Retrieve); ()] What we expect in access control are:  AE1 can only create in the  AE2 can only create for notification about the change of in the  AE2 can only retrieve in the  AE1 and AE2 shall not create in the Old Access Control Rules: Rule-1: [(AE1, AE2), (Create), ()] Rul2-2: [(AE2), (Retrieve), ()]

New Proposal : Conclusion 1.Compared with current rule format the new rule format can more accurately describe access control rules, and can be used for supporting fine grained access control. 2.The new access control rule contains the information of resources and Originators, so the access control rules belonging to different resources can be organized into one access control policy. This can simplify the access control policy management.

Thank You! Q&A Issues of Current Access Control Rule and New Proposal Introduction