IP Library Granted Patent US 11,886,232
Granted Patent B2
US 11,886,232 · App. 17/374,280 · Granted Jan 30, 2024

Providing a mobile communications device with access to a provider service conditioned upon a device security level determination

Inventors: Kevin Patrick Mahaffey (San Francisco, CA); John G. Hering (San Francisco, CA); James David Burgess (Alameda, CA); Brian James Buck (Livermore, CA); William Robinson (Brentwood, CA)
Assignee: LOOKOUT, INC.
G06F21/577G06F21/554H04L63/0227H04L63/123H04L63/1425H04L63/1433H04L63/166H04W12/02H04W12/12H04W12/67
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 11,886,232
App. No.
17/374,280
Granted
Jan 30, 2024
Kind
B2
Abstract

Methods and systems are provided for providing a mobile communications device with access to a provider with a plurality of security levels. The security state of the device varies according to severity levels of device security events. The mobile communications device generates data regarding security events and provides the data to the provider, which compares that security state to a policy associated with the provider. The mobile communications device is allowed to access to a provider service where the device's current security state meets or exceeds the security state required for the provider service.

Claims (119)

1. A method comprising:

sending, by a mobile communications device, a request for access to a service provider, the request being received by a software component executing on a server;

generating, by an application executing on the mobile communications device, event security data regarding security events on the mobile communications device, the event security data including event types and parameters associated with the security events, the parameters specifying a security threat detected in examined data; and

not receiving, by the mobile communications device, access to the service provider when the software component compares a current security state of the mobile communications device to a policy associated with the service provider and determines that the current security state of the mobile communications device does not meet a first minimum security state, or

receiving, by the mobile communications device, access to the service provider when the software component compares the current security state to the policy and determines that the current security state meets the first minimum security state, wherein:

i) the current security state of the mobile communications device was determined by the software component:

a. processing the generated event security data to determine severity levels for the security events, and

b. using the determined severity levels to assess the current security state of the mobile communications device;

ii) the first minimum security state is a security state of a device required for the device to be granted access to the service provider; and

iii) the first minimum security state was specified in the policy.

2. The method of claim 1 , wherein:

the request also requests access to a service provided by the service provider or requests a task be performed by the service provider;

the policy specifies a second minimum security state of the device required for access to the requested service or for access to the requested task to be granted to the device; and

receiving, by the mobile communications device, access to the service provider includes:

receiving access to the service provider, but not receiving access to the requested service or access to the requested task, when the comparison results in a determination that the current security state meets the required first minimum security state and does not meet the required second minimum security state; or

receiving access to the service provider, and receiving access to the requested service or to the requested task, when the comparison results in a determination that the current security state meets the required first minimum security state requirement and meets the required second minimum security state requirement.

3. The method of claim 2 , wherein the service provided by the service provider or the task to be performed by the service provider includes at least one of:

a service or task related to viewing data files;

a service or task related to editing data files;

a service or task related to sending data files;

a service or task related to uploading data files;

a service or task related to viewing only portions of certain data files;

a service or task related to checking an account balance;

a service or task related to viewing previous financial transactions; or

a service or task related to transferring funds.

4. The method of claim 1 , wherein the software component is a security component of the service provider and is tasked with receiving access requests intended for the service provider.

5. The method of claim 1 , wherein:

the software component is a security component that is not integrated into the service provider;

the software component is tasked with receiving access requests intended for the service provider before the access requests are received by the service provider; and

the software component prevents the access request from being received by the service provider when the current security state does not meet the required first minimum security state.

6. The method of claim 1 , wherein the current security state of the mobile communications device was determined by the software component further:

accessing a database containing security data received from the mobile communications device;

comparing the generated event security data to security data from the mobile communications device stored in the database; and

using the determined severity levels and the comparison of the generated event security data to the security data stored in the database to assess the current security state of the mobile communications device.

7. The method of claim 1 further comprising:

sending, by the mobile communications device, the generated event security data to the software component, the software component causing the received event security data to be stored in a database accessible to the software component.

8. The method of claim 1 , wherein using the determined severity levels to assess the current security state of the mobile communications device includes:

using the determined severity levels and at least one from the group of:

historical data for the state of the mobile communications device, and

security state information for the mobile communications device stored on the server;

to assess the current security state of the mobile communications device.

9. A non-transitory, computer-readable storage medium having stored thereon a plurality of instructions, which, when executed by a processor of a mobile communications device, cause the mobile communications device to:

send a request for access to a service provider, the request being received by a software component executing on a server;

generate event security data, by an application executing on the mobile communications device, regarding security events on the mobile communications device, the event security data including event types and parameters associated with the security events, the parameters specifying a security threat detected in examined data; and

not receive access to the service provider when the software component compares a current security state of the mobile communications device to a policy associated with the service provider and determines that the current security state of the mobile communications device does not meet a first minimum security state, or receive access to the service provider when the software component compares the current security state to the policy and determines that the current security state meets the first minimum security state, wherein:

i) the current security state of the mobile communications device was determined by the software component:

a. processing the generated event security data to determine severity levels for the security events, and

b. using the determined severity levels to assess the current security state of the mobile communications device;

ii) the first minimum security state is a security state of a device required for the device to be granted access to the service provider; and

iii) the first minimum security state was specified in the policy.

10. The computer-readable storage medium of claim 9 , wherein:

the request also requests access to a service provided by the service provider or requests a task be performed by the service provider;

the policy specifies a second minimum security state of the device required for access to the requested service or for access to the requested task to be granted to the device; and

the receive access to the service provider includes:

receiving access to the service provider, but not receiving access to the requested service or access to the requested task, when the comparison results in a determination that the current security state meets the required first minimum security state and does not meet the required second minimum security state; or

receiving access to the service provider, and receiving access to the requested service or to the requested task, when the comparison results in a determination that the current security state meets the required first minimum security state requirement and meets the required second minimum security state requirement.

11. The computer-readable storage medium of claim 10 , wherein the service provided by the service provider or the task to be performed by the service provider includes at least one of:

a service or task related to viewing data files;

a service or task related to editing data files;

a service or task related to sending data files;

a service or task related to uploading data files;

a service or task related to viewing only portions of certain data files;

a service or task related to checking an account balance;

a service or task related to viewing previous financial transactions; or

a service or task related to transferring funds.

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

the software component is a security component that is not integrated into the service provider;

the software component is tasked with receiving access requests intended for the service provider before the access requests are received by the service provider; and

the software component prevents the access request from being received by the service provider when the current security state does not meet the required first minimum security state.

13. The computer-readable storage medium of claim 9 , wherein the current security state of the mobile communications device was determined by the software component further:

accessing a database containing security data received from the mobile communications device;

comparing the generated event security data to security data from the mobile communications device stored in the database; and

using the determined severity levels and the comparison of the generated event security data to the security data stored in the database to assess the current security state of the mobile communications device.

14. The computer-readable storage medium of claim 9 further comprising instructions to:

send the generated event security data to the software component, the software component causing the received event security data to be stored in a database accessible to the software component.

15. The computer-readable storage medium of claim 9 , wherein the instructions to use the determined severity levels to assess the current security state of the mobile communications device include instructions to:

using the determined severity levels and at least one from the group of:

historical data for the state of the mobile communications device, and

security state information for the mobile communications device stored on the server;

to assess the current security state of the mobile communications device.

16. A system, comprising a mobile communications device with at least one processor and memory and instructions that when executed by the at least one processor cause the mobile communications device to:

send a request for access to a service provider, the request being received by a software component executing on a server;

generate event security data, by an application executing on the mobile communications device, regarding security events on the mobile communications device, the event security data including event types and parameters associated with the security events, the parameters specifying a security threat detected in examined data; and

not receive access to the service provider when the software component compares a current security state of the mobile communications device to a policy associated with the service provider and determines that the current security state of the mobile communications device does not meet a first minimum security state, or

receive access to the service provider when the software component compares the current security state to the policy and determines that the current security state meets the first minimum security state, wherein:

i) the current security state of the mobile communications device was determined by the software component:

a. processing the generated event security data to determine severity levels for the security events, and

b. using the determined severity levels to assess the current security state of the mobile communications device;

ii) the first minimum security state is a security state of a device required for the device to be granted access to the service provider; and

iii) the first minimum security state was specified in the policy.

17. The system of claim 16 , wherein:

the request also requests access to a service provided by the service provider or requests a task be performed by the service provider;

the policy specifies a second minimum security state of the device required for access to the requested service or for access to the requested task to be granted to the device; and

the receive access to the service provider includes:

receiving access to the service provider, but not receiving access to the requested service or access to the requested task, when the comparison results in a determination that the current security state meets the required first minimum security state and does not meet the required second minimum security state; or

receiving access to the service provider, and receiving access to the requested service or to the requested task, when the comparison results in a determination that the current security state meets the required first minimum security state requirement and meets the required second minimum security state requirement.

18. The system of claim 17 , wherein the service provided by the service provider or the task to be performed by the service provider includes at least one of:

a service or task related to viewing data files;

a service or task related to editing data files;

a service or task related to sending data files;

a service or task related to uploading data files;

a service or task related to viewing only portions of certain data files;

a service or task related to checking an account balance;

service or task related to viewing previous financial transactions; or

a service or task related to transferring funds.

19. The system of claim 16 , wherein:

the software component is a security component that is not integrated into the service provider;

the software component is tasked with receiving access requests intended for the service provider before the access requests are received by the service provider; and

the software component prevents the access request from being received by the service provider when the current security state does not meet the required first minimum security state.

20. The system of claim 16 , wherein the current security state of the mobile communications device was determined by the software component further:

accessing a database containing security data received from the mobile communications device;

comparing the generated event security data to security data from the mobile communications device stored in the database; and

using the determined severity levels and the comparison of the generated event security data to the security data stored in the database to assess the current security state of the mobile communications device.

21. The system of claim 16 further comprising instructions to:

send the generated event security data to the software component, the software component causing the received event security data to be stored in a database accessible to the software component.

22. The system of claim 16 , wherein the instructions to use the determined severity levels to assess the current security state of the mobile communications device include instructions to:

use the determined severity levels and at least one from the group of:

historical data for the state of the mobile communications device, and

security state information for the mobile communications device stored on the server, to assess the current security state of the mobile communications device.

Assignments (6)
SECURITY INTEREST Recorded Oct 7, 2025
From: LOOKOUT, INC.
To: MIDCAP FINANCIAL TRUST
Reel/Frame 073028/0189 →
SECURITY INTEREST Recorded Oct 2, 2025
From: LOOKOUT, INC.
To: CRESCENT COVE OPPORTUNITY LENDING, LLC, AS AGENT
Reel/Frame 072989/0675 →
SECURITY INTEREST Recorded Aug 10, 2024
From: LOOKOUT, INC.
To: MIDCAP FINANCIAL TRUST
Reel/Frame 068538/0177 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 12, 2023
From: MAHAFFEY, KEVIN PATRICK; BUCK, BRIAN JAMES; ROBINSON, WILLIAM; HERING, JOHN G.; BURGESS, JAMES DAVID; WYATT, TIMOTHY MICHEAL; GOLOMBEK, DAVID; RICHARDSON, DAVID LUKE; LINEBERRY, ANTHONY MCKAY; BARTON, KYLE; EVANS, DANIEL LEE; SALOMON, ARIEL; GRUBB, JONATHAN PANTERA; WOOTTON, BRUCE; STRAZZERE, TIMOTHY; SWAMI, YOGESH
To: LOOKOUT, INC.
Reel/Frame 064875/0518 →
RELEASE OF PATENT SECURITY INTEREST AT REEL 59909 AND FRAME 0764 Recorded Jun 2, 2023
From: ALTER DOMUS (US) LLC, AS ADMINISTRATIVE AGENT
To: LOOKOUT, INC.
Reel/Frame 063844/0638 →
SECURITY INTEREST Recorded May 9, 2022
From: LOOKOUT, INC.
To: ALTER DOMUS (US) LLC
Reel/Frame 059909/0764 →
Continuity (41)
Continuation 16670227 · Oct 31, 2019
Continuation 16443697 · Jun 17, 2019
Continuation 16443682 · Jun 17, 2019
Continuation 16000712 · Jun 5, 2018
Continuation 16000712 · Jun 5, 2018
Continuation 15687395 · Aug 25, 2017
Continuation 15393089 · Dec 28, 2016
Continuation 14973636 · Dec 17, 2015
Continuation In Part 14692669 · Apr 21, 2015
Continuation In Part 14688292 · Apr 16, 2015
Continuation In Part 14634115 · Feb 27, 2015
Continuation In Part 14611063 · Jan 30, 2015
Continuation In Part 14473917 · Aug 29, 2014
Continuation In Part 14455787 · Aug 8, 2014
Continuation In Part 14318450 · Jun 27, 2014
Continuation 14034320 · Sep 23, 2013
Continuation 13958434 · Aug 2, 2013
Continuation In Part 13896852 · May 17, 2013
Continuation 13790402 · Mar 8, 2013
Continuation 13742110 · Jan 15, 2013
Continuation 13741988 · Jan 15, 2013
Continuation 13689588 · Nov 29, 2012
Division 13484132 · May 30, 2012
Continuation In Part 13335779 · Dec 22, 2011
Continuation 13333654 · Dec 21, 2011
Continuation 13314032 · Dec 7, 2011
Continuation 13267731 · Oct 6, 2011
Continuation 13033025 · Feb 23, 2011
Continuation 12868676 · Aug 25, 2010
Continuation In Part 12868669 · Aug 25, 2010
Continuation In Part 12868676 · Aug 25, 2010
Continuation 12868669 · Aug 25, 2010
Continuation In Part 12868672 · Aug 25, 2010
Continuation 12868672 · Aug 25, 2010
Continuation 12255621 · Oct 21, 2008
Continuation In Part 12255621 · Oct 21, 2008
Continuation In Part 12255621 · Oct 21, 2008
Continuation 12255632 · Oct 21, 2008
Continuation In Part 12255621 · Oct 21, 2008
Continuation 12255635 · Oct 21, 2008
Related Publication 20210342452A1 · Nov 4, 2021
Cited By (4)
US 12,244,611 US 12,309,152 US 12,488,153 US 12,585,795