Device Onboarding and Provisioning

What onboarding means

When you buy a connected device and set it up, you are performing onboarding. For one device it may be a few taps in a phone app. For a business installing thousands of sensors, it has to be systematic, fast and secure. Provisioning is the technical core of that process: giving the device what it needs to work as a trusted member of a system.

At a minimum, a newly connected device needs three things:

1. An identity: a unique name or identifier that distinguishes it from every other device.
2. Credentials: a secret or certificate that proves the device is who it claims to be.
3. Settings: configuration such as where to send data, how often, and which features to use.

Without an identity, the system cannot tell devices apart. Without credentials, anyone could pretend to be a device. Without settings, the device may connect but not do anything useful.

Identity and credentials

Identities are often based on a serial number or a hardware address, but a serial number is a label, not proof. The credential is what proves the claim. Common forms are:

• A shared secret or key: simple, but dangerous if the same one is used on many devices, since extracting it from one device exposes all of them.
• A unique key per device: better, because a compromise stays contained and a single device can be revoked.
• A digital certificate: a signed document tying a device’s public key to its identity. Certificates allow devices and servers to verify each other without sharing a secret, and they can expire and be replaced.

Unique per-device credentials are widely regarded as good practice. The opposite, the reuse of factory-set shared passwords, is a long-standing cause of trouble and is explained in the article on default passwords.

Some devices include secure hardware that can store keys in a way that makes them difficult to copy out. When available, this strengthens the whole scheme, though its presence and quality vary between devices.

Where credentials come from

There are several broad approaches, and the choice depends on volume, cost and risk.

Factory provisioning. The manufacturer loads a unique identity and credentials before the device ships. This produces a strong starting point, since the device arrives ready to authenticate. It requires a controlled factory process and a way to hand the matching records to the buyer.

Installer or batch provisioning. A technician, or a tool connected to the device, loads credentials shortly before or during installation. This gives the owner more control, but it takes time and depends on careful procedures.

Claiming or self-service enrollment. The user scans a code or enters a short number printed on the device or box. This proves they physically have it, and the system links the device to their account. This is common for consumer products.

Zero-touch or automatic provisioning. The device ships with a minimal built-in identity that it uses to contact a known service on first power-up. The service checks that the device is expected and then supplies its real credentials and settings. For large rollouts, this reduces manual work, but it depends on the initial identity being trustworthy and on the service knowing in advance which devices to accept.

Steps in a typical first connection

Although details differ, a typical sequence looks like this:

1. The device powers on and finds a network. For Wi-Fi devices, that may mean the user supplies network details through a temporary setup mode or a phone app. For devices using cellular IoT, a subscriber card may already carry the connection details.
2. The device contacts a provisioning service or the main system and presents its starting identity.
3. The system checks the identity against its records.
4. Both sides authenticate one another. The device should also verify that it is talking to the right server, not an impostor.
5. The device receives its long-term credentials and its configuration.
6. The system registers the device in its inventory, assigns it to a group, and may trigger a check that its software is current.
7. The device starts normal operation.

Low-power devices that use radio links such as Bluetooth Low Energy often take part in a short local pairing step first, then connect onward through a nearby hub or gateway.

Common mistakes

• Shared credentials across a whole product line. One leak affects everything.
• Leaving setup mode open. A device that stays in an easy pairing state for long invites unwanted connections.
• Sending secrets without protection. Credentials should travel over encrypted channels.
• No way to revoke or replace credentials. Devices need a plan for renewal, for ownership changes and for decommissioning.
• Poor record keeping. If the inventory does not match what is installed, unknown devices can linger on a network unnoticed.
• Forgetting the human side. Setup that is too complicated leads people to skip steps or choose weak options.

Reprovisioning and ownership changes

Provisioning is not always a one-time event. A device may need new credentials when old ones expire, when it is sold or reassigned, or after a suspected compromise. A factory reset should remove the previous owner’s credentials and data and return the device to an unprovisioned state. The wider lifecycle, including removal, is part of the overall picture in managing fleets of connected devices.

What to remember

Good provisioning gives each device a unique identity, strong and individual credentials, and correct settings, with as little manual effort as the risk allows. Decisions made at this stage are hard to undo later, so it pays to design onboarding before the first device ships.