Topic starter
25/06/2026 2:50 pm
TL;DR: Matter device launches are being framed as a certification and certificate-lifecycle problem, with claims of up to 65% faster certification, 50% less DevSecOps overhead, and zero exposed keys when issuance, rotation, and revocation are handled in a managed workflow, according to DigiCert. The governance lesson is that device trust breaks fastest where teams still treat PKI as an engineering side task rather than an identity programme.
Editorial analysis by NHI Mgmt Group, based on content published by DigiCert: “DigiCert + Beechwoods Embedded Experts”.
Key questions
Q: What breaks when Matter certificates are handled as one-off engineering artefacts?
A: Certification becomes brittle because each device identity can drift away from the records that prove it is trusted, compliant, and revocable.
Q: Why do per-device certificates matter for IoT OEM compliance?
A: Per-device certificates give each unit a distinct trust anchor, which is essential when devices move through manufacturing, testing, shipment, and field operation.
Q: Why do IoT programmes need certificate lifecycle management?
A: Because device identity is only useful if it can be discovered, rotated, renewed, and revoked on time.
Practitioner guidance
- Standardise per-device certificate provisioning Define a repeatable provisioning flow that generates unique certificates for each device and binds them to approved manufacturing and test paths.
- Make rotation and revocation mandatory lifecycle steps Require every Matter device identity to have explicit rotation and revocation triggers tied to firmware updates, compromise response, and end-of-life handling.
- Separate certification evidence from engineering workarounds Keep certificate status, test readiness, and compliance evidence in governed records rather than in ad hoc spreadsheets or build notes.
Bottom line: Matter certification exposes a governance gap when device identity is treated as a one-time engineering task rather than a managed lifecycle.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 4:01 pm
Matter certification is becoming a certificate-lifecycle governance problem, not just a device-compliance task. OEMs can pass technical tests and still fail operational trust if issuance, rotation, and revocation are not controlled as one lifecycle. That is why device identity now sits inside broader NHI governance rather than isolated embedded engineering. The practitioner takeaway is to treat certification readiness and certificate governance as the same programme.
A question worth separating out:
Q: How should teams govern certificate rotation for Matter devices?
A: Teams should tie rotation to clear lifecycle events such as manufacturing release, firmware updates, compromise response, and retirement. Rotation should be policy-driven and evidenced in inventory records so that device trust does not depend on tribal knowledge or individual engineers.
👉 Read our full editorial: Matter certification and certificate lifecycle for IoT OEMs