TST-2015-0228-Developing_SEC_TP Developing SEC TP - discussion Group Name: TST WG Source: Easy Global Market (EGM) Meeting Date: 2015-11-9.

Slides:

Advertisements

Similar presentations

Access Control Mechanism Discussion

Advertisements

Call for test suites Group Name: REQ Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

Testing Framework TST 15 Source: Laurent Velez, ETSI, Meeting Date: TST Testing_framework.PPT.

App-ID Ad-Hoc Technical Issues TP AppID R02 Group Name: App-ID Ad-Hoc Group Source: Darold Hemphill, iconectiv,

Challenge Questions How good is our operational management?

Application Threat Modeling Workshop

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

Thoughts on oneM2M resource tree Group Name: WG2 Architecture at TP#7 (Sophia, October 2013) Source: Nicolas Damour, Sierra Wireless

Discussion on IEEE metrics guidelines Document Number: IEEE R0 Date Submitted: Source: Antonio BovoVoice:

Interoperability event proposal Group Name: WG TST Source: Sookhyun Jeon, TTA, Laurent Velez, ETSI, Meeting Date:

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:

End-to-End security definition Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date:

3GPP Rel-13 Interworking discussions

Pre-Commercial Procurement (PCP) Actions Open call in Objective 11.1 Calls for PCPs in specific public sector domains in objectives 5.3, 5.4 and 3.5

Work Group / Work Item Proposal Slide 1 © 2012 oneM2M Partners oneM2M-TP oneM2M_Work_Group_Work_Item_Proposal Group name: Technical Plenary Source:

Proposal for WG3 & WG5 work area split

Peering: A Minimalist Approach Rohan Mahy IETF 66 — Speermint WG.

WG 3 Progress Report at TP #7 Group Name: oneM2M TP #7 Source: Raymond Forbes, LM Ericsson, Meeting Date: /18 Agenda.

WPM ad-hoc group report TP#17 closing Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:

Primitive End-to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting.

CSCE 548 Secure Software Development Security Operations.

Interoperability event Sept 2015 Group Name: WG TST Source: Sookhyun Jeon, TTA, Laurent Velez, ETSI, Meeting Date:

Setting the context: Full costing and the financial sustainability of universities Country Workshop: POLAND EUIMA – Full Costing Project University of.

Technical questions on oneM2M certification Group Name: TST Source: JaeSeung Song KETI, TST WG Chair Meeting Date: Agenda.

Networked Systems Survivability CERT ® Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA © 2002 Carnegie.

Discussion for the next oneM2M release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI,

Test Purpose template discussion Group Name: TST WG Source: ETSI Meeting Date:

3GPP Rel-13 Interworking discussions

OneM2M Partnership Project. Contents Introduction Founding Partners Participation Scope & Objectives Structure Deliverables Contacts © 2013 oneM2M Partners.

App and Management End- to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm,

Discussion about RESTful Admin API Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.

Doc.: IEEE /0147r0 Submission January 2012 Rolf de Vegt (Qualcomm)) Slide ai Spec Development Process Update Proposal Date:

M2M Service Layer – DM Server Security Group Name: OMA-BBF-oneM2M Adhoc Source: Timothy Carey, Meeting Date:

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

SEC #11 WG4 Status & Release 1 Outlook Group Name: Source:,, Meeting Date: Agenda Item:

Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.

Status of Active Work Items Level of Completeness Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:

Clarification of Access Control Mechanism on Rel-1 & Rel-2 Group Name: SEC ( ARC & PRO for information) Source: FUJITSU Meeting Date: Agenda.

Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date:

Conformance Test Development Process discussion Group Name: TST WG Source: InterDigital Meeting Date: TST Conformance_Test_Development_Procedures.

Feedbacks on oneM2M certification Group Name: TP Source: JaeSeung Song KETI, TST WG Chair Meeting Date: Agenda Item:

Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

ATS code development workflow Group Name: TST WG Source: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, Miguel.

Reasons for CSF Clean-up (Issues & Next Steps) Group Name: WG2 Source: Syed Husain – NTT DOCOMO Meeting Date: (ARC_9.3) Agenda Item: 6 DOC#:

Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, Meeting Date: Agenda Item:

2 nd oneM2M Interoperability Event Prof. Song JaeSeung (KETI, TST WG Chair) TST Introduction-to-2 nd -interop-event.

TST R01-MBT_for_test_suites_development Use of MBT for test suites development- discussion Group Name: TST WG Source: Easy Global Market (EGM)

Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.

TST TTCN-3_development_plan TTCN-3 development plan Group Name: TST WG Source: Easy Global Market (EGM) Meeting Date:

TST MBT_for_test_suites_development Use of MBT for test suites development- discussion Group Name: TST WG Source: Easy Global Market (EGM) Meeting.

3GPP Rel-13 Interworking discussions Group Name: TP #18 Source: Rejesh Bhalla, ZTE Corporation, Meeting Date: Agenda Item:

Status of Active Work Items Level of Completeness

App-ID Ad-Hoc Technical Issues TP AppID R02

Service Enabled AE (SAE)

Possible options of using DDS in oneM2M

Semantic testing in oneM2M

3GPP Rel-13 Interworking discussions

WPM ad-hoc group report TP#25

Invite IIC testbeds to oneM2M interops

Considering issues regarding handling token

Overview of E2E Security CRs

ATIS Cybersecurity DOCUMENT #: GSC13-GTSC6-12 FOR: Presentation

Pre-Execution Process Review Presentation

Service Layer Dynamic Authorization [SLDA]

BU IS GIG Chemical, Oil & Gas

Commission proposal for a new LIFE Regulation CGBN meeting

Discussion on TDL future

CCSA Considerations on M2M Consolidation

ETSI TC MTS WG TST introduction

Presentation transcript:

TST Developing_SEC_TP Developing SEC TP - discussion Group Name: TST WG Source: Easy Global Market (EGM) Meeting Date:

TST Developing_SEC_TP Background TST WG call for volunteers for TP development EGM mentioned a new project (ARMOUR) going to start on IoT security testing And got appointed as volunteer for SEC TP development Present slides aim at – Presenting the forthcoming ARMOUR project and possible contribution to TST WG – Raise questions related to development of SEC TP

TST Developing_SEC_TP ARMOUR overview ARMOUR: H2020 (EU funded) project – Develop test suites for IoT Security & Trust – Deploy testbeds supporting large scale IoT Security & Trust experiments (process & tools) – Propose Benchmarks, framework and label for Secure & Trusted large-scale IoT

TST Developing_SEC_TP Possible contribution OneM2M mentioned as a potential use case 1.Compliance testing Support development and execution of OneM2M compliance test suites related to security & trust 2.Vulnerability testing Consider end to end scenarios Build upon OneM2M risk analysis (TR0008) Identified contributors:

TST Developing_SEC_TP SEC TP edition questions List of requirements to be covered ? – TS0002 is still high level. What is targeted level? Do security APIs exist? Coherence & traceability of Test Purposes – SEC requirements may overlap with others. – Need for a list providing the overall list of TPs (‘Test Objective charter’) Example TST TS-0018: TP/oneM2M/CSE/DMR/CRE/BV/004 Check that the IUT rejects the creation of a RESOURCE_TYPE resource when AE has no privileges TS001-§11.3 : The Authentication procedure shall be implemented as specified in the oneM2M Security Solutions Technical Specification [TS0002].

TST Developing_SEC_TP Example of test objectives Derived from TS-0002 / SER Slide to be completed - The oneM2M System shall be able to provide mechanism for the protection of confidentiality of the geographical location information