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 (SERVER.CHALLENGE); - Sending said server challenge to said application; - Generating a first message at said application, said first message being function of said server challenge, an application challenge and an unique identifier (APP.ID) of said application; - Sending said first message to a Root-Of-Trust service hosted in a secure processor of said terminal, said Root-of-Trust service generating an attestation of said first message, said attestation guaranteeing that said first message has not been modified and originates from said secure processor; - Transmitting said attestation of said first message to said distant server in an enablement request message; - At the level of said distant server: ○ Verifying that said attestation of said first message has been provided by said Root-of-Trust service; ○ Verifying that said first message contains said server challenge; ∘ Returning to said application an enablement payload containing a second message and a public key certificate holding the public key that shall be used to verify a signature of said second message, said second message being composed of said application challenge; - At the level of said application, when receiving said enablement payload: ○ Verifying said public key certificate; ○ Verifying said signature of said second message; ○ Verifying that said second message contains said application challenge. - 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 (SERVER.CHALLENGE); - Sending said server challenge to said application; - Generating a first message at said application, said first message being function of said server challenge, an application challenge and an unique identifier (APP.ID) of said application; - Sending said first message to a Root-Of-Trust service hosted in a secure processor of said terminal, said Root-of-Trust service generating an attestation of said first message, said attestation guaranteeing that said first message has not been modified and originates from said secure processor; - Transmitting said attestation of said first message to said distant server in an enablement request message; - At the level of said distant server: ○ Verifying that said attestation of said first message has been provided by said Root-of-Trust service; ○ Verifying that said first message contains said server challenge; ∘ Returning to said application an enablement payload containing a second message and a public key certificate holding the public key that shall be used to verify a signature of said second message, said second message being composed of said application challenge; ○ Verifying that said attestation of said first message has been provided by said Root-of-Trust service; ○ Verifying that said first message contains said server challenge; ∘ Returning to said application an enablement payload containing a second message and a public key certificate holding the public key that shall be used to verify a signature of said second message, said second message being composed of said application challenge; - At the level of said application, when receiving said enablement payload: ○ Verifying said public key certificate; ○ Verifying said signature of said second message; ○ Verifying that said second message contains said application challenge. ○ Verifying said public key certificate; ○ Verifying said signature of said second message; ○ Verifying that said second message contains said application challenge.