IP Library Granted Patent US 10,848,563
Granted Patent B2
US 10,848,563 · App. 16/133,159 · Granted Nov 24, 2020

On-device, application-specific compliance enforcement

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,848,563
App. No.
16/133,159
Granted
Nov 24, 2020
Kind
B2
Abstract

Examples herein describe systems and methods for on-device, application-specific compliance enforcement. An example method can include receiving, at a user device, an application having a compliance engine. The user device can also store a compliance rule that applies to the received application. The compliance rule can specify a condition and a remedial action for the application. The user device can execute the application. The application can determine, using the compliance engine within the application, whether the condition is present. The determination can be made regardless of whether the device has internet or cellular connectivity. Based on determining that the condition is present, the application can perform the remedial action.

Claims (68)

1. A method for compliance enforcement, comprising:

storing, at a memory store of a user device, a first compliance rule that applies to a first application and specifies a first condition and a first remedial action to be performed by the first application;

storing, at the memory store of the user device, a second compliance rule that applies to a second application and specifies a second condition and a second remedial action to be performed by the second application;

checking in with a management server within a predetermined period of time;

retrieving from the management server an updated first compliance rule that applies to the first application and specifies the first condition and an updated first remedial action to be performed by the first application;

storing the updated first compliance rule at the memory store of the user device;

determining, by a first compliance engine of the first application, whether the first condition is present;

based on determining that the first condition is present, performing the updated first remedial action by the first application;

determining, by a second compliance engine of the second application, whether the second condition is present;

based on determining that the second condition is present, performing the second remedial action by the second application;

receiving escalation instructions from a management server, the escalation instructions causing the user device to:

perform an escalation action that causes the first condition to no longer be present at the user device; and

reverse the updated first remedial action.

2. The method of claim 1 , wherein the first and second compliance engines are based on the same software-development kit (“SDK”).

3. The method of claim 1 , wherein at least one of the first condition, the second condition, the updated first remedial action, and the second remedial action can be assigned to at least one of the first and second compliance engines using a graphical user interface (“GUI”) remote from the user device.

4. The method of claim 1 , wherein:

the first condition and second condition are the same, and

the updated first remedial action and second remedial action are different.

5. The method of claim 1 , wherein the first application is at least one of an email application and a file-sharing application.

6. The method of claim 1 , wherein the user device is not enrolled with a device-management system.

7. The method of claim 1 , wherein:

the updated first remedial action limits functionality of the first application, and

the second remedial action limits functionality of the second application.

8. A non-transitory, computer-readable medium comprising instructions that, when executed by a processor of a user device, perform stages for performing compliance enforcement, the stages comprising:

storing, at the user device, a first compliance rule that applies to a first application and specifies a first condition and a first remedial action to be performed by the first application;

storing, at the user device, a second compliance rule that applies to a second application and specifies a second condition and a second remedial action to be performed by the second application;

checking in with a management server within a predetermined period of time;

retrieving from the management server an updated first compliance rule that applies to the first application and specifies the first condition and an updated first remedial action to be performed by the first application;

storing the updated first compliance rule at the memory store of the user device;

determining, by a first compliance engine of the first application, whether the first condition is present;

based on determining that the first condition is present, performing the updated first remedial action by the first application;

determining, by a second compliance engine of the second application, whether the second condition is present;

based on determining that the second condition is present, performing the second remedial action by the second application;

receiving escalation instructions from a management server, the escalation instructions causing the user device to:

perform an escalation action that causes the first condition to no longer be present at the user device; and

reverse the updated first remedial action.

9. The non-transitory, computer-readable medium of claim 8 , wherein the first and second compliance engines are based on the same software-development kit (“SDK”).

10. The non-transitory, computer-readable medium of claim 8 , wherein at least one of the first condition, the second condition, the updated first remedial action, and the second remedial action can be assigned to at least one of the first and second compliance engines using a graphical user interface (“GUI”) remote from the user device.

11. The non-transitory, computer-readable medium of claim 8 , wherein:

the first condition and second condition are the same, and

the updated first remedial action and second remedial action are different.

12. The non-transitory, computer-readable medium of claim 8 , wherein the first application is at least one of an email application and a file-sharing application.

13. The non-transitory, computer-readable medium of claim 8 , wherein the user device is not enrolled with a device-management system.

14. The non-transitory, computer-readable medium of claim 13 , wherein:

the updated first remedial action limits functionality of the first application, and

the second remedial action limits functionality of the second application.

15. A system for performing compliance enforcement, comprising:

a user device having a processor and memory storage;

wherein the memory storage contains a non-transitory, computer-readable medium comprising instructions that, when executed by the processor, carry out stages comprising:

storing, at a memory store of a user device, a first compliance rule that applies to a first application and specifies a first condition and a first remedial action to be performed by the first application;

storing, at the memory store of the user device, a second compliance rule that applies to a second application and specifies a second condition and a second remedial action to be performed by the second application;

checking in with a management server within a predetermined period of time;

retrieving from the management server an updated first compliance rule that applies to the first application and specifies the first condition and an updated first remedial action to be performed by the first application;

storing the updated first compliance rule at the memory store of the user device;

determining, by a first compliance engine of the first application, whether the first condition is present;

based on determining that the first condition is present, performing the updated first remedial action by the first application;

determining, by a second compliance engine of the second application, whether the second condition is present;

based on determining that the second condition is present, performing the second remedial action by the second application;

receiving escalation instructions from a management server, the escalation instructions causing the user device to:

perform an escalation action that causes the first condition to no longer be present at the user device; and

reverse the updated first remedial action.

16. The system of claim 15 , wherein the first and second compliance engines are based on the same software-development kit (“SDK”).

17. The system of claim 15 , wherein at least one of the first condition, the second condition, the updated first remedial action, and the second remedial action can be assigned to at least one of the first and second compliance engines using a graphical user interface (“GUI”) remote from the user device.

18. The system of claim 15 , wherein:

the first condition and second condition are the same, and

the updated first remedial action and second remedial action are different.

19. The system of claim 15 , wherein the first application is at least one of an email application and a file-sharing application.

20. The system of claim 15 , wherein the user device is not enrolled with a device-management system.

Assignments (4)
PATENT ASSIGNMENT Recorded Aug 5, 2024
From: VMWARE LLC
To: OMNISSA, LLC
Reel/Frame 068327/0365 →
SECURITY INTEREST Recorded Jul 3, 2024
From: OMNISSA, LLC
To: UBS AG, STAMFORD BRANCH
Reel/Frame 068118/0004 →
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067103/0030 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 17, 2018
From: MEHTA, NIKHIL; SATAGOPAN, SANJAY; TURNER, RYAN; MOHSIN, ALI; BROOKS, SIMON; CHEN, LUCAS
To: VMWARE, INC.
Reel/Frame 046891/0397 →