IP Library Granted Patent US 12,218,934
Granted Patent B2
US 12,218,934 · App. 18/885,474 · Granted Feb 4, 2025

Contextual and risk-based multi-factor authentication

Inventors: Jason Crabtree (Vienna, VA); Andrew Sellers (Monument, CO); Ian MacLeod (Arlington, VA)
Assignee: QOMPLX LLC
H04L63/0861H04L43/04H04L63/083H04L63/0876H04L63/105H04L63/1433H04L63/1408H04L2463/082
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,218,934
App. No.
18/885,474
Granted
Feb 4, 2025
Kind
B2
Abstract

A system for contextual and risk-based multi-factor authentication having a multi-dimensional time series data server configured to monitor and record a network's traffic data and to serve the traffic data to other modules and a directed computation graph module configured to receive network traffic data from the multi-dimensional time series data server, determine a network traffic baseline from the network traffic data, and determine a verification score needed before granting access based at least in part by the network traffic baseline. A plurality of verification methods build up a user's verification score to required level to gain access.

Claims (94)

1. A computer system configured to execute software instructions stored on nontransitory machine-readable storage media, wherein the software instructions comprise instructions that:

receive a request to authenticate a client, wherein the request comprises an identifier and a password,

store, in a multidimensional time-series database, information about the request,

determine whether the password corresponds to a user account identified by the identifier,

determine whether an additional verification is required to grant access,

wherein determining whether the additional verification is required to grant access comprises:

retrieving, from the multidimensional time-series database, historical information about previous access requests associated with the user account, and

determining, based at least on the historical information, whether the user account is associated with a previous access request to a network resource, wherein the previous access request to the network resource is anomalous relative to a baseline profile of access requests; and,

based on the additional verification being required to grant access:

select an additional verification method from a plurality of verification methods,

cause the client to be prompted to complete the additional verification method, and

determine whether the additional verification method has been completed correctly.

2. The computer system of claim 1 , wherein the historical information about previous access requests associated with the user account comprises historical information about previous requests to authenticate, wherein the previous requests to authenticate comprise the identifier.

3. The computer system of claim 1 , wherein determining whether the additional verification is required to grant access further comprises processing endpoint data from entities connected to the network.

4. The computer system of claim 1 , wherein determining whether the additional verification is required to grant access further comprises processing an external threat intelligence feed.

5. The computer system of claim 1 , wherein the software instructions further comprise instructions that:

based on the additional verification being required to grant access:

determine that a probable cyberattack is detected, and

provide an alert,

wherein the alert includes the identifier and an indicator that a probable cyberattack is detected, and

wherein the alert is designated to be provided to an administrator of the network.

6. The computer system of claim 5 , wherein the alert further includes an indication of where the probable cyberattack may have originated.

7. The computer system of claim 5 , wherein the alert further includes an indication of what enterprise information may be at risk in the probable cyberattack.

8. The computer system of claim 1 , wherein the software instructions further comprise instructions that:

deny the request based on determining that the user identification and the password are not associated with any user account, and

deny the request based on determining that the client failed to complete the additional verification method correctly.

9. The computer system of claim 1 , wherein the computer system comprises a plurality of physical computing machines.

10. The computer system of claim 1 , wherein the computer system comprises a plurality of virtual computing machines.

11. A method implemented on a computer system connected to a network, the method comprising:

receiving a request to authenticate a client, wherein the request comprises an identifier and a password,

storing, in a multidimensional time-series database, information about the request,

determining whether the password corresponds to a user account identified by the identifier,

determining whether an additional verification is required to grant access,

wherein determining whether the additional verification is required to grant access comprises:

retrieving, from the multidimensional time-series database, historical information about previous access requests associated with the user account,

determining, based at least on the historical information, whether the user account is associated with a previous access request to a network resource, wherein the previous access request to the network resource is anomalous relative to a baseline profile of access requests; and,

to require based on the additional verification being required to grant access:

selecting an additional verification method from a plurality of verification methods, causing the client to be prompted to complete the additional verification method, and determining whether the additional verification method has been completed correctly.

12. The method of claim 11 , wherein the historical information about previous access requests associated with the user account comprises historical information about previous requests to authenticate, wherein the previous requests to authenticate comprise the identifier.

13. The method of claim 11 , wherein determining whether the additional verification is required to grant access further comprises processing endpoint data from entities connected to the network.

14. The method of claim 11 , wherein determining whether the additional verification is required to grant access further comprises processing an external threat intelligence feed.

15. The method of claim 11 , further comprising:

require based on the additional verification being required to grant access:

determining that a probable cyberattack is detected, and

delivering an alert,

wherein the alert includes the identifier and an indicator that a probable cyberattack is detected, and

wherein the alert is designated to be delivered to an administrator of the network.

16. The method of claim 15 , wherein the alert further includes an indication of where the probable cyberattack may have originated.

17. The method of claim 15 , wherein the alert further includes an indication of what enterprise information may be at risk in the probable cyberattack.

18. A computer system is configured to execute software instructions stored on nontransitory machine-readable storage media, wherein the software instructions comprise instructions that:

receive a request to authenticate a client, wherein the request comprises an identifier and a password,

store, in a multidimensional time-series database, information about the request,

determine whether the password corresponds to a user account identified by the identifier,

determine whether an additional verification is required to grant access,

wherein determining whether the additional verification is required to grant access comprises:

retrieving, from the multidimensional time-series database, historical information about previous access requests associated with the user account, and

determining, based at least on the historical information, whether the user account is associated with a plurality of requests to authenticate comprising a brute force attack; and,

based on the additional verification being required to grant access:

select an additional verification method from a plurality of verification methods,

cause the client to be prompted to complete the additional verification method, and

determine whether the additional verification method has been completed correctly.

19. The computer system of claim 18 , wherein determining whether the additional verification is required to grant access further comprises processing endpoint data from entities connected to the network.

20. The computer system of claim 18 wherein determining whether the additional verification is required to grant access further comprises processing an external threat intelligence feed.

21. The computer system of claim 18 , wherein the software instructions further comprise instructions that:

based on the additional verification being required to grant access:

determine that a probable cyberattack is detected, and

provide an alert,

wherein the alert includes the identifier and an indicator that a probable cyberattack is detected, and

wherein the alert is designated to be provided to an administrator of the network.

22. The computer system of claim 21 , wherein the alert further includes an indication of where the probable cyberattack may have originated.

23. The computer system of claim 21 , wherein the alert further includes an indication of what enterprise information may be at risk in the probable cyberattack.

24. The computer system of claim 18 , wherein the computer system comprises a plurality of physical computing machines.

25. The computer system of claim 18 , wherein the computer system comprises a plurality of virtual computing machines.

26. A method implemented on a computer system connected to a network, the method comprising:

receiving a request to authenticate a client, wherein the request comprises an identifier and a password,

storing, in a multidimensional time-series database, information about the request,

determining whether the password corresponds to a user account identified by the identifier,

determining whether an additional verification is required to grant access,

wherein determining whether the additional verification is required to grant access comprises:

retrieving, from the multidimensional time-series database, historical information about previous access requests associated with the user account, and

determining, based at least on the historical information, whether the user account is associated with a plurality of requests to authenticate comprising a brute force attack; and,

based on the additional verification being required to grant access:

selecting an additional verification method from a plurality of verification methods,

causing the client to be prompted to complete the additional verification method, and

determining whether the additional verification method has been completed correctly.

27. The method of claim 26 , wherein determining whether the additional verification is required to grant access further comprises processing endpoint data from entities connected to the network.

28. The method of claim 26 , wherein determining whether the additional verification is required to grant access further comprises processing an external threat intelligence feed.

29. The method of claim 26 , further comprising:

based on the additional verification being required to grant access:

determining that a probable cyberattack is detected, and

delivering an alert,

wherein the alert includes the identifier and an indicator that a probable cyberattack is detected, and

wherein the alert is designated to be delivered to an administrator of the network.

30. The method of claim 29 , wherein the alert further includes an indication of where the probable cyberattack may have originated.

Assignments (4)
CHANGE OF NAME Recorded Sep 28, 2024
From: QPX LLC
To: QOMPLX LLC
Reel/Frame 069070/0283 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2024
From: QOMPLX, INC.
To: QPX LLC
Reel/Frame 069053/0339 →
CHANGE OF NAME Recorded Sep 18, 2024
From: FRACTAL INDUSTRIES, INC.
To: QOMPLX, INC.
Reel/Frame 068989/0708 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 15, 2024
From: CRABTREE, JASON; SELLERS, ANDREW; MACLEOD, IAN
To: FRACTAL INDUSTRIES, INC.
Reel/Frame 068590/0982 →