Skip to main content
USE CASE · IOT

An identity for every device on your production line.

A sensor has no user, no MDM and little computing power, but it still has to prove what it is to your backend. SCEPman can run an ECC CA for devices like that, issues certificates over an API that your production line calls, and lets you choose how long a certificate lives when the device can't renew it in the field.

  • ECC CA with P-256, P-256K, P-384 and P-521
  • REST API with Entra ID
  • Validity you choose
Example data.
ECC

ECC keys for devices with little computing power

Elliptic-curve keys give the same strength as RSA with far smaller keys and cheaper signatures, which matters on a battery-powered chip. SCEPman can create its CA on an elliptic curve, P-256, P-256K, P-384 and P-521, with the key in your Azure Key Vault like any SCEPman CA.

An ECC CA is for scenarios without SCEP. Devices that enroll over SCEP need an RSA CA, so an ECC CA for your IoT fleet runs as a SCEPman instance of its own.

PROVISIONING

Certificates at the assembly line

The device generates its key, the line station sends the CSR to SCEPman's REST API and writes the certificate back to the device before it is boxed. The station authenticates with an Entra ID app that has the CSR role, so a device on its own can't ask for a certificate.
  • Fix the extended key usages the API hands out, so a line station can't request a server certificate.
  • Every issued certificate lands in the certificate store of your SCEPman, searchable in Certificate Master and revocable there or through the Management API.
LIFETIME

Long lifetimes for devices that can't renew

A device in a field cabinet may never get a renewal window. SCEPman caps every certificate twice: once with a global maximum and once per endpoint. Raise the global maximum for your devices and the Intune endpoint still holds your laptops to 365 days. Long lifetimes put more weight on revocation: plan how you will revoke a certificate you can't replace.

Questions about IoT certificates

01Can a device renew its own certificate?

Yes, over EST with the certificate it has, if it speaks EST and the endpoint allows renewals.

02Do IoT devices need Entra ID?

No. The line station or backend that requests the certificates authenticates with Entra ID; the device itself only holds its key and certificate.

03Can we use a separate CA for IoT?

Yes. Run a second SCEPman instance with its own root, so the IoT trust chain stays apart from the laptops.

Give your next production batch an identity.

Try SCEPman with a test CA and a line station script before the first batch.