Re: [Rats] FIDO TPM attestation

"Fuchs, Andreas" <andreas.fuchs@sit.fraunhofer.de> Thu, 14 November 2019 16:18 UTC

Return-Path: <andreas.fuchs@sit.fraunhofer.de>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C14B1120129 for <rats@ietfa.amsl.com>; Thu, 14 Nov 2019 08:18:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z4bLdT0HK22J for <rats@ietfa.amsl.com>; Thu, 14 Nov 2019 08:18:06 -0800 (PST)
Received: from mailext.sit.fraunhofer.de (mailext.sit.fraunhofer.de [141.12.72.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5822A120113 for <rats@ietf.org>; Thu, 14 Nov 2019 08:18:05 -0800 (PST)
Received: from mail.sit.fraunhofer.de (mail.sit.fraunhofer.de [141.12.84.171]) by mailext.sit.fraunhofer.de (8.15.2/8.15.2/Debian-10) with ESMTPS id xAEGI2ZY031949 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA256 bits=128 verify=NOT); Thu, 14 Nov 2019 17:18:03 +0100
Received: from EXCH2010B.sit.fraunhofer.de ([169.254.2.69]) by EXCH2010CAS2.sit.fraunhofer.de ([141.12.84.171]) with mapi id 14.03.0468.000; Thu, 14 Nov 2019 17:17:57 +0100
From: "Fuchs, Andreas" <andreas.fuchs@sit.fraunhofer.de>
To: Laurence Lundblade <lgl@island-resort.com>
CC: "rats@ietf.org" <rats@ietf.org>
Thread-Topic: [Rats] FIDO TPM attestation
Thread-Index: AQHVmdgbKKlnQ1ZLsk2cVdcDGcns46eKarF6gABXgwCAABRmCA==
Date: Thu, 14 Nov 2019 16:17:56 +0000
Message-ID: <9F48E1A823B03B4790B7E6E69430724D0163BD5B5C@EXCH2010B.sit.fraunhofer.de>
References: <62DD1AD3-6F1A-4B2B-8236-10ECCE254443@island-resort.com> <9F48E1A823B03B4790B7E6E69430724D0163BD29CD@EXCH2010B.sit.fraunhofer.de>, <CEB0F75D-E703-41B9-8EEE-C95E848FBC8C@island-resort.com>
In-Reply-To: <CEB0F75D-E703-41B9-8EEE-C95E848FBC8C@island-resort.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [141.12.89.204]
Content-Type: multipart/alternative; boundary="_000_9F48E1A823B03B4790B7E6E69430724D0163BD5B5CEXCH2010Bsitf_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/HUeBXKCteHNJ1JoX__r806iRw-A>
Subject: Re: [Rats] FIDO TPM attestation
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Remote Attestation Procedures <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Nov 2019 16:18:10 -0000

We were talking about FIDO as one of many applications running in a TEE.
They rely on correctness of other TEE-apps and/or the TEE kernel
(or should I rather say TEE operating system). Thus a turing complete solution
(maybe even with loadable apps) and OS cannot be as secure as a special-purpose
functional logic security provider.

Also, by design an on-chip TEE offering cannot be as secure as a physically
separated chip that incorporates smartcard technologies. You also highlight
this by providing yubikey as example which is both; a separate SC-like chip
and fixed functional logic (similar to TPMs).

To conclude: fixed functional logic and separate chips have higher assurance
levels than turing-complete (loadable) areas of the main cpu.

And to your original point: TPMs are the preferred solution for attestation
in contrast to to a TEE-based approach, just as YubiKeys et al are preferred
for FIDO in contrast to a TEE-based approach.

________________________________
From: Laurence Lundblade [lgl@island-resort.com]
Sent: Thursday, November 14, 2019 16:51
To: Fuchs, Andreas
Cc: rats@ietf.org
Subject: Re: [Rats] FIDO TPM attestation


On Nov 14, 2019, at 1:46 AM, Fuchs, Andreas <andreas.fuchs@sit.fraunhofer.de<mailto:andreas.fuchs@sit.fraunhofer.de>> wrote:

The FIDO code running inside a TEE is not standardized (to the level of TPM) and most certainly not CC-evaluated.

That’s not true.

The FIDO L3 and L3+ Certification program<https://fidoalliance.org/certification/authenticator-certification-levels/authenticator-level-3/> is CC (Common Criteria) based (AVA_VAN.3 and AVA_VAN.4).

Many FIDO authenticators run on secure elements which provides roughly equivalent security to a TPM, however since the full authenticator protocol runs on the turing-complete secure element the full FIDO protocol is secured, not just the key storage. Here’s one<https://www.yubico.com/products/yubikey-hardware/yubikey%20neo/>.

Global Platform offers a CC-based certification program for TEE’s<https://www.commoncriteriaportal.org/files/ppfiles/anssi-profil_PP-2014_01.pdf>. FIDO is working on a certification program that will make use of that.

BSI has published a CC-based protection profile for FIDO<https://www.commoncriteriaportal.org/files/ppfiles/pp0096a_pdf.pdf>.

Android Keystore’s now supports StrongBox<https://proandroiddev.com/android-keystore-what-is-the-difference-between-strongbox-and-hardware-backed-keys-4c276ea78fd0>, which puts the keys in a secure element.

Qualcomm’s Snapdragon mobile phone chip has a secure-element like subsystem<https://www.qualcomm.com/news/releases/2019/06/25/qualcomm-snapdragon-855-becomes-first-mobile-soc-receive-smart-card> (not the TEE) that is CC-certified.

TEE and TEE-like offerings are stronger than they used to be, particular by supporting memory encryption.

Turing complete security products come in a range of security levels all the way up the security level offered by a TPM. EAT implementations can be just as secure and certified as TPM attestation.

LL