A distributed security mechanism for Resource-Constrained IoT Devices

James King, Ali Ismail Awad

Research output: Contribution to journalArticlepeer-review

58 Citations (Scopus)

Abstract

Internet of Things (IoT) devices have developed to comprise embedded systems and sensors with the ability to connect, collect, and transmit data over the Internet. Although solutions to secure IoT systems exist, Class-0 IoT devices with insufficient resources to support such solutions are considered a resourceconstrained in terms of secure communication. This paper provides a distributed security mechanism that targets Class-0 IoT devices. The research goal is to secure the entire data path in two segments, deviceto- gateway and gateway-to-server data communications. The main concern in the provided solution is that lighter security operations with minimal resource requirements are performed in the IoT device, while heavier tasks are performed in the gateway side. The proposed mechanism utilizes a symmetric encryption for data objects combined with the native wireless security to offer a layered security technique between the device and the gateway. In the offered solution, the IoT gateways provide additional protection by securing data using Transport Layer Security (TLS). Real-time experimental evaluations have demonstrated the applicability of the proposed mechanism pertaining to the security assurance and the consumed resources of the target Class-0 IoT devices.

Original languageEnglish
Pages (from-to)133-143
Number of pages11
JournalInformatica (Slovenia)
Volume40
Issue number1
Publication statusPublished - 2016
Externally publishedYes

Keywords

  • Class-0 IoT devices
  • Internet of things (IoT)
  • IoT security
  • Object data encryption

ASJC Scopus subject areas

  • Software
  • Theoretical Computer Science
  • Computer Science Applications
  • Artificial Intelligence

Fingerprint

Dive into the research topics of 'A distributed security mechanism for Resource-Constrained IoT Devices'. Together they form a unique fingerprint.

Cite this