Book Image

IoT Penetration Testing Cookbook

By : Aaron Guzman, Aditya Gupta
Book Image

IoT Penetration Testing Cookbook

By: Aaron Guzman, Aditya Gupta

Overview of this book

IoT is an upcoming trend in the IT industry today; there are a lot of IoT devices on the market, but there is a minimal understanding of how to safeguard them. If you are a security enthusiast or pentester, this book will help you understand how to exploit and secure IoT devices. This book follows a recipe-based approach, giving you practical experience in securing upcoming smart devices. It starts with practical recipes on how to analyze IoT device architectures and identify vulnerabilities. Then, it focuses on enhancing your pentesting skill set, teaching you how to exploit a vulnerable IoT device, along with identifying vulnerabilities in IoT device firmware. Next, this book teaches you how to secure embedded devices and exploit smart devices with hardware techniques. Moving forward, this book reveals advanced hardware pentesting techniques, along with software-defined, radio-based IoT pentesting with Zigbee and Z-Wave. Finally, this book also covers how to use new and unique pentesting techniques for different IoT devices, along with smart devices connected to the cloud. By the end of this book, you will have a fair understanding of how to use different pentesting techniques to exploit and secure various IoT devices.
Table of Contents (19 chapters)
Title Page
About the Authors
About the Reviewers
Customer Feedback

Securing third-party code and components

Following the setup of the toolchain, it is important to ensure that the software packages and third-party upstream libraries remain updated to protect against publicly known vulnerabilities once the IoT device is in production. Black box third-party software such as RomPager, NetUSB, and embedded build tools such as Buildroot, should be checked against vulnerability databases as well as their changelogs to decide when and if an update is needed. using upstream BSP drivers is not an easy task; changes to libraries and upstream BSP drivers should be tested by development teams prior to release builds, as updates can cause unforeseen dependency issues.

Embedded projects and applications should maintain a Bill of Materials (BOM) of the third-party libraries and open source software included in its firmware images. This is sometimes a requirement for certain regulated regions of the world and also for GPL but maintaining a BOM also improves management...