Book Image

IoT Penetration Testing Cookbook

Book Image

IoT Penetration Testing Cookbook

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 (12 chapters)

Hardware hacking methodology


The following are the steps involved in a Hardware hacking methodology methodology:

  • Information gathering and recon
  • External and internal analysis of the device
  • Identifying communication interfaces
  • Acquiring data using hardware communication techniques
  • Software exploitation using hardware exploitation methods
  • Backdooring (optional)

Let's go into each of them, one by one, and understand each of these steps at a deeper level.

Information gathering and recon

The first step in an embedded device hacking methodology is to gather as much information as possible about the target that we are working with. Now this may sound simple, but in the cases of embedded devices, this might be a bit more complicated than we might think. The information about a target device is usually limited-at least from a very high-level view-given the fact that in order to gain a relevant amount of information about the device, we will need access to the physical device itself.

But even before doing...