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
ECC keys for devices with little computing power
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.
Certificates at the assembly line
- 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.
Long lifetimes for devices that can't renew
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.