Chromecast built-in is a security commitment,
not just a certificate.

OnBoard™ IoT Security (OBIS) is built to that bar — key storage, CA operation, factory provisioning, end to end. Host both CA layers on OBIS, or keep your OEM CA on your existing PKI.

Built for the Cast security bar.

The Google Cast program carries security requirements across three operational areas. OBIS operates to those requirements end-to-end.

Key Management

Keys never leave the hardware boundary.

OBIS performs every key operation in HSM —with no extraction path, for OEMs or for Snowball operators.
CA Operation

Every signing is authorized and recorded.

OBIS records every signing event with operator, timestamp, and approval chain —exportable as a complete operational record.
Factory Provisioning

Injection runs under authorization, not on trust.

EdgeHSM enforces all three: offline-capable, per-line authorization, encrypted payloads only on the programming station.

A four-tier certificate hierarchy.

Google operates the Cast root, and each device carries a unique device certificate at the bottom. Between them sit two intermediate layers — OEM CA and Model CA. The Model CA and device certificate issuance always run on OBIS; the OEM CA is the variable.

Cast certificate, plus everything else the device needs.

Devices with Chromecast built-in typically require multiple credentials — Cast, OEM cloud identity, Matter DAC, and OTA/local encryption keys — each provisioned through separate services and workflows. OBIS consolidates them into a single Production Version, provisioned in one production-line step.

Ship Chromecast built-in. Skip the audit project.

A 30-minute walkthrough covers your hosting model, your factory setup, and how OBIS maps to the program's security requirements — with your security architect,
not a sales deck.