Provisioning IoT Devices: From Factory to Cloud

Provisioning is everything between a bare board on the production line and a device that is registered with its cloud service and bound to a customer account. It spans manufacturing, security and cloud engineering, so it often falls between teams and is designed late. Done well, it gives each device its own identity without exposing secrets on the factory floor. This article walks through the stages.

At a glance

Unique
Every device needs its own credential. A shared secret compromises the whole fleet at once.
X.509
The certificate format most IoT cloud platforms accept for device authentication.
On-chip
Generating the private key inside the device or a secure element means it never leaves.
Claim
The step that binds a registered device to a particular customer account.

The problem

The quickest way to get a prototype online is to compile one credential into the firmware. That shortcut survives into production more often than it should, and then one extracted credential lets an attacker impersonate every device that shares it.

The opposite mistake is a process that is secure but impractical: manual steps per unit, a laptop holding the signing key on the line, or factory network access the contract manufacturer cannot provide.

Treat provisioning as a manufacturing process with security requirements, not a security feature added after manufacturing.

Identity, registration and ownership

Identity is created in the factory: the device generates a key pair and its public key is signed by a certificate authority you control, so the cloud can verify any device carrying a valid certificate. Registration happens at first connection, when the cloud creates a record for the device. Major cloud platforms offer fleet provisioning services for this step.

Ownership comes later, when a customer claims the device through an app or a code on the label. Keeping these stages apart means devices can be built in bulk without knowing who will buy them.

What good looks like

Decide where keys are generated and stored: in the microcontroller, in a secure element, or injected by a programming station. Each choice changes what the factory must protect.

Design the line step: program firmware, create the identity, record serial number and certificate, and test the result before the unit is packed.

Define first connection and claiming, including how a device is reset and transferred to a new owner without leaving the old one with access.

From bare board to customer account

  1. Program: Bootloader and firmware
  2. Create identity: Key pair and signed certificate
  3. Record: Serial, certificate, test result
  4. First connect: Cloud registers the device
  5. Claim: Customer binds it to an account
Identity is created in the factory; ownership is assigned in the field.
Where the private key is generated
ApproachKey exposureFactory impact
Generated on the microcontrollerNever leaves the deviceNeeds a signing step per unit on the line
Secure element, pre-provisionedNever leaves the chipCertificates may arrive with the parts, depending on vendor
Injected by a programming stationExists outside the device brieflyStation must be secured and audited
Compiled into firmwareSame key in every imageSimple, but not acceptable for production
General trade-offs. Secure element provisioning services and options vary by vendor.

What it changes

Fleet Security

A compromised device exposes only its own credential, which can be revoked alone.

Factory Fit

The process runs at line speed with no secrets held on general-purpose PCs.

Traceability

Each serial number maps to a certificate, a firmware version and a test record.

Clean Ownership

Devices can be resold or returned without carrying old account access.

Where to go next

Plan certificate lifetimes against product life. A device that cannot renew its certificate stops connecting when it expires.

Agree the provisioning procedure with your contract manufacturer early. Programming stations, network access and record handling all need their agreement.

Problems this prevents

  • One credential shared across every device
  • Private keys handled in plain text on the line
  • Devices that keep old owners after resale
  • Certificates expiring before the product does

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.