Abstract

With the proliferation of smart devices capable of communicating over a network using different protocols, each year more and more successful attacks are recorded against these, underlining the necessity of developing and implementing mechanisms to protect against such attacks. This paper will review some existing solutions used to secure a communication channel, such as Transport Layer Security or symmetric encryption, as well as provide a novel approach to achieving confidentiality and integrity of messages. The method, called Value-to-Keyed-Hash Message Authentication Code (Value-to-HMAC) mapping, uses signatures to send messages, instead of encryption, by implementing a Keyed-Hash Message Authentication Code generation algorithm. Although robust solutions exist that can be used to secure the communication between devices, this paper considers that not every Internet of Things (IoT) device or network design is able to afford the overhead and drop in performance, or even support such protocols. Therefore, the Value-to-HMAC method was designed to maximize performance while ensuring the messages are only readable by the intended node. The experimental procedure demonstrates how the method will achieve better performance than a symmetric-key encryption algorithm, while ensuring the confidentiality and integrity of information through the use of one mechanism.

Highlights

  • The proliferation of embedded devices that possess their own memory, processing power, and have the ability to communicate with each other, has given birth to new attack vectors that have proven to be difficult to secure against

  • Robust solutions exist that can be used to secure the communication between devices, this paper considers that not every Internet of Things (IoT) device or network design is able to afford the overhead and drop in performance, or even support such protocols

  • According to [1], interconnected devices such as sensors, appliances, and cameras represent some of the components of this network, which was named the Internet of Things (IoT) by Kevin Ashton at a conference in 1999

Read more

Summary

Introduction

The proliferation of embedded devices that possess their own memory, processing power, and have the ability to communicate with each other, has given birth to new attack vectors that have proven to be difficult to secure against. The IoT became possible by the sudden increase in smart devices that manufacturers developed and released on the market This was accomplished without having properly considered all aspects of security and device limitations. Kevin stated that most of the information available was recorded using different conventional methods (e.g., typing) This aspect, coupled with the fact that humans in the modern era have a limited amount of time and ability to properly capture different aspects of life, gave birth to the idea that a machine which can record and even process data automatically could be built and programmed. Sci. 2019, 9, 848 effectively a flood of TCP and UDP packets that were destined for port 53 This denial of service attack and numerous others have made it clear that IoT requires robust protocols to ensure the security of the devices themselves, and to protect the outside world from the potential danger they pose

Security of the Internet of Things
Security Overview of MQTT
Research Setting
IoT Network Design for Experiment
Value-to-HMAC Mapping
Computational Complexity of Blake2
Performance Assessment
Algorithm Comparison
Conclusions

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.