A More Open Trust Protocol
summary
A new Open Trust Protocol proves an end‑to‑end, developer‑focused way to provision and manage trusted applications over the air into TEEs (ARM TrustZone reference) using PKI: per‑device and per‑firmware certificates, derived per‑service keys, JSON Web Signatures, and OCSP stapling for revocation. The IETF internet‑draft (published July 2016, expires Jan) defines an OT‑RP agent API and operations (get device state, create security domain, install/update/remove TA). It’s vendor‑agnostic, open, already in draft form with ~13 members but adoption remains early.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:27Overview
- 1:55Trust Execution Environment
- 7:43Service Provider
- 9:18Challenges
- 10:28Open Trust Protocol Alliance
- 16:50Model
- 20:02Spec
- 29:32Agent
- 32:24Standard
- 37:36Summary
- 40:24T Providers
- 42:59Service Providers
- 47:36Hardware
related talks
41mOP-TEE - Using TrustZone to Protect Our Own Secrets
29mRemote Attestation of IoT devices using a discrete TPM 2.0
39mSoftware Supply Chain Security with Trusted Execution Environment Provisioning (T...
10mRoot-of-trust - What it is and why you need one in IoT
15mProposal of porting Trusted Execution Environment Provisioning (TEEP) Protocol...
40mTrusted Internet of Things Device Onboarding and Lifecycle Management
25mEstablishing Trusted and Secure Foundation for Device Management Using Open Source Software
18mBeyond the Default Password: Building Trustworthy IoT Products