Connected-device vendor

IoT security audit: from the cloud backend to the device in the field

Industry
IoT, connected devices (thousands of devices in the field)
Frybad's role
Security audit across backend, transport and device; support for the fix; introduction of continuous vulnerability scanning
Stack
MQTT, firmware update process, container images and package registries with automated scanning

Starting point

The vendor’s devices connect over MQTT to a cloud backend and receive commands and updates through it. Thousands of them sit at end customers, so a flaw in the protocol or in authentication affects not one server but every device in the field. The vendor wanted the whole path examined: backend, transport, device.

What we did

  • Backend and transport. We examined the cloud backend and the MQTT integration: device authentication, topic permissions, what one device can learn about or trigger on other devices through the broker.
  • Device. The physical devices were included: firmware, local interfaces and the update path.
  • Finding. A critical vulnerability in the MQTT channel would have allowed devices to be taken over.
  • Fix. We supported the client through the fix. The vehicle was a secure firmware update process, so that the correction reaches every device in the field without the update channel becoming the next vulnerability.
  • Supply chain. With us, the client’s team introduced continuous vulnerability scanning for its container images and package registries.

What a secure firmware update process does: the device verifies the origin and integrity of an update cryptographically before applying it, and can roll back to the previous version on failure. Without that check, the update channel is the most convenient way to take over devices in the field.

What this means for your project

If a customer demands a security test or your device is about to launch, start with Penetration testing & IoT security. If the secure update path is still missing, we build it with you: Software development & architecture.

Result

Example from a client project.

Critical MQTT vulnerability found; we supported the client in fixing it through a secure firmware update process.

Continuous vulnerability scanning for containers and package registries in operation at the client.

Not included: exact numbers on devices, findings or duration.

What we would do differently today

Examine the update path before the first device ships. A secure firmware update process is what makes every later vulnerability fixable. It belongs before the rollout, not in the remediation.

Topic permissions per device at the broker. A device should only read and write its own topics. That limits what a single compromised unit can do.

Similar situation?

Tell us which devices are in the field and how they get updates today. We will say where we would look first.