
Research Article
Investigating the IoT Security and Privacy Challenges: Summary and Recommendations
@ARTICLE{10.4108/eetcs.v7i22.2652, author={Premlata Chauhan and Shafeeq Ahmad and Pervez Rauf Khan and Naseem Ahmad Khan}, title={Investigating the IoT Security and Privacy Challenges: Summary and Recommendations}, journal={EAI Endorsed Transactions on Cloud Systems}, volume={7}, number={22}, publisher={EAI}, journal_a={CS}, year={2022}, month={8}, keywords={Internet of Things, IoT Systems, security, privacy, cyber-attack}, doi={10.4108/eetcs.v7i22.2652} }
- Premlata Chauhan
Shafeeq Ahmad
Pervez Rauf Khan
Naseem Ahmad Khan
Year: 2022
Investigating the IoT Security and Privacy Challenges: Summary and Recommendations
CS
EAI
DOI: 10.4108/eetcs.v7i22.2652
Abstract
With the development of innovative technology transformation like cloud and Internet of Things (IoT), more technology companies are pursuing research in employing such innovations. Smart homes and cities are just two examples of the many systems and technologies that the IoT can endorse. IoT - based smart objects communicate with other parts, such as proxies, portable devices, as well as data collectors. Although these components help to tackle a number of societal issues and offer users new, cutting-edge services, their confined processing power makes them susceptible to well-known privacy and security attacks. This in turn highlights the demand for a strong technical as well as legislative foundation and asserts the significance of validity and reliability in IoT. This paper provides an insight of the IoT, security, as well as privacy challenges, and also discusses the recommendations for IoT solutions. Further we also highlighting some unresolved problems that require further study.
Copyright © 2022 Premlata Chauhan et al., licensed to EAI. This is an open access article distributed under the terms of the CC BYNC-SA 4.0, which permits copying, redistributing, remixing, transformation, and building upon the material in any medium so long as the original work is properly cited.