Skip to main navigation Skip to search Skip to main content

Securing Cloud-Based Internet of Things: Challenges and Mitigations

  • Sungkyunkwan University
  • University of Melbourne

Research output: Contribution to journalReview articlepeer-review

Abstract

The Internet of Things (IoT) has seen remarkable advancements in recent years, leading to a paradigm shift in the digital landscape. However, these technological strides have introduced new challenges, particularly in cybersecurity. IoT devices, inherently connected to the internet, are susceptible to various forms of attacks. Moreover, IoT services often handle sensitive user data, which could be exploited by malicious actors or unauthorized service providers. As IoT ecosystems expand, the convergence of traditional and cloud-based systems presents unique security threats in the absence of uniform regulations. Cloud-based IoT systems, enabled by Platform-as-a-Service (PaaS) and Infrastructure-as-a-Service (IaaS) models, offer flexibility and scalability but also pose additional security risks. The intricate interaction between these systems and traditional IoT devices demands comprehensive strategies to protect data integrity and user privacy. This paper highlights the pressing security concerns associated with the widespread adoption of IoT devices and services. We propose viable solutions to bridge the existing security gaps while anticipating and preparing for future challenges. This paper provides a detailed survey of the key security challenges that IoT services are currently facing. We also suggest proactive strategies to mitigate these risks, thereby strengthening the overall security of IoT devices and services.

Original languageEnglish
Article number79
JournalSensors
Volume25
Issue number1
DOIs
StatePublished - Jan 2025

Keywords

  • IaaS
  • IoT privacy
  • IoT security
  • cloud
  • security

Fingerprint

Dive into the research topics of 'Securing Cloud-Based Internet of Things: Challenges and Mitigations'. Together they form a unique fingerprint.

Cite this