System and method for remote wipe

• US 10,171,501 B2
• Filed: 09/19/2014
• Issued: 01/01/2019
• Est. Priority Date: 09/20/2013
• Status: Active Grant

• Current Assignee: Ip Ot Sub Ulc
• Original Assignee: Open Text Sa Ulc (Open Text Corporation)
• Inventors: Beckman, Gregory, Laird, Robert, Gagne, Alain
• Primary Examiner(s): Pham, Luu T
• Assistant Examiner(s): Malinowski, Walter J
• Application Number:
  US14/491,492
• Publication Number:
  US 20150089659A1
• Time in Patent Office: 1,565 Days
• Field of Search: 726 1, 726 3, 726 26, 709217
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/16 Program or content traceability, e.g. by watermarking
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 2221/2143 Clearing memory, e.g. to prevent the data from being stolen
• CPC Class Codes: G06F 3/04817 using icons graphical or visual programming using iconic symbols G06F8/34
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 63/02 for separating internal from external traffic, e.g. firewalls
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/5683 Storage of data provided by user terminals, i.e. reverse caching
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A remote wipe message or notification may be sent from a server computer to one or more target client devices associated with a user. A managed container running on a target client device associated with the user and having a managed cache storing content managed by or through the server computer may, in response to the remote wipe message or notification, deleting the managed content or a portion thereof from its managed cache. The managed container may send back an acknowledgement or message to the server computer that it had completed the remote wipe. The remote wipe functionality can avoid having to deal with individual applications running on the client device and therefore can eliminate the complexity of having to deal with individual applications. Furthermore, the remote wipe can be done independently of the local operating system and without affecting non-managed information/applications on the client device.

Claims

1. A method comprising:

running, by a client device of an application gateway server computer, a managed container that the client device has downloaded from a network source, the managed container written in a programming language native to the client device and comprising a managed cache and an application framework, the application framework having an execution engine;

receiving, from the application gateway server computer by the managed container running on the client device, a client application for a backend system operating in an enterprise computing environment, wherein the application gateway server computer communicates with the backend system through a firewall of the enterprise computing environment;

storing, by the managed container running on the client device, the client application for the backend system in the managed cache of the managed container, wherein the storing further comprises;

storing, in the managed cache of the managed container, a plurality of client applications for a plurality of backend systems operating in the enterprise computing environment, the plurality of client applications received by the managed container from the application gateway server computer;

providing, by the execution engine of the managed container, a runtime environment for running the client application on the client device;

receiving, by the managed container running on the client device, a remote wipe message from the application gateway server computer over a network connection, the remote wipe message initiated at the application gateway server computer and specific to a user associated with the client device;

causing, by the managed container running on the client device and independently of a local operating system of the client device in response to the remote wipe message from the application gateway server computer, a low level destruction to content or a portion thereof within the managed cache of the managed container, the low level destruction to the managed cache caused by the managed container resulting in deletion of the client application for the backend system; and

sending, from the managed container to the application gateway server computer using an application programming interface of the application gateway server computer, an acknowledgement or message that the managed container had completed the remote wipe.

2. The method according to claim 1, wherein the receiving further comprises:

receiving, by the client device, the remote wipe message or a notification through a notification service provided by the application gateway server computer.

3. The method according to claim 1, wherein the network source resides on the Internet.

4. The method according to claim 1, further comprising:

initiating, by the application gateway server computer, the network connection via a request for connection from the application gateway server computer to the client device.

5. The method according to claim 1, further comprising:

tracking, by the application gateway server computer, information on one or more devices associated with the user.

6. The method according to claim 1, further comprising:

sending, by the application gateway server computer, the remote wipe message from the application gateway server computer to a managed container running on each client device of a plurality of client devices associated with the user, wherein, responsive to the remote wipe message from the application gateway server computer, the managed container running on each client device of the plurality of client devices associated with the user deleting the content or a portion thereof from its managed cache.

7. The method according to claim 1, further comprising:

maintaining a list of approved client devices;

determining that the client device is absent from the list of approved client devices; and

based on said determining, sending the remote wipe message to the managed container.

8. The method according to claim 1, wherein the content includes multiple versions of a document.

9. The method according to claim 1, wherein the content includes a document, the application gateway server sending the remote wipe message to the managed container in response to a record management operation relevant to the document and received from a backend system.

10. A system, comprising:

an application gateway server computer communicatively connected to backend systems running in an enterprise computing environment and to a client device of the application gateway server computer,

the backend systems residing behind a firewall of the enterprise computing environment,

the application gateway server computer residing in the enterprise computing environment outside of the firewall of the enterprise computing environment,

wherein the application gateway server computer communicates with the backend systems through the firewall of the enterprise computing environment; and

a managed container on the client device,

the managed container written in a programming language native to the client device and downloaded by the client device from a network source,

the managed container comprising a managed cache and an application framework, the application framework having an execution engine,

the managed container embodied on non-transitory computer memory including instructions executable by a processor of the client device for;

receiving, from the application gateway server computer, a client application for a backend system operating in the enterprise computing environment;

storing the client application for the backend system in the managed cache of the managed container, wherein the client application is one of a plurality of client applications for the backend systems that have been received by the managed container from the application gateway server computer and stored in the managed cache of the managed container;

providing, by the execution engine, a runtime environment for running the client application on the client device;

receiving a remote wipe message from the application gateway server computer over a network connection, the remote wipe message initiated at the application gateway server computer and specific to a user associated with the client device;

responsive to the remote wipe message from the application gateway server computer, causing, independently of a local operating system of the client device, a low level destruction to content or a portion thereof within the managed cache of the managed container, the low level destruction to the managed cache caused by the managed container resulting in deletion of the client application for the backend system; and

sending, to the application gateway server computer using an application programming interface of the application gateway server computer, an acknowledgement or message that the managed container had completed the remote wipe.

11. The system of claim 10, wherein the remote wipe message or a notification is received by the managed container through a notification service provided by the application gateway server computer.

12. The system of claim 10, wherein the managed container comprises a program downloaded to the client device from a source on the Internet.

13. The system of claim 10, wherein the application gateway server computer is configured to initiate the network connection with the client device.

14. The system of claim 10, wherein the application gateway server computer is configured to track information on one or more devices associated with the user.

15. The system of claim 10, wherein the client device is one of a plurality of client devices associated with the user, wherein the remote wipe message is sent from the application gateway server computer to a managed container running on each of the plurality of client devices associated with the user, and wherein, responsive to the remote wipe message from the application gateway server computer, the managed container running on each of the plurality of client devices associated with the user deleting the content or a portion thereof from its managed cache.

16. The system of claim 10, wherein the application gateway server computer maintains a list of approved client devices and wherein the application gateway server computer sends the remote wipe message to the managed container if the client device is absent from the list of approved client devices.

17. The system of claim 10, wherein the content includes multiple versions of a document.

18. The system of claim 10, wherein the content includes a document and wherein the application gateway server sends the remote wipe message to the managed container in response to a record management operation relevant to the document and received from a backend system.