AI & Automation

Device Provisioning for IoT Fleets: Giving Every Device an Identity Before It Leaves the Workshop

November 11, 2026 · 7 min read · Etzal Group Team

A facilities company installs twelve temperature sensors in a client's building. Each is configured on a laptop: the same Wi-Fi password, the same username and password for the data platform, typed in by an engineer. It works. A year later the company has 1,400 sensors across forty sites, all using that same platform password. One is stolen from a plant room. To be safe, the password should be changed, which means visiting 1,399 devices. Nobody does. Device provisioning done properly at twelve devices would have made the theft a five-minute task.

What provisioning is

Provisioning is everything that turns a blank device into a trusted member of your fleet.

  • Identity. A unique identifier, and a credential that proves it.
  • Connection details. Where to send data.
  • Configuration. What to measure, how often, with what thresholds.
  • Registration. The platform knows this device exists, what it is and where it belongs.
  • Ownership. Which customer, site and measuring point it serves.

The rule: one device, one identity

Every device has its own credential, never shared with another.

  • A unique key pair or certificate is the strongest common form. The private key is generated on or injected into the device and never leaves it. The platform holds only the public part.
  • A unique token or key per device is a weaker and simpler alternative, acceptable for lower-risk uses if stored carefully.
  • A shared password across the fleet is not acceptable beyond a bench test.

What unique identity gives you:

  • Revoke one device without touching the others.
  • Trace every reading to its source.
  • Limit each device to its own data: it can publish its readings and nothing else.
  • Detect clones: the same identity connecting from two places.

Where the secret lives

A credential is only as safe as its storage.

  • Secure element or hardware-protected storage. A chip designed so the private key cannot be read out, even with the device opened. The best option, and now inexpensive.
  • Encrypted flash with protected boot. Reasonable where a secure element is not available.
  • Plain text in firmware or a config file. Readable by anyone who opens the device or obtains a firmware image.

Ask a hardware supplier which of these the device uses. The answer says a great deal about the rest of their security.

Three ways to provision at scale

1. Factory provisioning

The manufacturer creates each device's identity on the production line and supplies you a list of device identifiers with their public keys or certificates. You load the list into your platform.

  • Good for: large volumes, the strongest security, zero secrets handled in the field.
  • Needs: a supplier who offers it, and trust in their process.

2. Provisioning at your workshop

Devices arrive blank. At your bench, a station generates or loads each identity, registers it in the platform, labels the device and tests it.

  • Good for: medium volumes, full control, mixed hardware.
  • Needs: a secured provisioning station, a written procedure, and trained staff. The station itself becomes a sensitive asset.

3. Claiming in the field

The device ships with a factory identity and a printed code, often a QR code. The installer scans it with an app, which binds the device to the customer, site and measuring point. The device then fetches its configuration by itself.

  • Good for: installation by technicians or customers with no technical setup.
  • Needs: a claim process that cannot be abused. A code alone should not let a stranger take over a device. Combine it with the installer's authenticated account, and allow claiming only once.

Many fleets combine them: identity at the factory or workshop, assignment to a site in the field.

Zero-touch as the aim. The installer mounts the device, powers it and scans a code. Nothing is typed. Every credential that a person must type is a credential that will be reused, photographed or written on the enclosure.

The asset register

Provisioning creates records, and they must be kept.

For every device:

  • Identifier and serial number.
  • Hardware model and revision.
  • Firmware version.
  • Credential fingerprint and its expiry.
  • Status: in stock, installed, suspended, retired.
  • Customer, site and measuring point.
  • Installation date and installer.
  • Last contact.
  • History of every change.

Without this, you cannot answer simple questions: how many devices are in the field, which are on old firmware, which belonged to the customer who just cancelled.

Separate the device from what it measures

A common design error ties data to the device's serial number. When the device fails and is replaced, the history breaks.

Model two things:

  • The measuring point: "Cold room 2 temperature, Warehouse B". Permanent. Charts, alarms and reports belong here.
  • The device: the physical unit currently serving that point. Replaceable.

A device is bound to a point for a period. The register keeps the sequence: device A from January to August, device B from August onward.

Lifecycle procedures

Write each as a short procedure before the fleet grows.

Installation.

  1. Scan the device and select the measuring point.
  2. The platform binds them and sends configuration.
  3. The installer confirms a live reading on the app before leaving the site.

Replacement.

  1. Bind the new device to the same measuring point.
  2. Revoke the old device's credential.
  3. Mark the old device as failed or returned.
  4. History continues on the point.

Moving a device.

  1. Unbind from the old point, with a timestamp.
  2. Bind to the new point.
  3. Readings after the move go to the new point only.

Lost or stolen.

  1. Revoke the credential immediately.
  2. Mark the device as lost.
  3. Check for any connection attempts afterwards.

Customer leaves, or a device is retired.

  1. Unbind and revoke.
  2. Wipe the device: credentials, configuration, stored data.
  3. Only then reuse or dispose of it. A device moved to another customer with the first customer's settings and stored readings is a data leak.

Credential renewal. Certificates expire. Plan automatic renewal well before expiry, and monitor for devices approaching the date. An entire fleet falling silent on the same day because its certificates expired together is a well-known failure.

Limit what each device can do

Identity is half of it. The other half is permission.

  • A device may publish only to its own topics or endpoints.
  • A device may read only its own configuration.
  • A device cannot list other devices or read their data.
  • Management functions use different credentials from data functions.

Then a compromised device exposes one device's worth of access.

Multi-customer fleets

When one platform serves several customers:

  • Every device belongs to exactly one customer at a time.
  • Data is separated by customer in storage and in every query.
  • Installers see only the customers they are assigned to.
  • Transfer between customers goes through the retire-and-wipe procedure.

Questions to ask a supplier or platform vendor

  1. Does each device have a unique identity, and what kind?
  2. Where is the private key stored?
  3. How is identity created: factory, workshop or field?
  4. Can we revoke a single device, and how fast does it take effect?
  5. How are credentials renewed?
  6. What does an installer have to type?
  7. Can a device be reassigned, and is it wiped first?
  8. Is there a register with full history, and can we export it?
  9. What can a single compromised device access?
  10. What happens if the provisioning service is unavailable during an installation?

Common mistakes

  • One password for the whole fleet.
  • Credentials typed by hand in the field.
  • Secrets in plain text in firmware.
  • No register, or a spreadsheet nobody updates.
  • Data tied to serial numbers.
  • No procedure for lost devices.
  • Devices reused without wiping.
  • Certificates that all expire on the same date with no renewal.
  • Claim codes that work more than once.
  • Every device able to read every other device's data.

We design provisioning, device identity and lifecycle procedures into the monitoring systems we build, as part of IoT and Control Systems. If your fleet has grown past the point where anyone can list its devices with confidence, contact us.

Summary

Give every device its own credential, stored where it cannot be read out, and never share one across a fleet. Create identities at the factory or at a secured workshop station, assign devices to sites by scanning in the field, and aim for installation with nothing typed. Keep a register with full history, model measuring points separately from devices, limit each device to its own data, and write procedures for replacement, loss, reassignment, retirement and credential renewal.

Frequently asked questions

What is device provisioning in IoT?

It is the process of giving a device its identity and settings so it can connect securely to your system: a unique identifier, credentials such as a certificate or key, the server address, and its initial configuration. Done well, a device can be installed by a technician with no secrets typed in by hand.

Why should each IoT device have its own credentials?

Because shared credentials mean that one stolen or opened device exposes the whole fleet, and you cannot disable one device without changing the password on all of them. With a unique credential per device, a lost or compromised unit is revoked individually and every message can be traced to the device that sent it.

How do you replace a failed IoT sensor without losing its data history?

Separate the physical device from the logical point it measures. The history belongs to the measuring point, such as "Tank 3 level". When a device fails, the new device is bound to the same point with its own new identity, and the old device's credential is revoked. The charts continue unbroken, and the audit trail shows the swap.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

WhatsApp AI Chatbot

We build, train, and run a WhatsApp AI agent that answers customers 24/7, qualifies leads, and follows up.