Securely operating a process using user-specific and device-specific security constraints

• US 9,871,821 B2
• Filed: 11/11/2014
• Issued: 01/16/2018
• Est. Priority Date: 11/11/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Ponsini, Nicolas, Vetillard, Eric
• Primary Examiner(s): Nguyen, Kevin
• Application Number:
  US14/538,514
• Publication Number:
  US 20160134660A1
• Time in Patent Office: 1,162 Days
• Field of Search: 715744, 715780, 715851-853, 715765
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: H04L 2209/64 Self-signed certificates
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

A method for enforcing secure processes between a user and a device involves determining that the user has initiated installation of a secure application, installing the RA part of the secure application, triggering a trusted UI session upon realization that the TA part of the secure application is not installed, receiving, via the trusted UI session, user credentials for authenticating the user and enforcing user-specific and device-specific security, cryptographically signing combined user credentials with a cryptographic signature to obtain an authentication object, passing the authentication object to a service provider associated with the secure application for extraction of the user credentials, and generating an authorization token permitting the installation of the TA part of the secure application upon verification of the cryptographically signed authentication object.

Claims

1. A method, comprising:

determining that a user has initiated an installation of a secure application on a device owned by the user, the secure application comprising a rich application (RA) part and a trusted application (TA) part, wherein the rich application part operates using resources shared with other applications, and wherein the trusted application part operates in an isolated execution environment with functionality to provide security services to the rich application part;

installing the RA part of the secure application on the device;

triggering, by the RA executing on the device, a trusted user interface (UI) session, upon realization that the TA part of the secure application is not installed in the isolated execution environment on the device, wherein the trusted UI session is initiated to enforce user-specific and device-specific security criteria;

receiving, via the trusted UI session, user credentials for authenticating the user;

combining the user credentials with a unique identifier of the isolated execution environment in which the TA part of the secure application operates to obtain combined user credentials;

cryptographically signing the combined user credentials with a cryptographic signature to obtain an authentication object, wherein the authentication object facilitates the enforcement of the user-specific and the device-specific security criteria;

passing the authentication object to a service provider associated with the secure application for extraction of the user credentials; and

generating, by an authorization entity, an authorization token permitting the installation of the TA part of the secure application, upon verification of the cryptographically signed authentication object.

2. The method of claim 1, wherein triggering a trusted UI session further comprises:

requesting, by the RA part of the secure application, a user-binding TA to initiate the trusted UI session, wherein the user-binding TA is a system application that is an integrated part of the isolated execution environment on the device.

3. The method of claim 1, further comprising:

using the authorization token to complete installation of the secure application by installing the TA part of the secure application within the isolated execution environment on the device.

4. The method of claim 1, further comprising:

storing a mapping of the user and the unique identifier in a user-to-provider mapping on a back-end server, wherein the user-to-provider mapping is configured to perform the verification of the cryptographic signature and the request for generation of the authorization token.

5. The method of claim 1, wherein the user credentials comprise at least one selected from a group consisting of biometric information, a one-time password (OTP), a username, and a password.

6. The method of claim 1, wherein the device is an Internet-enabled electronic device.

7. The method of claim 1, wherein the trusted UI session is configured to:

obtain a derived version of the user credentials; and

delete an original version of the user credentials provided by the user via the trusted UI session,

wherein the derived version of the user credentials are concatenated with the unique identifier and cryptographically signed to obtain the authentication object.

8. The method of claim 7, wherein the derived version of the user credentials is obtained by one of encrypting the original version of the user credentials or hashing the user credentials.

9. The method of claim 1, wherein when the trusted UT session is executing on the device, the trusted UI session presents a security indicator to the user.

10. The method of claim 9, wherein the security indicator is one selected from a group consisting of a dedicated light on the device, a phrase or sentence known only to the user displayed during the trusted UI session, or a picture provided by the user displayed during the trusted UI session.

11. The method of claim 1, further comprising:

verifying the cryptographic signature by the back-end server, resulting in a one-to-one binding between a single user, a single device, and a single application executing on the device.

12. A system, comprising:

a device on which an installation of a secure application is initiated by a user, wherein the device is owned by the user;

a service provider configured to provide the secure application to be installed on the device, the secure application comprising a rich application (RA) part and a trusted application (TA) part, wherein the rich application part operates using resources shared with other applications, and wherein the trusted application part operates in an isolated execution environment with functionality to provide security services to the rich application part; and

a back-end server comprising an authorization entity configured to generate an authorization token permitting installation of the TA part of the secure application, upon verification of an authentication object,

wherein, when installation of the secure application is initiated by the user, the RA is configured to request a user-binding TA in the isolated execution environment to initiate a trusted user interface (UI) session by which user credentials are obtained from the user,

wherein the authentication object is generated by;

combining the user credentials obtained via the trusted UI session with a unique identifier of the isolated execution environment on the device to obtain combined user credentials, and

cryptographically signing the combined user credentials using a cryptographic signature to obtain the authentication object,

wherein the service provider is further configured to receive the authentication object from the RA part of the secure application to check the user credentials, and

wherein the back-end server is configured to verify the cryptographically signed authentication object, and, using the verified authentication object, generate the authorization token authorizing the installation of the TA part of the secure application.

13. The system of claim 12, wherein the back-end server is further configured to store a mapping of the user and the unique identifier of the isolated execution environment on the device owned by the user in a user-to-provider mapping.

14. The system of claim 12, wherein the trusted UI session is configured to:

obtain a derived version of the user credentials; and

delete an original version of the user credentials provided by the user via the trusted UI session,

wherein the derived version of the user credentials are combined with the unique identifier and cryptographically signed to obtain the authentication object.

15. The system of claim 14, wherein the derived version of the user credentials is obtained by one of encrypting the original version of the user credentials or hashing the user credentials.

16. The system of claim 12, wherein when the trusted UI session is executing on the device, the trusted UI session presents a security indicator to the user.

17. The system of claim 16, wherein the security indicator is one selected from a group consisting of a dedicated light on the device, a phrase or sentence known only to the user displayed during the trusted UI session, or a picture provided by the user displayed during the trusted UI session.

18. The system of claim 12, wherein the user-binding TA is a system application that is an integrated part of the isolated execution environment on the device.

19. A non-transitory computer readable medium comprising instructions that, when executed by a computer processor, perform a method comprising:

determining that a user has initiated an installation of a secure application on a device owned by the user, the secure application comprising a rich application (RA) part and a trusted application (TA) part, wherein the rich application part operates using resources shared with other applications, and wherein the trusted application part operates in an isolated execution environment with functionality to provide security services to the rich application part;

installing the RA part of the secure application on the device;

triggering, by the RA executing on the device, a trusted user interface (UI) session, upon realization that the TA part of the secure application is not installed in the isolated execution environment on the device, wherein the trusted UI session is initiated to enforce user-specific and device-specific security criteria;

receiving, via the trusted UI session, user credentials for authenticating the user;

combining the user credentials with a unique identifier of the isolated execution environment in which the TA part of the secure application operates to obtain combined user credentials;

cryptographically signing the combined user credentials with a cryptographic signature to obtain an authentication object, wherein the authentication object facilitates the enforcement of the user-specific and the device-specific security criteria;

passing the authentication object to a service provider associated with the secure application for extraction of the user credentials; and

generating, by an authorization entity, an authorization token permitting the installation of the TA part of the secure application, upon verification of the cryptographically signed authentication object.

20. The non-transitory computer readable medium of claim 19, wherein the trusted UI session is configured to execute the steps of:

obtaining a derived version of the user credentials; and

deleting an original version of the user credentials provided by the user via the trusted UI session,

wherein the derived version of the user credentials are concatenated with the unique identifier and cryptographically signed to obtain the authentication object.

21. The non-transitory computer readable medium of claim 20, wherein when the trusted UI session is executing on the device, the trusted UI session presents a security indicator to the user.

22. The non-transitory computer readable medium of claim 19, wherein triggering a trusted UI session further comprises:

requesting, by the RA part of the secure application, a user-binding TA to initiate the trusted UI session, wherein the user-binding TA is a system application that is an integrated part of the isolated execution environment on the device.