IP Library Granted Patent US 12,223,037
Granted Patent B2
US 12,223,037 · App. 17/069,529 · Granted Feb 11, 2025

Systems and methods for context-based mitigation of computer security risks

Inventors: Robert M. Juncker (Farmington, MN); Christopher J. Goettl (Owatonna, MN)
Assignee: Ivanti, Inc.
G06F21/55G06F8/65G06F21/62H04L63/101H04L63/104H04L63/14H04L63/1433H04L63/1441H04L63/20H04W12/12H04W12/126H04W12/128G06F2221/034G06F2221/2141
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,223,037
App. No.
17/069,529
Filed
Oct 13, 2020
Granted
Feb 11, 2025
Kind
B2
Examiner
DO, KHANG D
Art Unit
2492
USPC
726/25
Abstract

An apparatus includes a processor operatively coupled to a memory. The processor receives a first set of risk assessment rules including first user privilege criteria and first device criteria. The first device criteria include a computing device patch level, a network type, and/or a password policy. The processor identifies a user-specific security risk based on the first set of risk assessment rules and applies a privilege mitigation measure based on the user-specific security risk without being in communication with a management server. The processor later receives a second, updated set of risk assessment rules at the computing device. Upon detecting another login of the user, the processor identifies an updated user-specific security risk based on the updated set of risk assessment rules, and applies a modified privilege mitigation measure based on the updated user-specific security risk, again without being in communication with the management server.

Claims (91)

1. A method of context-based privilege mitigation, the method comprising:

detecting a login event of a user of a computing device;

receiving, by the computing device from a management server, a risk assessment rule that includes risk criteria and a plurality of privilege mitigation measures associated with the risk criteria, the risk assessment rule being communicated from the management server in response to the detection of the login event at the computing device, and the risk assessment rule indicates that a software application is vulnerable to an exploit;

evaluating, by an agent on the computing device, information on the computing device that is relevant to the risk criteria;

determining that the user has elevated privileges on the computing device;

detecting, by the computing device, a vulnerable software application to which the user has access, the vulnerable software application being flagged by the risk assessment rule;

identifying, by the computing device, a particular privilege mitigation measure of the plurality of privilege mitigation measures, wherein the particular privilege mitigation measure is mapped to the detected vulnerable software application; and

applying, by the computing device, the particular privilege mitigation measure on the computing device, the particular privilege mitigation measure including an action that reduces a user privilege level of the user and prevents software from being used on the computing device by the user until a desired update to the vulnerable software application has been installed.

2. The method of claim 1 , wherein the risk criteria include user privilege criteria, device criteria, and application criteria applicable to detection of the vulnerable software application.

3. The method of claim 2 , wherein:

the device criteria include at least one of:

a patch level of the computing device,

a network type of the computing device, or

a password policy; and

the particular privilege mitigation measure is associated with the user privilege criteria.

4. The method of claim 1 , wherein:

the risk criteria are a first risk criteria;

the login event is a first login event;

the vulnerable software application is a first security risk;

the action is a first action;

the particular privilege mitigation measure is a first privilege mitigation measure; and

the method further comprises:

receiving a second risk assessment rule including a second risk criteria and the plurality of privilege mitigation measures associated with the second risk criteria;

detecting a second login event of the user of the computing device;

determining a second security risk associated with the second login event based at least partially on the second risk criteria;

identifying a second privilege mitigation measure of the plurality of privilege mitigation measures, wherein the second privilege mitigation measure is mapped to the second security risk based on the second risk criteria and the second privilege mitigation measure includes a second action to decrease the second security risk that is different from the first action; and

applying the second privilege mitigation measure on the computing device.

5. The method of claim 1 , further comprising receiving a second risk assessment rule in response to detection of a new vulnerability associated with the computing device.

6. The method of claim 4 , wherein:

the second risk criteria include a network type of the computing device; and

the second privilege mitigation measure includes one or both of:

disabling network access for the user responsive to the network type of the computing device being a public network; and

sending an alert to the user responsive to the network type of the computing device being a public network that advises the user that the network is public.

7. The method of claim 4 , wherein the applying the second privilege mitigation measure includes:

patching;

privilege management;

whitelisting;

blacklisting;

automatically repairing a group policy associated with the user;

causing installation of an update on the computing device; or repairing user account settings associated with the user to comply with a group policy.

8. The method of claim 4 , wherein:

the computer device is in operable communication with a network, and

the identification of the second security risk is performed in response to:

a detected change in the network; or

a detected group policy violation.

9. A non-transitory computer-readable medium having encoded therein programming code executable by one or more processors to perform or control performance of operations of context-based privilege mitigation, the operations comprising:

detecting a login event of a user of a computing device;

receiving, by the computing device from a management server, a risk assessment rule that includes risk criteria and a plurality of privilege mitigation measures associated with the risk criteria, the risk assessment rule being communicated from the management server in response to the detection of the login event at the computing device, and the risk assessment rule indicates that a software application is vulnerable to an exploit;

evaluating, by an agent on the computing device, information on the computing device that is relevant to the risk criteria;

determining that the user has elevated privileges on the computing device;

detecting, by the computing device, a vulnerable software application to which the user has access, the vulnerable software application being flagged by the risk assessment rule;

identifying, by the computing device, a particular privilege mitigation measure of the plurality of privilege mitigation measures, wherein the particular privilege mitigation measure is mapped to the detected vulnerable software application; and

applying, by the computing device, the particular privilege mitigation measure on the computing device, the particular privilege mitigation measure including an action that reduces a user privilege level of the user and prevents software from being used on the computing device by the user until a desired update to the vulnerable software application has been installed.

10. The non-transitory computer-readable medium of claim 9 , wherein the risk criteria include user privilege criteria, device criteria, and application criteria applicable to detection of the vulnerable software application.

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

the device criteria include at least one of:

a patch level of the computing device,

a network type of the computing device, or

a password policy; and

the particular privilege mitigation measure is associated with the user privilege criteria.

12. The non-transitory computer-readable medium of claim 9 , wherein:

the risk criteria are a first risk criteria;

the login event is a first login event;

the vulnerable software application is a first security risk;

the action is a first action;

the particular privilege mitigation measure is a first privilege mitigation measure; and

the operations further comprise:

receiving a second risk assessment rule including a second risk criteria and the plurality of privilege mitigation measures associated with the second risk criteria;

detecting a second login event of the user of the computing device;

determining a second security risk associated with the second login event based at least partially on the second risk criteria;

identifying a second privilege mitigation measure of the plurality of privilege mitigation measures, wherein the second privilege mitigation measure is mapped to the second security risk based on the second risk criteria and the second privilege mitigation measure includes a second action to decrease the second security risk that is different from the first action; and

applying the second privilege mitigation measure on the computing device.

13. The non-transitory computer-readable medium of claim 9 , wherein the operations further comprise receiving a second risk assessment rule in response to detection of a new vulnerability associated with the computing device.

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

the second risk criteria include a network type of the computing device; and

the second privilege mitigation measure includes one or both of:

disabling network access for the user responsive to the network type of the computing device being a public network; and

sending an alert to the user responsive to the network type of the computing device being a public network that advises the user that the network is public.

15. The non-transitory computer-readable medium of claim 12 , wherein the applying the second privilege mitigation measure includes:

patching;

privilege management;

whitelisting;

blacklisting;

automatically repairing a group policy associated with the user;

causing installation of an update on the computing device; or

repairing user account settings associated with the user to comply with a group policy.

16. The non-transitory computer-readable medium of claim 12 , wherein:

the computer device is in operable communication with a network, and

the identification of the second security risk is performed in response to:

a detected change in the network; or

a detected group policy violation.

Assignments (8)
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY 14633493 WHICH WAS ENTERED INCORRECTLY AS 14633793 PREVIOUSLY RECORDED ON REEL 71176 FRAME 315. ASSIGNOR(S) HEREBY CONFIRMS THE FIRST LIEN NEWCO SECURITY AGREEMENT. Recorded Nov 10, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 073818/0515 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 16, 2025
From: IVANTI SECURITY HOLDINGS LLC
To: IVANTI, INC.
Reel/Frame 071958/0203 →
2025-1 SECOND LIEN SECURITY AGREEMENT Recorded May 5, 2025
From: IVANTI SECURITY INTERMEDIATE HOLDINGS LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 071176/0498 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 5, 2025
From: IVANTI, INC.
To: IVANTI SECURITY HOLDINGS LLC
Reel/Frame 071180/0690 →
PARTIAL RELEASE OF SECURITY INTERESTS Recorded May 5, 2025
From: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
To: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; CHERWELL SOFTWARE, LLC
Reel/Frame 071176/0289 →
FIRST LIEN NEWCO SECURITY AGREEMENT Recorded May 5, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 071176/0315 →
SECURITY INTEREST Recorded May 3, 2025
From: IVANTI SECURITY HOLDINGS LLC
To: ALTER DOMUS (US) LLC
Reel/Frame 071165/0164 →
RELEASE OF SECURITY INTEREST Recorded May 2, 2025
From: ALTER DOMUS (US) LLC
To: IVANTI SECURITY HOLDINGS LLC
Reel/Frame 071162/0130 →
Continuity (3)
Continuation 15906559 · Feb 27, 2018
Provisional Application 62464152 · Feb 27, 2017
Related Publication 20210150023A1 · May 20, 2021
References Cited (54)
US 6785810B1 · Lirov · 2004 [cited by examiner]
US 8321944B1 · Mayer · 2012 [cited by examiner]
US 8539546B2 · Kobayashi · 2013 [cited by examiner]
US 9185136B2 · Dulkin · 2015 [cited by examiner]
US 9282114B1 · Dotan · 2016 [cited by examiner]
US 9436820B1 · Gleichauf · 2016 [cited by examiner]
US 9703974B1 · Surkatty · 2017 [cited by examiner]
US 9798883B1 · Gil · 2017 [cited by examiner]
US 9830469B1 · Anderson · 2017 [cited by examiner]
US 9843934B1 · Jiang · 2017 [cited by examiner]
US 10404733B1 · Shavell · 2019 [cited by examiner]
US 10887325B1 · Lin · 2021 [cited by examiner]
US 20040078384A1 · Keir · 2004 [cited by examiner]
US 20040181689A1 · Kiyoto · 2004 [cited by examiner]
US 20060112007A1 · Hurwitz · 2006 [cited by examiner]
US 20070168311A1 · Genty · 2007 [cited by examiner]
US 20080307525A1 · Nickle · 2008 [cited by examiner]
US 20090249448A1 · Choi · 2009 [cited by examiner]
US 20100257580A1 · Zhao · 2010 [cited by applicant]
US 20110016513A1 · Bailey, Jr. · 2011 [cited by examiner]
US 20120192271A1 · Srivastava · 2012 [cited by examiner]
US 20120210434A1 · Curtis · 2012 [cited by examiner]
US 20130031629A1 · Srivastava · 2013 [cited by examiner]
US 20130067542A1 · Gonsalves · 2013 [cited by examiner]
US 20130074182A1 · Ikeda · 2013 [cited by examiner]
US 20130096980A1 · Basavapatna · 2013 [cited by examiner]
US 20140033321A1 · Patidar · 2014 [cited by examiner]
US 20140090071A1 · Salehie · 2014 [cited by examiner]
US 20140109168A1 · Ashley et al. · 2014 [cited by applicant]
US 20140359777A1 · Lam · 2014 [cited by examiner]
US 20150319185A1 · Kirti · 2015 [cited by examiner]
US 20150334129A1 · Moyle · 2015 [cited by examiner]
US 20150339477A1 · Abrams · 2015 [cited by examiner]
US 20160026813A1 · Neitzel · 2016 [cited by examiner]
US 20160112445A1 · Abramowitz · 2016 [cited by examiner]
US 20160226905A1 · Baikalov · 2016 [cited by examiner]
US 20160234229A1 · Carpenter · 2016 [cited by examiner]
US 20170070527A1 · Bailey · 2017 [cited by examiner]
US 20170078315A1 · Allen · 2017 [cited by examiner]
US 20170118223A1 · Mathew · 2017 [cited by examiner]
US 20170169249A1 · de Oliveira · 2017 [cited by examiner]
US 20170208023A1 · Katayama · 2017 [cited by examiner]
US 20170251013A1 · Kirti · 2017 [cited by examiner]
US 20170272472A1 · Adhar · 2017 [cited by examiner]
US 20170295197A1 · Parimi · 2017 [cited by examiner]
US 20170318036A1 · Movsisyan · 2017 [cited by examiner]
US 20170346846A1 · Findlay · 2017 [cited by examiner]
US 20180026944A1 · Phillips · 2018 [cited by examiner]
US 20180027006A1 · Zimmermann · 2018 [cited by examiner]
US 20180041540A1 · Tas · 2018 [cited by examiner]
US 20180091553A1 · Mandyam · 2018 [cited by examiner]
US 20180121665A1 · Anderson · 2018 [cited by examiner]
US 20180191766A1 · Holeman · 2018 [cited by examiner]
Federal Examination Report for Application No. 201917037863, dated Jan. 13, 2022, 5 pages. [cited by applicant]