A trusted identity for every device, issued on the factory line
Your PKI, without running a CA
LAAVAT runs your device PKI: root and issuing CAs with their keys in the HSM, and an IEEE 802.1AR IDevID certificate for every unit you build.

A fleet you cannot tell apart is a fleet you cannot trust
Shared secrets
Clones and counterfeits
Running a CA is a job
One default credential across a fleet means one extraction compromises every device.
Without an identity for each unit, a cloned device looks the same to your cloud as a genuine one.
Root ceremonies, HSMs, revocation lists and audit evidence are a practice of their own, and most device teams do not staff it.
What LAAVAT runs for you
CA keys stay in the HSM
Root and issuing CA keys are generated in FIPS-validated HSMs and never leave them in the clear.
Every certificate on record
Each certificate is logged under the name of the station that requested it, ready for an audit and your technical file.
Use the root you already have
Create a Sub CA in LAAVAT, have its request signed by your external root, and upload the issued chain.
Where identity fits in the CRA
Annex I expects protection against unauthorised access. A certificate for each device lets devices and services authenticate each other.
Make the key on the device, sign it in the HSM
Build your hierarchy
Create a Root CA and issuing CAs in LAAVAT, or chain them under the root CA you already have.
Issue on the factory line
Each device creates its own key on the line, and the private key never leaves it. The factory test PC requests the IDevID under its own identity, and every issue is logged.
Operate the fleet
Enrol operational certificates over EST, and revoke through CRLs that LAAVAT generates and signs for each CA.
Start from a working example
01
Trusted device identities
Set up the hierarchy and issue IDevID certificates on the factory line.
04
EST enrolment
Configure EST so devices can enrol for operational certificates.
02
Device certificate issuance
A worked example of issuing a certificate for a device.
05
Factory reference client
Install the pip reference client on the test PC. It signs in under the station’s own identity, so there are no tokens to handle.
03
Advanced PKI hierarchy
Build a multi-level CA hierarchy for your products.
06
Revocation and CRLs
LAAVAT generates and signs your certificate revocation lists. You publish them at your own distribution point.
