Towards secure elements for the Internet of Things: The eLock use case: Work in progress - Invited paper

Pascal Urien

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Security and trust are major prerequisites for the deployment of Internet of Things (IoT) infrastructures. In this paper we present secure elements providing TLS and DTLS stacks, and running the CoAP protocol dedicated to IoT systems. These secure elements are used in an electronic lock context, in which the lock is a CoAP server and the key a CoAP client. We define two main security domains one for key interaction with the lock, and the other for key generation. These two domains are associated to applications running in SIM cards managed by mobile applications. Key generators are hosted in secure elements plugged in key servers, built over the RACS protocol. We introduce an innovative double TLS concept that avoids application tampering by cloud provider. Finally we discuss scalability issues of this approach.

Original languageEnglish
Title of host publicationProceedings of the 2016 2nd Conference on Mobile and Secure Services, MOBISECSERV 2016
EditorsPascal Urien, Selwyn Piramuthu
PublisherInstitute of Electrical and Electronics Engineers Inc.
ISBN (Electronic)9781467396844
DOIs
Publication statusPublished - 23 Mar 2016
Externally publishedYes
Event2nd Conference on Mobile and Secure Services, MOBISECSERV 2016 - Gainesville, United States
Duration: 26 Feb 201627 Feb 2016

Publication series

NameProceedings of the 2016 2nd Conference on Mobile and Secure Services, MOBISECSERV 2016

Conference

Conference2nd Conference on Mobile and Secure Services, MOBISECSERV 2016
Country/TerritoryUnited States
CityGainesville
Period26/02/1627/02/16

Keywords

  • CoAP
  • DTLS
  • HCE
  • IoT
  • NFC
  • RACS
  • TLS

Fingerprint

Dive into the research topics of 'Towards secure elements for the Internet of Things: The eLock use case: Work in progress - Invited paper'. Together they form a unique fingerprint.

Cite this