Controlling mobile device access to secure data

Patent metadata

Field	Value
Publication number	US-9858428-B2
Application number	US-201715422761-A
Country	US
Kind code	B2
Filing date	Feb 2, 2017
Priority date	Oct 16, 2012
Publication date	Jan 2, 2018
Grant date	Jan 2, 2018

Abstract

Various aspects of the disclosure relate to providing secure containers or data vaults for data of one or more managed applications. In some embodiments, each managed application may be assigned its own private data vault and/or may be assigned a shared data vault that is accessible to at least one other managed application. As the managed application executes, calls for access to the data may be intercepted and redirected to the secure containers. Data stored in a secure container may be encrypted according to a policy. Other aspects relate to deleting data from a secure container, such as via a selective wipe of data associated with a managed application. Further aspects relate to configuring and creating the secure containers, retrieving key information required to encrypt/decrypt the data stored in the secure containers, and publishing the managed applications, policy information and key information for download to a mobile device.

First claim

We claim:

1. A method, comprising:
configuring a mobile device such that a managed application of the mobile device is able to be executed in accordance with policy information that defines a management framework for executing the managed application by at least:
configuring, based on at least one first setting of the policy information, a private secure container, which is to be private to the managed application, such that a first set of read or write operations from the managed application is to be redirected to the private secure container;
configuring, based on at least one second setting of the policy information, a shared secure container, which is to be accessible by the managed application and at least one other managed application of the mobile device, such that a second set of read or write operations from the managed application is to be redirected to the shared secure container;
determining that legacy data, which is associated with an application of the mobile device that was executed not in accordance with the management framework, is to be configured for the managed application;
responsive to determining that the legacy data is to be configured for the managed application, encrypting the legacy data, resulting in encrypted legacy data;
storing a first set of the encrypted legacy data in the private secure container; and
storing a second set of the encrypted legacy data in the shared secure container.

2. The method of claim 1 , further comprising:
obtaining, via an access gateway, key information that includes one or more keys for encrypting or decrypting data of the private secure container or the shared secure container.

3. The method of claim 1 , wherein the at least one first setting instructs that the private secure container is to be configured on the mobile device such that the first set of read or write operations from the managed application is to be redirected to the private secure container; and
wherein the at least one second setting instructs that the shared secure container is to be configured on the mobile device such that the second set of read or write operations from the managed application is to be redirected to the private secure container.

4. The method of claim 1 , further comprising:
intercepting a read or write operation from the managed application while the managed application is executing on the mobile device, wherein the read or write operation comprises an application programming interface (API) call available via a file system of the mobile device, wherein the file system of the mobile device is different from both a file system of the private secure container and a file system of the shared secure container, and wherein the read or write operation indicates a type of data to be read or written;
determining, based on the policy information and the type of data to be read or written, whether to redirect the read or write operation to the shared secure container or the private secure container; and
based on the determining, redirecting the read or write operation to the private secure container or the shared secure container.

5. The method of claim 1 , wherein the private secure container and the shared secure container are each a logical interface into which data is read from and written to in an encrypted form.

6. The method of claim 1 , wherein the private secure container is accessible to only the managed application.

7. The method of claim 1 , wherein the shared secure container is accessible to only the managed application and the at least one other managed application, wherein the policy information is assigned to the managed application and the at least one other managed application.

8. A method, comprising:
configuring a mobile device such that a managed application of the mobile device is able to be executed in accordance with policy information that defines a management framework for executing the managed application by at least:
configuring, based on at least one first setting of the policy information, a private secure container, which is to be private to the managed application, such that a first set of read or write operations from the managed application is to be redirected to the private secure container, and
configuring, based on at least one second setting of the policy information, a shared secure container, which is to be accessible by the managed application and at least one other managed application of the mobile device, such that a second set of read or write operations from the managed application is to be redirected to the shared secure container;

intercepting a first read or write operation from the managed application while the managed application is executing on the mobile device, wherein the first read or write operation comprises an application programming interface (API) call available via a file system of the mobile device, wherein the file system of the mobile device is different from both a file system of the private secure container and a file system of the shared secure container;
determining, based on the policy information, whether to redirect the read or write operation to the shared secure container or the private secure container; and
based on the determining, redirecting the first read or write operation to the private secure container or the shared secure container.

9. The method of claim 8 , wherein configuring the shared secure container includes configuring the file system of the shared secure container and an access manager of the shared secure container, and wherein the method further comprises:
managing access to the shared secure container via a client agent installed on the mobile device.

10. The method of claim 8 , wherein the first read or write operation includes a read operation of particular data, and the method further comprises:
retrieving an encrypted form of the particular data from the private secure container based on the file system of the private secure container and an access manager of the private secure container;
decrypting, using a key received via an access gateway, the encrypted form of the particular data, resulting in a decrypted form of the particular data; and
providing the decrypted form of the particular data to the managed application.

11. The method of claim 8 , wherein the first read or write operation includes a write operation of particular data, and the method further comprises:
encrypting, using a key received via an access gateway, the particular data, resulting in an encrypted form of the particular data; and
providing, to the private secure container, the encrypted form of the particular data for storage based on the file system of the private secure container and an access manager of the private secure container.

12. The method of claim 8 , further comprising initiating a configuration process for the managed application, and wherein the configuring of the mobile device is performed responsive to the initiating.

13. The method of claim 8 , further comprising:
configuring a policy-aware interception layer to perform the intercepting of the first read or write operation.

14. An apparatus, comprising:
at least one processor; and
memory storing executable instructions configured to, when executed by the at least one processor, cause the apparatus to:
configure the apparatus such that a managed application of the apparatus is able to be executed in accordance with policy information that defines a management framework for executing the managed application by at least:
configuring, based on at least one first setting of the policy information, a private secure container, which is

Assignees

• Citrix Systems Inc

Inventors

• Barton Gary
• Lang Zhongmin
• Desai Nitin
• Walker James Robert

Classifications

• G06F21/60

  Protecting data · CPC title

• H04L63/0428

  wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title

• G06F21/602 Primary

  Providing cryptographic facilities or services · CPC title

• G06F21/53 Primary

  by executing in a restricted environment, e.g. sandbox or secure virtual machine · CPC title

• G06F2221/2143

  Clearing memory, e.g. to prevent the data from being stolen · CPC title