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

Exposed interfaces

One of the most important things for securing hardware in IoT devices is to disable and remove the UART and JTAG interfaces, as well as any other diagnostic functionality in the hardware when the device is launched to the market.

The other important consideration here is that, even if there are no exposed interfaces visible, an attacker can directly hook to the legs of the chip to get access to the UART, JTAG, and so on. This is done by reading the datasheet of the chipset, figuring out which pins are for what functionalities, and then making the necessary connections. One of the steps that could be taken here to add a bit of complexity is to have the interfaces deep between different layers via vias and not exposed on one of the visible layers. However, this should be done only if the exposed interfaces are required for the device developer at a later point in time. In all other practical cases, these interfaces should be removed. Another security protection worth noting...