Patent Application
20140281539
Various embodiments of the present invention generally relate to mobile devices. More specifically, some embodiments of the present invention relate to a secure mobile framework for securely connecting applications running on mobile devices to services within an enterprise.
Many companies or enterprises are either providing mobile devices (e.g., smartphones, tablets, etc.) to employees or allowing employees to bring their own mobile device. However, allowing employees to access services within the company through a mobile device has increased the company's exposure to potential security breaches. For example, if an employee lost their mobile device, an unauthorized party could retrieve any unsecured data on the phone and potentially access services within the company. As another example, if the employee leaves the company and does not give back the mobile device, the former employee could still potentially access sensitive data stored on the device or within the company.
In order to mitigate this type of unauthorized access, many companies use mobile device management (MDM) policies to restrict control of the mobile devices and thereby reduce potential security risks for mobile devices that are capable of connecting to services within the enterprise. The MDM policies that are set by the enterprise control and protect data through management of the configuration settings of the mobile devices. In order to manage the configuration settings, over-the-air programming (OTA) capabilities are often used. The use of OTA capabilities allows the enterprise to remotely configure a single mobile device or an entire fleet of mobile devices, to send software and operating system (OS) updates, and to remotely lock and wipe a device in order to protect the data stored on the device when it is lost or stolen, etc.
However, the restrictions imposed by the MDM polices can be cumbersome to the user who may also be using the device in a personal capacity. For example, an MDM policy may require the mobile device to auto lock and prompt the user to provide a password with a particular set of characteristics before the mobile device is unlocked. The user may find these restrictions annoying. As such, there are a number of challenges and inefficiencies created in traditional mobile device management.
Systems and methods are described for a secure mobile framework capable of securely connecting applications running on mobile devices to services (e.g., an e-mail service, a trading service, or a reservation service) within an enterprise. In some embodiments, an authentication request from a remote device to access a service provided by an enterprise can be received at a gateway associated with the enterprise. The request can originate from an enterprise-managed application running on the remote device. A framework authentication token and security policy (e.g., password structure, password duration, access controls for an application and/or secure container of data, etc.) can be generated.
The security policy can be based on the service provided by the enterprise that the remote device is requesting to access. The framework authentication token and the security policy can then be transmitted to the remote device which ensures compliance with the security policy before generating a connection request to connect to the service within the enterprise. The connection request can be based on the framework authentication token and the security policy. A service authenticator determines if the application running on the remote device is authorized to access the service. Some embodiments monitor interactions between the enterprise-managed application and the service. Upon detecting a violation of one or more fraud policies at the mobile device and/or gateway, an elevated authentication request can be generated.
In some embodiments, a request can be received from an initiating device to establish a service connection between an enterprise-managed application running on the initiating device and an enterprise service. The request includes authentication credentials associated with an end-user. A framework authentication token can be generated and transmitted to the initiating device, wherein upon receipt the initiating device initiates a service connection request based on the authentication token. A secure connection can be created between the enterprise service and the initiating device upon successful validation (e.g., authorization and authentication) of the service connection request. Any data transmitted to the initiating device using the stored connection can be stored within a secure container that is only accessible by the enterprise-managed application.
One of the immediate objectives of any hacker is to obtain application content and/or alter the binary to satisfy their own requirements. The later situation, which presents a more significant threat, enables the hacker to launch attacks using the legitimate user credentials if they can compromise the device in an undetected fashion. As such, the authentication framework, in accordance with various embodiments, may validate, or at least require that, the operating system integrity and/or the enterprise-managed application integrity be determined if a connection can be established between the enterprise-managed application and the service.
One of the overall objectives of evaluating the operating system integrity (e.g., jailbreak detection or rooting) is to evaluate the integrity of execution environment by testing various aspects of the sandbox. The sandbox is a set of restrictive policies and mechanisms which the operating system uses to enforce a particular scope of operation on the application. Thus, various embodiments have the application test known limits. If these known limits can be passed, then the device appears to have a compromised operating system integrity (e.g., jail broken or rooted). However, the hacker may suspect there are protections in the code. Thus, some embodiments are designed to force or lead the hacker down an avenue of analysis and patching that requires all checks to be discovered and removed. Various embodiments also add safeguards and countermeasures to make the cost of getting the analysis wrong and expensive by destroying usable information as quickly as possible. In some embodiments, the code path can be changed to yield different results or ultimately deny access to the enterprise.
Some embodiments not only check the OS integrity, but also check the executing application's integrity. This is certainly one form of defense against the broken operating system which looks intact however allows a re-crafted and malicious binary to operate. There are some inherent limitations to guaranteeing operating system integrity by the very nature of where the checks are being performed. If a compromised (e.g., jail broken or rooted) operating system looks perfectly intact from the applications perspective, then the application will operate under that assumption. Alternatively, if the hacker completely analyzes the binary and removes all integrity checks perfectly the first time such that it executes as if there were no checks engineered into it then equally it would act as normal. In both of these situations, additional defenses may be found in a DMZ and anomaly detection system which monitor the use of the applications activity to differentiate between legitimate and illegitimate users.
Embodiments of the present invention also include computer-readable storage media containing sets of instructions to cause one or more processors to perform the methods, variations of the methods, and other operations described herein.
In various embodiments, a system can include a gateway, an authenticator, a token generator, a communications module, a discovery service, and/or a fraud detection module. The gateway can be configured to provide remote devices access to services of an enterprise. In some embodiments, the gateway can include multiple levels, each of which provides isolated authentication protocols and activity logging. The remote devices can have stored thereon one or more applications managed by the enterprise. The authenticator can be configured to determine if a user is authorized to access the enterprise and to construct policies regarding the management of the one or more applications.
The token generator can be configured to generate one or more tokens (e.g., authentication token, a user binding token, and/or a framework authentication token) for creating secure connections between one or more applications managed by the enterprise and servers. The tokens can be based on various identifiers such as, but not limited to the following: user identifiers, device identifiers, device type identifiers, application family identifiers, etc. Some tokens may include a binding of other tokens. For example, in one embodiment, a framework authentication token can be based on an enterprise authentication token, a user binding token, and/or a framework authentication token expiration date. In some embodiments, one or more of the tokens may be cryptographically secured (e.g., digitally signed) that allow for the system to detect if the tokens have been tampered with or altered.
The communications module can be configured to communicate the policies to the remote devices. The discovery service can be configured to determine which of the services of the enterprise to connect with the one or more applications. The anomaly detector can be configured to monitor activity between the remote devices and the servers and generate an indicator of anomalies in activity. For example, the anomaly detector may monitor the IP velocity of the user, failed log-in attempts, etc.
While multiple embodiments are disclosed, still other embodiments of the present invention will become apparent to those skilled in the art from the following detailed description, which shows and describes illustrative embodiments of the invention. As will be realized, the invention is capable of modifications in various aspects, all without departing from the scope of the present invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not restrictive.
Embodiments of the present invention will be described and explained through the use of the accompanying drawings in which:
The drawings have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be expanded or reduced to help improve the understanding of the embodiments of the present invention. Similarly, some components and/or operations may be separated into different blocks or combined into a single block for the purposes of discussion of some of the embodiments of the present invention. Moreover, while the invention is amenable to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and are described in detail below. The intention, however, is not to limit the invention to the particular embodiments described. On the contrary, the invention is intended to cover all modifications, equivalents, and alternatives falling within the scope of the invention as defined by the appended claims.
Various embodiments of the present invention relate generally to a secure mobile framework capable of securely connecting applications running on mobile devices to services within an enterprise. Some examples of services provided by an enterprise include, but are not limited to, an e-mail service, a trading service, a payment processing service, a customer relationship management service, an inventory system service, a business intelligence service, a healthcare service, a student information service, a reservation service, secure services, and/or other services containing sensitive information. In accordance with some embodiments, the secure mobile framework provides a collection of software libraries and service components which provide software developers the ability to build secure applications on non-enterprise mobile devices. The secure mobile framework can be used in conjunction by enterprises that have firewalled content, services, and network from the public network through means of a DMZ-type architecture. As a result, much of the enterprise's existing authentication and authorization systems can be utilized. Client and server libraries can be utilized or extended to provide secure storage and communication in both the client and server applications.
There are a number of enterprises which through internal policy or regulation need to ensure that enterprise content and communication is protected, managed and monitored. Normally for devices managed by the enterprise, the aforementioned control requirements are directly implemented through device and operating system (OS) management. However, for devices which are not managed by the enterprise and cannot connect directly to the enterprise network, there is a need to ensure that the same controls are applied to enterprise applications running on these unmanaged devices.
In accordance with various embodiments, the secure mobile framework can provide one or more of the following features to connect and utilize services within the enterprise: 1) mechanisms to store enterprise content on a device in a protected manner whereby the enterprise content can only be accessed by authorized users, possibly offline, and be managed through enterprise policy; 2) mechanisms to provide multiple authentications against the gateway (i.e., framework authentication) and against the enterprise services (i.e., enterprise authentication), provide secure connection to those enterprise services where authorized, and manage per service access through enterprise policy; 3) mechanism to manage and support connected applications and their dependent services; and 4) mechanisms to dynamically detect an undesirable or unsafe operating system environment and manage through a multi-step process (e.g., evaluating the policy, interrogation of the program, interrogation of the OS, and/or performing other checks in the client and/or server environments).
The gateway can generate one or more tokens which can be used for authentication. For example, in some embodiments, an enterprise authentication token (EAT) can be generated representing a single or multi-factor credentials that can be used to authenticate with a given company as if single or multi factor credentials were presented, for a finite period of time. A user binding token (UBT) can also be used in one or more embodiments. The UBT can be an amalgamated, unique representation of a user (id), device (id), type of device, and app family. In addition, a framework authentication token (FAT) can be used in various embodiments. The FAT can be created by binding an EAT, UBT, and an expiration date used to authenticate with the framework. One advantage of this construction of the FAT is that the details cannot be tampered with by an unauthorized party.
In some embodiments, secure mobile framework client and server components can be used to detect the integrity of the operational environment for the client application. Given that the client application is executed within an unmanaged operating system environment, the client application may need to ascertain, as best it can, if the environment is considered to be unsafe. Common examples of unsafe operating system environments are devices on which the operating system restrictions that have been imposed by the OS manufacturer have been removed. This is commonly referred to as jailbreaking or rooting. In the case of Apple's iOS, for example, this process usually means removing various components of the code signing verification system and file access imposed by Seatbelt.
The operating system provides the security bedrock for many embodiments of the secure mobile framework by providing secure boot chain, signature enforced executables and sandboxed applications. A broken operating system cannot be trusted as it is possible that the broken operating system could be running malicious code performing anything from data leakage to a platform for advance persistent threat attacks (APT). Because the process of comprising operating system restrictions (e.g., jailbreaking an iOS device or rooting an Android device) is relatively easy it is quite possible that many of the devices will be broken for “legitimate” reasons.
However, even an operating system broken for a “legitimate” reason still breaks the security model and opens doors for hackers. In fact, if steps are not taken to close some obvious holes, like changing the root password, the ability of a hacker to gain control of the device becomes extremely trivial. As a result, the client applications in various embodiments perform the necessary checks to verify and establish if the original integrity of the operating system has been compromised. Certainly with iOS these checks have to be done by the application itself as there are no extraneous methods available due to the nature of the devices configuration and Apple restrictions. As such, various embodiments provide a multi-point check of the operating system through the application before allowing the remote device to connect to the gateway services.
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. It will be apparent, however, to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details.
While, for convenience, embodiments of the present invention are described with reference to dedicated enterprise-based setups, embodiments of the present invention are equally applicable to various other operational models such as cloud-based models. In addition, while some of the following discussion focuses on iOS, many of the ideas readily translate to Android and other mobile operating systems. Moreover, the techniques introduced here can be embodied as special-purpose hardware (e.g., circuitry), as programmable circuitry appropriately programmed with software and/or firmware, or as a combination of special-purpose and programmable circuitry. Hence, embodiments may include a machine-readable medium having stored thereon instructions that may be used to program a computer (or other electronic devices) to perform a process. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, compact disc read-only memories (CD-ROMs), magneto-optical disks, ROMs, random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), application-specific integrated circuits (ASICs), magnetic or optical cards, flash memory, or other type of media/machine-readable medium suitable for storing electronic instructions.
Brief definitions of terms, abbreviations, and phrases used throughout this application are given below.
The terms “connected” or “coupled” and related terms are used in an operational sense and are not necessarily limited to a direct physical connection or coupling. Thus, for example, two devices may be coupled directly, or via one or more intermediary media or devices. As another example, devices (e.g., mobile devices, server machines, etc.) may be coupled in such a way that information can be passed therebetween, while not sharing any physical connection with one another. Based on the disclosure provided herein, one of ordinary skill in the art will appreciate a variety of ways in which connection or coupling exists in accordance with the aforementioned definition.
The phrases “in some embodiments,” “according to some embodiments,” “in the embodiments shown,” “in other embodiments,” and the like generally mean the particular feature, structure, or characteristic following the phrase is included in at least one implementation of the present invention, and may be included in more than one implementation. In addition, such phrases do not necessarily refer to the same embodiments or different embodiments.
If the specification states a component or feature “may”, “can”, “could”, or “might” be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic.
The term “module” refers broadly to a software, hardware, firmware, or service (or any combination thereof) component. Modules are typically functional components that can generate useful data or other output using specified input(s). A module may or may not be self-contained. An application program (also called an “application”) may include one or more modules, or a module can include one or more application programs.
Gateway 130 manages the access of enterprise-managed applications 110A-110N and user devices 120A-120N. Gateway 130 can be used to verify and establish a trust relationship between the enterprise-managed applications 110A-110N and business-specific services provided by the enterprise. For example, in some embodiments, the data and requests initially submitted by enterprise-managed applications 110A-110N are transferred between the device and gateway 130 via network 140. Once gateway 130 is satisfied with the security of the device, then gateway 130 can open up a channel to some business-specific service within the application management platform 150 and enterprise services 160. Gateway 130 and services within the application management platform 150 can have multiple independent layers of security and checks.
User devices 120A-120N can be any computing device capable of receiving user input as well as transmitting and/or receiving data via the network 140. In one embodiment, user devices 120A-120N can be any device having computer functionality, such as a personal digital assistant (PDA), mobile telephone, smartphone, tablet, wearable types of mobile computers, body-mounted computers, or similar device. User devices 120A-120N can be configured to communicate via network 140, which may comprise any combination of local area and/or wide area networks, using wired and/or wireless communication systems. In one embodiment, network 140 uses standard communications technologies and/or protocols. Thus, network 140 may include links using technologies such as Ethernet, 802.11, worldwide interoperability for microwave access (WiMAX), 3G, 4G, CDMA, digital subscriber line (DSL), etc.
Similarly, the networking protocols used within the various layers of network 140 may include multiprotocol label switching (MPLS), transmission control protocol/Internet protocol (TCP/IP), User Datagram Protocol (UDP), hypertext transport protocol (HTTP), hypertext transport protocol secure (HTTPs), simple mail transfer protocol (SMTP), file transfer protocol (FTP), secure file transfer protocol (SFTP), and/or other networking protocols. Data exchanged over network 140 may be represented using technologies and/or formats including hypertext markup language (HTML) or extensible markup language (XML). In addition, all or some links can be encrypted using conventional encryption technologies such as secure sockets layer (SSL), transport layer security (TLS), and Internet Protocol security (IPsec).
A variety of authentication and security checks can be performed at the enterprise during authentication operation 230. In some embodiments, for example, once the set of credentials are received from the user, an authorization request can be sent from the remote device (i.e., the client) to the gateway server. The gateway server can determine a current policy which should be applied at the remote device and send policy information from the gateway server to the remote device. Then, the device characteristics can be checked and new container credentials can be acquired if necessary. If the gateway determines that the application should have access to one or more servers within the enterprise, creation operation 240 can be used to create a binding between the application and an enterprise service.
Various embodiments of the present invention provide systems and methods for checking the operating system integrity as part of authentication operation 230. These checks may be performed at the user device and/or at the enterprise. A broken operating system cannot be trusted as it is possible that the mobile device could be running malicious code performing anything from data leakage to a platform for advanced persistent threat attacks (APT). Because the process of jailbreaking an iOS device is relatively easy, it is quite possible that many of the devices will be broken for “legitimate” reasons. This still breaks the security model and opens doors for hackers. In fact, if steps are not taken to close some obvious holes, like changing the root password, the ability of a hacker to gain control of the device becomes extremely trivial. Various embodiments allow an enterprise gateway to use the operating integrity check in conjunction with other mobile application management techniques to determine if any violations are discovered. Access to enterprise services can be denied or immediately suspended if any violations are discovered.
Memory 305 can be any device, mechanism, or populated data structure used for storing information. In accordance with some embodiments of the present invention, memory 305 can encompass any type of, but is not limited to, volatile memory, nonvolatile memory, and dynamic memory. For example, memory 305 can be random access memory, memory storage devices, optical memory devices, media magnetic media, floppy disks, magnetic tapes, hard drives, SDRAM, RDRAM, DDR RAM, erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), compact disks, DVDs, and/or the like. In accordance with some embodiments, memory 305 may include one or more disk drives, flash drives, one or more databases, one or more tables, one or more files, local cache memories, processor cache memories, relational databases, flat databases, and/or the like. In addition, those of ordinary skill in the art will appreciate many additional devices and techniques for storing information which can be used as memory 305
Memory 305 may be used to store instructions for running one or more applications or modules on application processor(s) 310. For example, memory 305 could be used in one or more embodiments to house all or some of the instructions needed to execute the functionality of operating system 325, application 330, secure container 335, validator 340, key generator 345, encryption/decryption module 350, access module 355, data removal module 360, information module 365, policy manager 370, communications module 375, and/or GUI generation module 380.
Application processor(s) (AP) 310 are the main processors of user device 120. Application processor(s) provide the processing power to support software applications, memory management, graphics processing, and multimedia. AP 310 is communicably coupled with memory 305 and configured to run the operating system 325, the user interface, and the applications 330 stored on memory 305. Baseband processor 315 is configured to perform signal processing and implement/manage real-time radio transmission operations of user device 120. These processors along with the other components may be powered by power supply 320 (e.g., a battery or other power source).
Operating system 325 provides a software package that is capable of managing the resources (e.g., hardware resource) of user device 120. Operating system 325 can also provide common services for software applications running on AP 310. In accordance with various embodiments of the present invention, operating system 325 may act as an intermediary between applications 330 and hardware components. Applications 330 may include can include enterprise-managed applications 110A-110N that can be used to access services and data within the enterprise.
User device 120 may also include secure container 335 that allows for information to be securely stored. Secure container 335 may include one or more tokens or access keys that can be used to create a secure connection or validate a current state of user device 120. In some embodiments, secure container 335 can securely store information about an uncompromised operating system 325, information about an uncompromised application, and/or other information that may be sensitive.
In accordance with one or more embodiments, secure container 335 may be encrypted/decrypted using information about operating system 325. Secure container 335 may have multiple storage compartments that each contain different information. The encryption/decryption process may use a multi-level or multi-stage key generation sequence. For example, validator 340 can be used to test the operating system integrity and/or the application integrity at multiple points. Key generator 345 can then generate a key to access secure container 335 by performing a multi-level or multi-stage key generation sequence. The key generation sequence may be based on the operating system integrity and/or the application integrity determined by validator 340.
If the current state of operating system 325 and/or the application does not match the state of the operating system 325 used to encrypt secure container 335, then encryption/decryption module 350 will generate a different key than the access key needed to access secure container 335. The key generated by encryption/decryption module 350 can then be passed to access module 355. Access module 355 is configured to allow access to the secure container within the memory of the remote device. If the key generated by encryption/decryption module 350 does not successfully decrypt the content, data removal module 360 can remove data stored in the secure container. In some embodiments, when validator 340 determines that the operating system integrity has been compromised, an immediate request to remove the data may be sent to data removal module 360 and/or a notification may be sent to the enterprise.
Other types of inputs may also be part of the key generation sequence. For example, information from a remote service or gateway may be used. As another example, user-provided inputs (e.g., passwords) may be used in the key generation sequence. Information module 365 can be used to collect this information. In some cases, various information about the current policy being enforced by policy manager 370 may also be used as part of the key generation sequence.
Communications module 375 may be configured to manage and translate any requests or messages between components of user device 120, graphical user interface screens, remote service, networks, and/or any other component into a format required by the destination component and/or system. Similarly, communications module 375 may be used to communicate between systems and/or modules that use different communication protocols, data formats, or messaging routines. According to some embodiments, system components can communicate through messaging methods including extensible markup language (XML), proprietary message formats, and/or others.
GUI generation module 380 can generate one or more GUI screens that allow for interaction with user device 120. In at least one embodiment, GUI generation module 380 generates a graphical user interface allowing a user of the mobile device to set preferences, present reports, set device constraints, and/or otherwise receive or convey information to the user.
Secure storage 410 can securely store enterprise data locally on mobile device 405. Secure storage 410 can include a group of protected files managed as a single unit through policy 420. In some embodiments, enterprise content can be stored in encrypted files and accessed via random access methods. In addition, various mechanisms can be used to set encryption block sizes on a per file basis and simultaneously maintain a sidecar index file used to aid with the synchronization content between client and service. The protected files are held within a secure partition which uses a single encrypted master file to hold per file encryption keys and a translation between applications file names and obfuscate file names. This secure file partition mechanism can be used to securitize not only application content directly but also used as a virtual file system for database servers hosted on the device, logging and telemetry data for customer support.
Policy 420 can be an application-specific (or application family) security policy set by the enterprise with which application 415 should comply. An application family generally refers to a grouping of applications governed by a common policy that shares access to authorization and authentication information on a given device, for a given user. Policy 420 can include the value of security variables used in authorization, authentication, and securitizing data on the device. For example, policy 420 can include password structure, how long the device can remain disconnected from the gateway, how many times the user can fail to enter in a correct password, and other security variables.
A further instance of a secure file partition is authentication store 425 which can contain authentication credentials (e.g., tokens and assertions), policy details, and a master encryption key used to encrypt all other secure file partitions' master files. An authentication store master file store can be encrypted with an ephemeral key generated based on a user password or phrase. Furthermore, authentication store 425 can be shared among multiple applications on the device to form a common store for enterprise access and sharing encrypted content.
Once application 415 and corresponding components are installed on mobile device 405, application 415 can request access to one or more internal services within an enterprise running on servers 430 or virtual machines 435 after passing one or more device security checks. The request from application 415 is first received at a perimeter gateway 440 where a first round of authentication is established before allowing application access to an intermediate layer 445. Intermediate layer 445 authenticates the user and ensures that the policy being enforced by application 415 is up-to-date. In addition, mobile device telemetry and configuration settings can be gathered, processed, analyzed, evaluated, and/or recorded within database 450. This information can be useful in creating (e.g., in real-time or in near real-time) various indicators of fraud or anomaly detection. Intermediate layer 445 also allows application 415 to log into mobile application store 450. In addition, proxy 455 can be used as an intermediary between application 415 and the servers 430.
If the policy and user are successfully validated, then validation operation 550 validates the user's authentication credentials at the gateway. Enterprise credentials are then passed to the destination service during submission operation 560 where authentication and authorization take place during verification operation 570. Upon successful authentication, binding operation 580 creates a binding between the application and the named service.
The enterprise-managed application can use a framework authentication token (FAT) to authenticate with the gateway, and an enterprise authentication token (EAT) to authenticate with a service. Validation operation 630 determines (e.g., using a framework authentication system) the validity of the FAT. A server authorizer can then construct one or more tokens for creating a secure connection to the enterprise service. For example, in some embodiments the server authorizer can create a User Binding Token (UBT) consisting of the user id, the application id, and the device id. In addition, the FAT can be created by binding the UBT, EAT, and an expiration date. In addition, the server authorizer may determine if the user is authorized to access the enterprise. A secure mobile framework server can construct a policy based on the enterprise services the user can interact with. The information in the policy can include the FAT expiration date, a type of enterprise authentication the user must perform when the FAT expires, and other policy information used to secure data on the mobile device. The secure mobile framework server gateway can then respond to the mobile device with the FAT and the policy.
The calling client (e.g., the mobile device) can use an authentication store to save the FAT and policy content. The application can then use generation operation 640 to generate a connection request upon verification of the policy enforcement. Then creation operation 650 creates a secure channel between the enterprise-managed application and the enterprise service. For example, the application can ask the client secure mobile framework to connect to a particular enterprise service using some canonical name. Then, the framework can send the service name along with the UBT to the secure mobile framework server service authenticator over the same connection. The service authenticator determines if the UBT is allowed to connect to that destination.
The secure mobile framework server service router can then map the canonical name to the real address of the service, and establish a connection. The mobile application can now communicate freely over a secured channel once the enterprise authentication is successfully completed. On subsequent requests for connections, the application may ask the secure mobile framework to connect to a particular service using some canonical name. The secure mobile framework can then send the service name along with the UBT and EAT to the secure mobile framework gateway. In some embodiments, the next time the application attempts to connect with the service, this information can be used rather than the user entered enterprise credentials, at least until the FAT expires.
Communications API 710 obtains the user's raw credentials or stored token (FAT) to establish a connection with an enterprise gateway using secure key store 730. For example, upon receiving the user's credentials, a secure key can be retrieved from secure key store 730. This key can be used to access a key chain after which subcomponents of the framework can be initialized. System management 735 can receive, from the device/application, an identification of a current policy associated with the application. Using policy management 740 a determination can be made as to whether the policy associated with the application is up to date or needs to be updated. System management 735 can ensure that proper logging, virtual file system management, and page caching occur.
Upon successful authorization and authentication, the gateway requests policy and device information from communications API 710. Upon successful validation, the gateway can bind a connection to a web browser proxy service, capable of making HTTP/S calls within the enterprise. Web browser 705 can then transmit the wrapped HTTP/S requests through this channel.
Upon launching application 815, a request is sent to far mobile content gateway 820. Within the main stack 825 of far mobile content gateway 820, validation and authentication of the user and device can be confirmed. For example, in some embodiments, an enterprise authentication service 830 (e.g., RSA® or Kerberos™) can be used. In some embodiments, the authentication process can include a username, a whitelist check, a policy check, and/or a destination check. In addition, device telemetry and configurations can be monitored and transmitted to a second intermediate authentication layer. These allow for the user, device, and application to be authenticated.
Once the user, device, and application have been authenticated, a connection can be established with server 810. Many embodiments use the various tokens created during the authentication of the user, device, and application for establishing a connection with server 810. Far mobile content gateway 820 can connect with mobile gateway services 835 for additional authentication services for access to servers within the enterprise. For example, in some embodiments, a user can enter a password or other authentication credentials within application 815 that can be used to decrypt data stored locally on the device. Then, the user could present a FAT to a gateway process running on a remote environment. The gateway process uses the FAT to authorize and authenticate the user and the device. Then, to access any particular service, the user would present an EAT to the remote service. In some embodiments, the FAT and EAT can be stored locally on the device after preforming one or more pluggable forms of authentication (e.g., time codes+pin, biometrics, passwords, etc.).
In some embodiments, the form of authentication can be rotated on a predefined schedule (e.g., periodic) or upon detection of one or more events. For example, the gateway can securely transmit the current authentication form to the mobile device which can be stored in the secure store. While
The mobile authorization service can authorize access, generate a UBT, and store the device identifier, the user name, application family, and the UBT. The mobile authorization service signs the UBT and authentication token before returning a policy, a UBT, and a digital signature to the far content gateway. The far content gateway then generates a FAT which is returned along with the policy, UBT and digital signature to the device application. In some cases, the policy may require the device application to request a new password for the secure container. The FAT, UBT, and digital signature can then be stored in the secure container which can be locked with the password.
The device application submits the canonical name of the enterprise service to which the device application wants to connect. The far content gateway uses a destination service module to determine if the UBT is allowed to connect to that service. If the UBT is allowed to connect, the far content gateway binds a connection to the enterprise service, or a proxy to that service. A success code is returned from the far content gateway to the device application along with the latest policy version. The device application checks to see if the policy version just returned is greater than the policy retrieved from the secure container. If the policy version is greater, then the new policy is applied. The FAT can then be retrieved from the secure container and the conversation with the far content gateway can be initiated.
Various embodiments of the secure mobile framework utilize a number of paths which seek the balance between number of checks, types of checks, and actions taken.
Additional checks, such as filesystem checks 1115-1135 can also be used to test the ability to look outside the application's filesystem sandbox. For example, the filesystem checks 1115-1135 can test either the ability to access or open files/directories which should be inaccessible. The result of each of these checks can be combined with an application nonce as part of the ephemeral key generation 1140.
In accordance with various embodiments, there are several types of actions which can be taken as a result of finding the device has a compromised OS integrity. Actions can include visual actions, destructive actions, and/or an absence of a required operation. The visual action can pop up a dialog which indicates to users that the device does not pass the sufficient integrity requirements and that this violates compliance policy. The dialog may be shown for a period of time (e.g., for 5 seconds) before the application exits. The exit may be conducted on a background thread and cannot be easily hooked out through an objective-c message override. This action informs the user that the phone does not pass the sufficient integrity requirements, something they may not be aware of, and that this violates policy. It is expected to be found fairly quickly given its obvious nature, however, it may only be reached after passing through a more destructive check first.
The destructive action calls on a clear method, may be used as part of normal container operation, which removes all container material in the keychain. Once removed, the user is left in the initial provision state and needs to go through the provision process again which requires authentication. The final action effectively does not happen. There are a number of components thrown into the ephemeral container key generation including device reference, salt, password and an application nonce.
Embodiments of the present invention include various steps and operations, which have been described above. A variety of these steps and operations may be performed by hardware components which are part of a mobile device, server, or other computer system used within embodiments of the present invention. In some embodiments, these steps and operations may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, the steps may be performed by a combination of hardware, software, and/or firmware. As such,
Processor(s) 1420 can be any known processor, such as, but not limited to, an Intel® Itanium® or Itanium 2® processor(s); AMD® Opteron® or Athlon MP® processor(s); ARM-based processors; or Motorola® lines of processors. Communication port(s) 1430 can be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, or a Gigabit port using copper or fiber. Communication port(s) 1430 may be chosen depending on a network such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 1400 connects.
Main memory 1440 can be Random Access Memory (RAM) or any other dynamic storage device(s) commonly known in the art. Read only memory 1460 can be any static storage device(s) such as Programmable Read Only Memory (PROM) chips for storing static information such as instructions for processor 1420.
Mass storage 1470 can be used to store information and instructions. For example, hard disks such as the Adaptec® family of SCSI drives, an optical disc, an array of disks such as RAID, such as the Adaptec family of RAID drives, or any other mass storage devices may be used.
Bus 1410 communicatively couples processor(s) 1420 with the other memory, storage, and communication blocks. Bus 1410 can be a PCI/PCI-X or SCSI based system bus depending on the storage devices used.
Removable storage media 1450 can be any kind of external hard-drives, floppy drives, IOMEGA® Zip Drives, Compact Disc—Read Only Memory (CD-ROM), Compact Disc—Re-Writable (CD-RW), and/or Digital Video Disk—Read Only Memory (DVD-ROM).
The components described above are meant to exemplify some types of possibilities. In no way should the aforementioned examples limit the scope of the invention, as they are only exemplary embodiments. Moreover, some of the computer systems (e.g., servers, clients, mobile devices, etc.) contemplated by embodiments of the present invention may not include all of these components. In addition, some of the computer systems may include different configurations and/or additional components from those illustrated in
In conclusion, the present invention provides novel systems, methods and arrangements for a secure mobile framework for enterprise-managed applications. While detailed descriptions of one or more embodiments of the invention have been given above, various alternatives, modifications, and equivalents will be apparent to those skilled in the art without varying from the spirit of the invention. For example, while the embodiments described above refer to particular features, the scope of this invention also includes embodiments having different combinations of features and embodiments that do not include all of the described features.
This application is a continuation-in-part of Ser. No. 13/854,837, filed Apr. 1, 2013 entitled “Secure Mobile Framework” which claims priority to U.S. Provisional Application Ser. No. 61/618,511 filed Mar. 30, 2012 and U.S. Provisional Application Ser. No. 61/806,763 filed Mar. 29, 2013, the entire contents of each are incorporated herein by reference for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| 61618511 | Mar 2012 | US | |
| 61806763 | Mar 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13854837 | Apr 2013 | US |
| Child | 14293765 | US |
