Admin API for Secure Environment Group Name: SEC Source: Giesecke & Devrient Meeting Date: 2015-09-07.

Slides:



Advertisements
Similar presentations
World Class Standards 1 SCP(11)0001 SCP Plenary #47 January 12-14, 2011 Title*: Update on TC M2M activities (and Smart Metering Mandate) Submitted by:
Advertisements

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:
Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: Agenda Item:
Methods Of Work Ad hoc Report TP#11 Source: Enrico Scarrone, Telecom Italia, Meeting Date:
IoT in ODL Lionel Florit, Principal Engineer, ODL ID lflorit
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.
Service Layer Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP16 Agenda Item:
App-ID Ad-Hoc Technical Issues TP AppID R02 Group Name: App-ID Ad-Hoc Group Source: Darold Hemphill, iconectiv,
Mechanism to support establishment of charging policies Group Name: WG2-ARC Source: InterDigital Meeting Date: TP8 Agenda Item:
App-ID Use Cases, Syntax and Attributes SEC App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,
App-ID Ad-Hoc Technical Issues TP AppID R01 Group Name: App-ID Ad-Hoc Group Source: Darold Hemphill, iconectiv,
Focus on developing RESTful API Group Name: TP Source: Shingo Fujimoto, FUJITSU (TTC), Meeting Date: Agenda Item:
In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:
3GPP Rel-13 Interworking discussions
In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:
Cryptography and Network Security (CS435) Part One (Introduction)
Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.
An operator’s perspective on support for different M2M deployment scenarios AT&T Group Name: TP Source: Farooq Bari, Jianrong Wang; AT&T;
WG1 status report to TP#17 Group Name: oneM2M TP17 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#17, Item 10.3,
Proposal for WG3 & WG5 work area split
Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.
Ontology Resource Discussion
Introducing concept of M2M-application data modeling Group Name: MAS Source: FUJITSU Meeting Date: Agenda Item: Semantics and Device Configuration.
OneM2M Challenges of M2M Security and Privacy
WG 2 Progress Report at TP#9 Group Name: oneM2M TP #9 Source: WG2 leadership Meeting Date: /21 Agenda Item: WG Reports.
SEC Conference calls following TP#11 Group Name: WG4 (SEC ) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information.
Access Control Status Report Group Name: ARC/SEC Source: Dragan Vujcic, Oberthur Technologies, Meeting Date: 09/12/2013 Agenda Item:
Proposed App-ID Format Group Name: Architecture, Security Source: Darold Hemphill, iconectiv, Meeting Date: Agenda Item:
3GPP Rel-13 Interworking discussions
Role Based Access Control In oneM2m
CCSDS Security Working Group Application Layer Security Discussion Mike Pajevski NASA/JPL October 2008.
ARC ordinary F2F meeting Seoul, June 2013 WG2 MEETING NOTES.
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.
Introducing Event handler Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.
Discussion about RESTful Admin API Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.
WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
Security API discussion Group Name: SEC Source: Shingo Fujimoto, FUJITSU Meeting Date: Agenda Item: Security API.
SEC #11 WG4 Status & Release 1 Outlook Group Name: Source:,, Meeting Date: Agenda Item:
WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
Streaming Session Support in oneM2M Framework Group Name: WG2 Source: George Foti, Ericsson Meeting Date: Work Item :WI GPP_Rel13_IWK.
Status of Active Work Items Level of Completeness Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:
TST Developing_SEC_TP Developing SEC TP - discussion Group Name: TST WG Source: Easy Global Market (EGM) Meeting Date:
Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:
ARC Possible_Collaboration_Area_with_OSGi.pptx Possible Collaboration Area with OSGi Group Name: ARC WG Source: Hiroyuki Maeomichi, NTT (TTC)
WPM ad-hoc group report TP#20 Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:
DM Collaboration – OMA & BBF: Deployment Scenarios Group Name: WG5 - MAS Source: Tim Carey, ALU, Meeting Date:
Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, Meeting Date: Agenda Item:
WG1 - REQ Progress Report at TP #11 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chairs Meeting Date: to Agenda Item: TP#11,
Directions for Release 3 Group Name: SEC Source: NEC Europe Ltd. Meeting Date: SEC22, Agenda Item: Discuss directions.
Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.
Virtual Local Area Networks In Security By Mark Reed.
GOCDB Status and Plans David Meredith John Casson
ArcGIS for Server Security: Advanced
Background Data Transfer
App-ID Ad-Hoc Technical Issues TP AppID R02
CSE Retargeting to AE, IPE, and NoDN Hosted Resources
CSE Retargeting to AE, IPE, and NoDN Hosted Resources
Build your own Gateway PEARC17, July 10th 2017
Possible options of using DDS in oneM2M
WPM ad-hoc group report TP#24
MAF&MEF Interface Specification discussion of the next steps
WPM ad-hoc group report TP#25
MobileMAN Workshop 2 Cambridge 2 –
Considering issues regarding handling token
CMDH Refinement Contribution: oneM2M-ARC-0397R01
Cloud Management Mechanisms
TIM Compression for No Buffered Unicast Traffic
Time Features Date: Authors: May 2009 Month Year
Presentation transcript:

Admin API for Secure Environment Group Name: SEC Source: Giesecke & Devrient Meeting Date:

Introduction To manage Secure Environments TS-0003 includes a “Security Administration” service responsible for the management of security (sensitive) functions and data within the SE  “SE management” SE management can take place locally or remotely In TP 18, the need to have dedicated API for administrative operation regarding security (in general) was agreed 2

Open topics Reference point for „SE / security administration“ has to be defined Dependency between Security Management and SE management need to be clarified Relation between Credential Management and SE Management need to be clarified 3

Proposal Reference point for SE / security administration – Mcs shall be used as reference point for SE administration SE management vs security management – Security features are encapsulated within an SE – The SE can be virtual or physical, e.g. unprotected memory area storing credentials is an SE with security level = 0 – SE management = security management SE management vs. credential management – Credentials are stored within the SE – The SE can be virtual or physical, e.g. an unprotected memory area storing credentials is an SE with security level = 0 – SE management = credential management (i.e. uses SE management functions) SE management shall also include mechanisms to manage (create, delete, update) sensitive functions such as cryptographic algorithms 4

Consequences Mcs reference point need to be accessible locally (within Field Domain) and remotely Mcs layer need to “translate” SE management API into SE technology dependent API – e.g. for secure elements, translation from oneM2M API into secure element (GP) APIs need to be done – Restful vs Service oriented approach – oneM2M API need to consider functionality of underlying technologies and their capabilities – Resources as proposed in SEC R01- RESTful_Administration_API_discussion need further study Currently SE management focus on Field Domain Node – Secure Environments within the infrastructure are currently out of scope 5