IP Library Granted Patent US 12,494,932
Granted Patent B2
US 12,494,932 · App. 17/818,023 · Granted Dec 9, 2025

Generating contextual compliance policies

Inventors: Ravish Chawla (Chamblee, GA); Adam Samuel Chow (Atlanta, GA)
Assignee: Omnissa, LLC
H04L12/1831H04L12/1813H04L12/1818H04L51/224H04L63/0807H04L63/0815H04L63/20H04W12/06G06Q10/1093H04L63/10
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 12,494,932
App. No.
17/818,023
Granted
Dec 9, 2025
Kind
B2
Abstract

Examples of generating contextual compliance policies are described. A meeting invitation can be created by a meeting organizer. The meeting can have compliance rules associated therewith. A compliance policy that facilitates enforcement of the compliance rules during the meeting can be transmitted to attendee client devices and enforced by a management component running on the client devices.

Claims (48)

1 . A method for generating contextual compliance policies, comprising:

monitoring a mailbox of a compliance meeting object created in an enterprise directory on an email server and detecting that the compliance meeting object has been invited to a meeting;

in response to detecting that the compliance meeting object has been invited to the meeting, generating a message for at least one user associated with the meeting, the message requesting one or more restriction settings for a compliance policy to be applied to a client device associated with the meeting;

in response to the message, receiving the one or more restriction settings;

generating the compliance policy that alters a device functionality of the client device based on the received one or more restriction settings; and

transmitting the compliance policy to the client device, wherein a management component on the client device installs the compliance policy on the client device, the compliance policy being enforced during the meeting.

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

obtaining a rule set associated with the meeting from a message classification associated with the meeting, wherein the rule set is embedded within the message classification; and

generating the compliance policy based upon the rule set.

3 . The method according to claim 2 , wherein the rule set is specified by a meeting organizer in a response to creation of a meeting object in the email server that corresponds to the meeting, wherein the meeting object specifies at least one of a date, a start time, and an end time associated with the meeting.

4 . The method according to claim 2 , wherein the rule set is automatically generated based upon an identity of a meeting organizer or an identity of a user linked to the email account.

5 . The method according to claim 1 , further comprising causing an authentication token corresponding to a federated service to be revoked during the meeting, the authentication token associated with a user account linked to the email account, wherein the authentication token is revoked in response to detecting non-compliance with the compliance policy during the meeting.

6 . The method according to claim 5 , wherein the authentication token is associated with a physical access credential for a meeting room, wherein revoking the authentication token causes the physical access credential to be denied access to the meeting room.

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

obtaining a rule set associated with the meeting from a user interface generated in response to a link provided to a meeting organizer; and

generating the compliance policy based upon the rule set.

8 . A non-transitory computer-readable medium embodying program code executable by at least one computing device, the program code, when executed, causing the at least one computing device to at least:

monitor a mailbox of a compliance meeting object created in an enterprise directory on an email server and detect that the compliance meeting object has been invited to a meeting;

in response to detecting that the compliance meeting object has been invited to the meeting, generate a message for at least one user associated with the meeting, the message requesting one or more restriction settings for a compliance policy to be applied to a client device associated with the meeting;

in response to the message, receive the one or more restriction settings;

a generate the compliance policy that alters a device functionality of the client device based on the received one or more restriction settings; and

transmit the compliance policy to the client device, wherein a management component on the client device installs the compliance policy on the client device, the compliance policy being enforced during the meeting.

9 . The non-transitory computer-readable medium according to claim 8 , wherein the at least one computing device is further directed to at least:

obtain a rule set associated with the meeting from a message classification associated with the meeting, wherein the rule set is embedded within the message classification; and generate the compliance policy based upon the rule set.

10 . The non-transitory computer-readable medium according to claim 9 , wherein the rule set is specified by a meeting organizer in a response to creation of a meeting object in the email server that corresponds to the meeting, wherein the meeting object specifies at least one of a date, a start time, and an end time associated with the meeting.

11 . The non-transitory computer-readable medium according to claim 9 , wherein the rule set is automatically generated based upon an identity of a meeting organizer or an identity of a user linked to the email account.

12 . The non-transitory computer-readable medium according to claim 8 , wherein the program code further causes the at least one computing device to at least:

cause an authentication token corresponding to a federated service to be revoked during the meeting, the authentication token associated with a user account linked to the email account, wherein the authentication token is revoked in response to detecting non-compliance with the compliance policy during the meeting.

13 . The non-transitory computer-readable medium according to claim 12 , wherein the authentication token is associated with a physical access credential for a meeting room, wherein revoking the authentication token causes the physical access credential to be denied access to the meeting room.

14 . The non-transitory computer-readable medium according to claim 8 , wherein the program code causes the at least one computing device to at least:

obtain a rule set associated with the meeting from user interface generated in response to a link provided to a meeting organizer; and

generate the compliance policy based upon the rule set.

15 . A system for multi-persona enrollment management, comprising:

at least one computing device; and

at least one application executed by the at least one computing device, the at least one application, when executed, causing the at least one computing device to at least:

monitor a mailbox of a compliance meeting object created in an enterprise directory on an email server and detect that the compliance meeting object has been invited to a meeting;

in response to detecting that the compliance meeting object has been invited to the meeting, generate a message for at least one user associated with the meeting, the message requesting one or more restriction settings for a compliance policy to be applied to a client device associated with the meeting;

in response to the message, receive the one or more restriction settings;

generate the compliance policy that alters a device functionality of the client device based on the received one or more restriction settings; and

transmit the compliance policy to the client device, wherein a management component on the client device installs the compliance policy on the client device, the compliance policy being enforced during the meeting.

16 . The system according to claim 15 , wherein the at least one computing device is further configured to at least:

obtain a rule set associated with the meeting from a message classification associated with the meeting, wherein the rule set is embedded within the message classification; and

generate the compliance policy based upon the rule set.

17 . The system according to claim 16 , wherein the rule set is specified by a meeting organizer in a response to creation of a meeting object in the email server that corresponds to the meeting, wherein the meeting object specifies at least one of a date, a start time, and an end time associated with the meeting.

18 . The system according to claim 16 , wherein the rule set is automatically generated based upon an identity of a meeting organizer or an identity of a user linked to the email account.

19 . The system according to claim 15 , wherein the at least one application causes the at least one computing device to at least:

cause an authentication token corresponding to a federated service to be revoked during the meeting, the authentication token associated with a user account linked to the email account, wherein the authentication token is revoked in response to detecting non-compliance with the compliance policy during the meeting.

20 . The method of claim 1 , wherein the message is an auto-reply message to a meeting initiator generated in response to detecting that the compliance meeting object has been invited to the meeting by the meeting initiator.

Assignments (3)
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 067102/0242 →