A connected device needs a plan for the day it is no longer new.

Devices stay in the world long after a project handover. Their identity, update process and offline behaviour shape how safe and useful they remain.

RU / FIELD NOTES14 — INSIGHTS IOT-SECURITY
01 / THINK IT THROUGH

Give every device its own identity

Avoid shared default credentials. Establish a way to provision each device, replace its credentials when necessary and revoke access if it is lost or retired.

02 / THINK IT THROUGH

Plan for trustworthy updates

Decide how a device learns that an update is genuine, how interrupted updates recover and how long updates will be provided. An update channel that nobody owns is not a security plan.

03 / THINK IT THROUGH

Protect data while it travels and rests

Choose the data the device truly needs to collect. Protect communication, restrict service access and set a retention period that matches the purpose. Consider physical access to the device as well as network access.

04 / THINK IT THROUGH

Define safe offline behaviour

Ask what happens when the network fails, the clock is wrong or a sensor produces an impossible reading. The device should fail in a way that is visible and appropriate to its environment, rather than silently pretending everything is fine.

Plan a connected product

Bring the rough version. We will help you find the useful next step.

Start a conversation