IoT Device Pentest Interactive Guide
Explore the five layers of the IoT attack surface, what is tested at each, the real tools used and how it all maps to the OWASP IoT Top 10.
Pick a device to highlight the layers that matter most, then click any layer to explore what is tested.
1. Hardware
What is tested: Physical access: UART/JTAG/SWD debug interfaces, chip-off memory dumps, open test pads, serial consoles, glitch / voltage fault injection and exposed ports on the PCB are tested.
- Open UART console giving a root shell or bootloader access
- Unlocked JTAG/SWD allowing full memory read/write
- Firmware dumped from unsoldered SPI/I2C flash
- Secure boot disabled or no bootloader password
- Bus Pirate
- JTAGulator
- Saleae Logic
- OpenOCD
- flashrom
- Chip-off / SOIC clip
OWASP IoT Top 10: I8 Lack of Physical Hardening, I3 Insecure Ecosystem Interfaces
The IoT attack surface
A connected device is never just one target. Its attack surface spans hardware debug ports, the firmware running on it, the network and radio protocols it speaks, the mobile app that controls it and the cloud backend behind it. A serious IoT pentest works across all five layers, because a single weak link, like an open UART console, can collapse the rest.
Related reading: EMBA firmware security analysis for IoT and embedded devices.
OWASP IoT Top 10
The OWASP IoT Top 10 frames the most common, highest-impact mistakes. The recurring themes are weak, guessable or hardcoded passwords (I1), insecure network services (I2), insecure ecosystem interfaces (I3), missing secure update mechanisms (I4), insecure data transfer and storage (I7) and a lack of physical hardening (I8). The interactive guide above maps each layer back to these items so you can prioritise remediation.
OT and embedded device security
Industrial OT/SCADA and embedded systems raise the stakes: long lifecycles, unpatched firmware and physical accessibility make hardware and firmware testing essential. A scoped pentest plus secure firmware analysis tells you exactly where your devices break and how to fix it.
See also: The penetration test process: pricing and when you need one.