Black Friday Our software, PenTest Project: Slate Enterprise at €53 instead of €173 per user a month, and Flint free for 12 months. Until 30 November. See the offer →
PenTest Hub logo

Firmware · Debug interfaces · Secure boot

IoT Hardware & Embedded System Security

We open the box. In-depth reviews of smart devices, industrial IoT and embedded systems: firmware, circuit boards, debug interfaces, bootloaders and secure storage, to find the weaknesses that give an attacker root.

  • Firmware reverse engineering
  • UART, JTAG and SPI
  • OWASP IoT Top 10
Sample findings · Embedded device reviewSample
CRITICALRoot shell through the UART debug headerLeft enabled on production units
HIGHFirmware readable from the flash chipIncludes the private key used for cloud access
HIGHSecure boot not enforcedA modified bootloader runs without warning
MEDIUMSame default password on every devicePrinted in the public manual
From the circuit board to the cloud back endSample findings

In one sentence

What is an IoT hardware and embedded system review?

An IoT hardware and embedded system review is an in-depth assessment of a device's hardware and firmware, including reverse engineering, circuit board analysis and probing of interfaces such as UART, JTAG and SPI, to find root-level vulnerabilities and insecure-by-default configurations.

Whoever holds the device can open it. We test what they could extract, change or take over, and how that could affect the rest of your fleet and your cloud services.

Devices we review

  • Smart home and consumer devices
  • Industrial IoT and controllers
  • Medical and building systems
  • Gateways and embedded computers

Scope

What we test

Every layer of the device, from the chips to the cloud.

Hardware interfaces

UART, JTAG, SPI and other debug and programming interfaces left accessible.

  • UART
  • JTAG
  • SPI

Firmware analysis

Firmware extraction and reverse engineering for secrets, unsafe code and backdoors.

  • Extraction
  • Reverse engineering
  • Secrets

Bootloader and secure boot

Whether the device only runs trusted code, and how the boot chain can be attacked.

  • Bootloader
  • Secure boot
  • Chain of trust

Secure storage and keys

How credentials, keys and certificates are stored and protected on the device.

  • Keys
  • Certificates
  • Storage

Fault injection simulation

Simulated glitching attacks against security checks in hardware.

  • Glitching
  • Bypass
  • Hardware checks

Update mechanism

Over-the-air updates: signing, integrity checks and rollback protection.

  • OTA
  • Signing
  • Rollback

Methods

How we test a device

Physical, local and remote attacks.

Physical access

Hardware layer

Debug ports, chips and memory, to extract firmware or tamper with the device.

Firmware

Reverse engineering

Disassembly and analysis of firmware images for unsafe code, weak cryptography and backdoors.

Radio and network

Wireless and cloud

Bluetooth, Wi-Fi, Zigbee and cellular interfaces, and the cloud services the device talks to.

Engagement

How we work with you

  1. Scope online

    Describe what you need in Flint, our scoping platform. Answer only the questions that apply.

  2. Proposal, signed online

    Effort, price and the statement of work are built from your answers.

  3. Ready for day one

    Authorisation, test accounts and rules of engagement are agreed before testing starts.

  4. Senior-led testing

    Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.

  5. Report and retest

    Your report is ready in Slate, our client portal, within 48 hours of testing ending.

What you receive

Everything stays in one place, in your own client portal.

  • A report in Slate within 48 hours of testing ending
  • Every finding with evidence, a risk rating and a fix
  • An executive summary for leadership
  • Retests you can request finding by finding
  • Downloads as PDF or Excel
  • Evidence you can hand to your auditors

Standards

Standards we test against

Aligned with the standards your regulators and customers expect.

  • OWASP IoT Top 10
  • NIST IoT cybersecurity guidance
  • ISO/SAE 21434
  • UNECE R155 (WP.29)

FAQ

Frequently asked questions

Can't find yours? Ask a senior tester and we'll reply directly.

Do you need physical devices?
Yes. We agree the number and type of sample devices with you during scoping.
Will testing damage the devices?
Some hardware techniques can. We agree with you which devices may be opened or modified.
Do you test the cloud back end too?
Yes, if it is in scope. Many device weaknesses only matter because of what they unlock in the cloud.
Does this help with regulation?
It gives you independent evidence for the cybersecurity requirements your products must meet. It is evidence, not a certification.
When will we receive the report?
Within 48 hours of testing ending, in Slate, our client portal.

Contact

Tell us what you need to test

A senior tester reads every message and replies directly.