Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Device identity gives each unit a unique, hardware-protected credential; provisioning is the process of creating that credential and enrolling the device with the services it is allowed to use.

What Is Device Identity and Provisioning?
Device identity is the answer to a deceptively simple question: when something connects to your platform and claims to be sensor 4,812, how do you know it is? Provisioning is the process that creates the proof — generating or injecting a credential, binding it to a specific unit, and registering that unit with the services it is entitled to use. Get it right and a stolen device compromises one device. Get it wrong, usually by sharing a key across a product line, and recovering a single unit compromises the fleet.
Three properties matter more than the format.
In practice this means an X.509 certificate with the key in hardware. IEEE 802.1AR formalises the pattern: an IDevID is the manufacturer-installed birth certificate, created at production and valid for the life of the device, while an LDevID is the locally significant certificate an operator issues once the device joins their own PKI. The IDevID proves origin; the LDevID carries the operator’s authorisation and can be revoked without arguing with the vendor.
There are two production models, and the difference is consequential.
Key injection generates the key elsewhere and writes it into the device during manufacture. It is simpler and works with parts that cannot generate keys, but the private key exists outside the chip at some point, so the production line becomes part of your trust boundary. Contract manufacturers must be audited accordingly.
On-device generation has the chip create its own key pair and emit only a certificate signing request. The private key never exists anywhere else. This is the stronger pattern and most modern secure elements support it, often with a pre-provisioned manufacturer certificate already present from the silicon vendor.
Nobody registers a hundred thousand devices by hand, so enrolment has to be automatic without being open to anyone who asks. The established approaches:
The Matter standard for smart home products applies the same thinking in consumer form: each device carries a Device Attestation Certificate chaining to a product attestation authority, and a commissioner validates that chain before admitting the device to a fabric.
Certificates expire, keys need rotation, and devices get sold, returned, or stolen. Plan for renewal before the first fleet reaches its expiry cliff — a batch of certificates issued with a ten-year lifetime on the same day is a future outage. Maintain revocation that the platform actually checks, support decommissioning that wipes credentials and removes the device from the registry, and keep a factory reset path that does not reinstate a shared secret. Pair the identity with signed firmware updates, because an attacker who can replace the firmware can simply ask the secure element to sign whatever they like.
At Privia Security, our IoT Penetration Test Services include provisioning review — the enrolment API is often where a well-designed hardware identity quietly stops mattering.
It is a poor trade. A shared key means any compromised or stolen unit yields a credential valid for every other unit, and rotation requires touching the whole fleet at once. Private networks are also less isolated than assumed, with contractor laptops, remote maintenance links, and bridged segments. Per-device credentials cost little once provisioning exists and remove an entire category of incident.
An IDevID is installed by the manufacturer during production and identifies the physical device for its whole life; it proves authenticity of origin. An LDevID is issued by the operator after the device joins their environment and carries local meaning such as site, role, and permissions. You verify the IDevID once at onboarding, then rely on the LDevID day to day because you can revoke it.
Build renewal into the device from the start: have it request a new certificate well before expiry over EST or the platform’s own API, keep the old credential valid until the new one is confirmed working, and stagger renewal across the fleet. Test the failure path, because a device that bricks its own connectivity during rotation needs a site visit to recover.
Indirectly. A hardware-held key stops an attacker extracting credentials from flash, but it does not stop modified firmware from using those keys on the device itself. Identity has to be combined with secure boot so that only signed code runs, and with attestation so the platform can detect a device whose measurements no longer match an approved build.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.