SECURE MOBILE FRAMEWORK

• US 20140245377A1
• Filed: 05/01/2014
• Published: 08/28/2014
• Est. Priority Date: 03/30/2012
• Status: Active Grant

• Current Assignee: Synchronoss Technologies Incorporated
• Original Assignee: Goldman Sachs & Company (Goldman Sachs Group Incorporated)
• Inventors: Faltyn, Daniel, Smith, Andrew J.R.
• Granted Patent: US 9,467,475 B2
• Time in Patent Office: Days
• US Class Current: 726/1
• 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/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/37 Managing security policies for mobile devices or for controlling mobile applications

Abstract

Systems and methods for a secure mobile framework to securely connect applications running on mobile devices to services within an enterprise are provided. Various embodiments provide mechanisms of securitizing data and communication between mobile devices and end point services accessed from a gateway of responsible authorization, authentication, anomaly detection, fraud detection, and policy management. Some embodiments provide for the integration of server and client side security mechanisms, binding of a user/application/device to an endpoint service along with multiple encryption mechanisms. For example, the secure mobile framework provides a secure container on the mobile device, secure files, a virtual file system partition, a multiple level authentication approach (e.g., to access a secure container on the mobile device and to access enterprise services), and a server side fraud detection system.

Claims

1. A method comprising:

receiving, at a gateway, a request from an initiating device to establish a service connection between an enterprise managed application running on the initiating device and an enterprise service, wherein the request includes authentication credentials associated with an end-user;

generating a framework authentication token;

transmitting the framework authentication token to the initiating device, wherein upon receipt the initiating device initiates a service connection request based on the authentication token; and

creating a secure connection between the enterprise service and the initiating device upon successful validation of the service connection request.

2. The method of claim 1, wherein any data transmitted to the initiating device is stored within a secure container only accessible by the enterprise managed application.

3. The method of claim 1, further comprising gathering information about the initiating device and the enterprise managed application.

4. The method of claim 1, further comprising determining a policy that the initiating device should enact in managing the enterprise managed application.

5. The method of claim 4, wherein the secure connection will not be created if the enterprise cannot verify the initiating device is enacting the policy.