Subject: [Teep] Attestation

From: Hannes Tschofenig <[email-masked]>
Date: Wed, 8 Mar 2017 11:00:19 +0000

Hi all,

when I briefly presented the TEEP BOF effort to the folks from the IoT Directorate last Monday I was told that there are various efforts ongoing on attestation. Since we use the attestation concept in the Open Trust Protocol draft as well I thought it would be useful to explain what it actually means.

In a nutshell, the idea of attestation in this context is that the device demonstrates that it is equipped with a TEE functionality (rather than just running everything in software). The attestation at the version -03 draft is provided using two different keys, namely based on

*       a key pair that is provided during manufacturing (the TEE key pair) for use with the trusted application manager, and

*       a key pair that is dynamically generated when a security domain is created for use with the service provider. This key pair is supposed to provide additional privacy properties since different service providers are not able to see the TEE key).

Ciao
Hannes

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.