IICTPIICTP

Blog / Guides

IoT & edge26 October 20265 min read

OTA updates done right: safe firmware delivery at scale

Over-the-air (OTA) updates let you fix and improve devices after they ship. They are also the most dangerous thing you do to a fleet: a bad update can brick thousands of devices at once.

In this post
  1. Requirements
  2. Rolling out
  3. Plan for the field
  4. Sources and further reading

Requirements

  • Signed images, verified by the device before use.
  • Rollback: keep the previous version and return to it if the new one fails.
  • Atomic updates, so a power cut mid-update cannot leave a half-written device.
  • Version checks, to stop downgrade attacks.

Rolling out

  1. Test on a bench and on a small internal group.
  2. Release to a small share of the fleet and watch health.
  3. Widen in stages; pause automatically on failures.
  4. Keep the ability to stop an update quickly.

Plan for the field

Devices have weak or intermittent links, low battery and limited storage. Make downloads resumable, schedule them for safe moments and report status back.

Sources and further reading

  1. IETF RFC 9019. A Firmware Update Architecture for Internet of Things. rfc-editor.org/rfc/rfc9019.

IICTP is a new independent credential and is not ISO/IEC 17024 accredited.

Keep reading

← All posts

Where do you stand?

Find the credential that fits the work you do.