IP Library Granted Patent US 11,570,209
Granted Patent B2
US 11,570,209 · App. 17/169,924 · Granted Jan 31, 2023

Detecting and mitigating attacks using forged authentication objects within a domain

Inventors: Jason Crabtree (Vienna, VA); Andrew Sellers (Monument, CO)
Assignee: QOMPLX, INC.
H04L63/1466H04L9/0643H04L63/1416H04L63/1425
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,570,209
App. No.
17/169,924
Granted
Jan 31, 2023
Kind
B2
Abstract

A system for detecting and mitigating attacks using forged authentication objects within a domain is provided, comprising an authentication object inspector configured to observe a new authentication object generated by an identity provider, and retrieve the new authentication object; and a hashing engine configured to retrieve the new authentication object from the authentication object inspector, calculate a cryptographic hash for the new authentication object, and store the cryptographic hash for the new authentication object in a data store; wherein subsequent access requests accompanied by authentication objects are validated by comparing hashes for each authentication object to previous generated hashes.

Claims (33)

1. A system for detecting and mitigating attacks using forged authentication objects within a domain, comprising:

a computing device comprising a memory and a processor;

an authentication object inspector comprising a first plurality of programming instructions stored in the memory which, when operating on the processor, causes the computing device to:

receive network traffic comprising a plurality of network packets, the plurality of network packets comprising a plurality of first authentication objects known to be generated by an identity provider associated with an authentication domain;

store a record of each received first authentication object, with attached metadata comprising a timestamp of when each first authentication object was received, in a time-series database;

calculate a cryptographic hash of each first authentication object using a hashing engine;

store the cryptographic hash of each first authentication object in a database of hashes for the identity provider;

receive a request for access to a network resource associated with the authentication domain accompanied by a second authentication object;

calculate a cryptographic hash of the second authentication object using the hashing engine;

compare the cryptographic hash of the second authentication object with the cryptographic hashes of the first authentication objects stored in the database of hashes to determine whether the cryptographic hash of the second authentication object already exists in the database of hashes;

where the cryptographic hash of the second authentication object does not exist in the database of hashes, generate a notification that the identity provider may be compromised; and

the hashing engine comprising a second plurality of programming instructions stored in the memory which, when operating on the processor, causes the computing device to:

receive authentication objects from the authentication object inspector;

calculate cryptographic hashes for authentication objects received by performing a plurality of calculations and transformations on each authentication object received; and

return the cryptographic hashes of authentication objects received to the authentication object inspector.

2. The system of claim 1 , wherein the authentication object inspector is operated by the identity provider.

3. The system of claim 1 , wherein the authentication object inspector is operated by a client device communicating with the identity provider over a network.

4. A method for detecting and mitigating attacks using forged authentication objects within a domain, comprising the steps of:

using an authentication object inspector operating on a computing device comprising a memory and a processor to:

receive network traffic comprising a plurality of network packets, the plurality of network packets comprising at least a plurality of first authentication objects known to be generated by an identity provider associated with an authentication domain;

store a record of each received authentication object, with attached metadata comprising at least a timestamp of when the authentication object was received, in a time-series database;

calculate a cryptographic hash of each first authentication object using a hashing engine;

store the cryptographic hashes of the first authentication objects in a database of hashes for the identity provider;

receive a request for access to a network resource associated with the authentication domain accompanied by a second authentication object;

calculate a cryptographic hash of the second authentication object using the hashing engine;

compare the cryptographic hash of the second authentication object with the cryptographic hashes of the first authentication objects stored in the database of hashes to determine whether the cryptographic hash of the second authentication object already exists in the database;

where the cryptographic hash of the second authentication object does not exist in the database, generate a notification that the identity provider may be compromised; and

using the hashing engine operating on the computing device to:

receive authentication objects from the authentication object inspector;

calculate cryptographic hashes on authentication objects received by performing a plurality of calculations and transformations on each authentication object received; and

return the calculated cryptographic hashes to the authentication object inspector.

5. The method of claim 4 , wherein the authentication object inspector is operated by the identity provider.

6. The method of claim 4 , wherein the authentication object inspector is operated by a client device communicating with the identity provider over a network.

Assignments (5)
CHANGE OF ADDRESS Recorded Oct 1, 2024
From: QOMPLX LLC
To: QOMPLX LLC
Reel/Frame 069083/0279 →
CHANGE OF NAME Recorded Sep 27, 2023
From: QPX LLC
To: QOMPLX LLC
Reel/Frame 065036/0449 →
CORRECTIVE ASSIGNMENT TO CORRECT THE RECEIVING PARTY PREVIOUSLY RECORDED AT REEL: 064674 FRAME: 0408. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 20, 2023
From: QOMPLX, INC.
To: QPX LLC
Reel/Frame 064966/0863 →
PATENT ASSIGNMENT AGREEMENT TO ASSET PURCHASE AGREEMENT Recorded Aug 23, 2023
From: QOMPLX, INC.
To: QPX, LLC.
Reel/Frame 064674/0407 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 12, 2021
From: SELLERS, ANDREW; CRABTREE, JASON
To: QOMPLX, INC.
Reel/Frame 055241/0339 →
Continuity (16)
Continuation In Part 15837845 · Dec 11, 2017
Continuation In Part 15825350 · Nov 29, 2017
Continuation In Part 15725274 · Oct 4, 2017
Continuation In Part 15655113 · Jul 20, 2017
Continuation In Part 15616427 · Jun 7, 2017
Continuation In Part 15237625 · Aug 15, 2016
Continuation In Part 15206195 · Jul 8, 2016
Continuation In Part 15186453 · Jun 18, 2016
Continuation In Part 15166158 · May 26, 2016
Continuation In Part 15141752 · Apr 28, 2016
Continuation In Part 15091563 · Apr 5, 2016
Continuation In Part 14986536 · Dec 31, 2015
Continuation In Part 14925974 · Oct 28, 2015
Continuation In Part 14925974 · Oct 28, 2015
Provisional Application 62596105 · Dec 7, 2017
Related Publication 20210297447A1 · Sep 23, 2021
Cited By (7)
US 12,199,995 US 12,363,145 US 12,438,851 US 12,438,906 US 12,482,333 US 12,598,197 US 12,621,311