SECURE EXECUTION OF UNSECURED APPS ON A DEVICE

• US 20120246484A1
• Filed: 12/01/2011
• Published: 09/27/2012
• Est. Priority Date: 03/21/2011
• Status: Active Grant

• Current Assignee: Blue Cedar Networks, Inc.
• Original Assignee: Mocana Corporation (DigiCert Incorporated)
• Inventors: BLAISDELL, James, VALLY, Jean-Max
• Granted Patent: US 8,812,868 B2
• Time in Patent Office: Days
• US Class Current: 713/189
• CPC Class Codes: G06F 21/52 during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: H04W 12/12 Detection or prevention of fraud
• CPC Class Codes: H04W 12/37 Managing security policies for mobile devices or for controlling mobile applications

Abstract

Given the volume of apps being developed and downloaded, performing operations to enable security for mobile devices, such as locating relevant classes and substituting different classes, can become very inefficient when done to a very high number of apps. In the invention, a device is enabled with an app security enforcement layer. The consumer can download unsecured apps and have the app execute on the phone in a secure manner, where potential data loss to the device, such as a smart phone or tablet, is minimized. To make the security wrapping process more efficient, an app template containing markers is created. This template is merged with data in an active user policy or is used to randomize or obfuscate the code to add more security. The process of security wrapping an app becomes more efficient.

Claims

1. A method of securing an app for execution on a device using a security program, the method comprising:

obtaining core object code of the app, wherein a digital signature is removed from the app;

substituting app object code with security program object code, thereby creating a security-wrapped app;

creating an app template;

preparing the security-wrapped app for execution on the device;

modifying the app template; and

re-signing the security-wrapped app with a new key,

wherein a centralized policy to control and secure access to data is implemented on the device.

2. A method as recited in claim 1 wherein the template has markers which are merged with content from a user policy.

3. A method as recited in claim 2 wherein modifying the app template further comprises using an active policy.

4. A method as recited in claim 1 wherein modifying the app template further comprises obfuscating the app object code to add randomness.

5. A method as recited in claim 1 wherein modifying the app template further comprises personalizing the app object code using an active user policy.

6. A method as recited in claim 1 further comprising decompiling the app using the security program thereby obtaining executable code.

7. A method as recited in claim 1 further comprising disassembling the app using the security program, thereby obtaining executable code.

8. A method as recited in claim 1 further comprising:

applying a security program to the app.

9. A method as recited in claim 1 wherein said obtaining core object code and substituting app object code is done before the app interacts with an operating system of the device.

10. A method as recited in claim 1 further comprising making a copy of the app.

11. A method as recited in claim 10 further comprising:

deleting an original app from the device.

12. A method as recited in claim 10 further comprising:

reverting to an original app if a malfunction occurs while securing the app on the device.

13. A method as recited in claim 1 further comprising:

applying security program object code to operating system object code, wherein the security program object code is derived from policies.

14. A method as recited in claim 1 further comprising:

changing an icon representing the app on a display of the device to show that the app is secured.

15. A method as recited in claim 1 further comprising:

wrapping the app with a security layer before downloading the app.

16. A method as recited in claim 1 wherein the security-wrapped app implements an app policy.

17. A method as recited in claim 1 wherein the app policy includes one or more of limiting app execution time on the device, limiting the total number of apps on the device;

and limiting where the app may execute.