OnBoard™ IoT Security (OBIS) governs Cast certificate operations, provisioning workflows, and lifecycle operations through one operational trust chain — whether OEMs retain their own CA hierarchy or operate through OBIS-managed infrastructure.
Devices with Chromecast built-in typically require multiple credentials — Cast certificates, OEM identities, Matter DACs, and OTA credentials — each governed across separate operational workflows. OBIS governs them through one provisioning workflow and one operational trust chain.
The Google Cast program defines security requirements across key management, certificate operations, and provisioning workflows. OBIS governs these operational controls end-to-end.
Google operates the Cast root, while each device carries a unique device certificate. Between them sit the OEM CA and Model CA layers, which establish operational trust across the provisioning workflow. OBIS governs Model CA operations and device certificate issuance, while OEMs retain flexibility over the OEM CA trust model.
Cast certificates expire, firmware requires continuous updates, and lifecycle security obligations now extend across the full supported product lifespan. OBIS governs certificates, keys, SBOMs, provisioning records, and operational evidence through the same operational trust chain.
Discuss your certificate provisioning workflow, factory architecture, device authentication model, and operational requirements with the OBIS engineering team.
