US 12,034,870 B2
Method for securely diversifying a generic application stored in a secure processor of a terminal
Guillaume Phan, Paris (FR); Emmanuel Lepavec, Paris (FR); Nicolas Vienne, Orsay (FR); Olivier Poncelet, Rueil Malmaison (FR); and Evangelos Spyropoulos, Champigny sur Marne (FR)
Assigned to THALES DIS FRANCE SAS, Meudon (FR)
Appl. No. 17/792,432
Filed by THALES DIS FRANCE SAS, Meudon (FR)
PCT Filed Dec. 23, 2020, PCT No. PCT/EP2020/087805
§ 371(c)(1), (2) Date Jul. 13, 2022,
PCT Pub. No. WO2021/148223, PCT Pub. Date Jul. 29, 2021.
Claims priority of application No. 20305059 (EP), filed on Jan. 24, 2020.
Prior Publication US 2023/0037536 A1, Feb. 9, 2023
Int. Cl. H04L 9/32 (2006.01); H04L 9/08 (2006.01)
CPC H04L 9/3265 (2013.01) [H04L 9/0825 (2013.01); H04L 9/3271 (2013.01)] 4 Claims
OG exemplary drawing
 
1. A method for securely diversifying a generic application stored in a secure processor of a terminal, said method comprising:
Generating at the request of a manager application hosted in an application processor of said terminal, at the level of a distant server, a server challenge;
Sending said server challenge to said application;
Generating a first message (MSG1) at said application, said first message (MSG1) being function of said server challenge, an application challenge and an unique identifier (APP.ID) of said application;
Sending said first message (MSG1) to a Root-Of-Trust service hosted in the secure processor of said terminal, said Root-of-Trust service generating an attestation of said first message, said attestation guaranteeing that said first message (MSG1) has not been modified and originates from said secure processor;
Transmitting said attestation of said first message (MSG1) to said distant server in an enablement request message;
At the level of said distant server:
Verifying that said attestation of said first message (MSG1) has been provided by said Root-of-Trust service;
Verifying that said first message (MSG1) contains said server challenge;
Returning to said application an enablement payload containing a second message (MSG2) and a public key certificate holding the public key that shall be used to verify a signature of said second message (MSG2), said second message (MSG2) being composed of said application challenge; and
At the level of said application, when receiving said enablement payload:
Verifying said public key certificate;
Verifying said signature of said second message; and
Verifying that said second message (MSG2) contains said application challenge.