IP Library Granted Patent US 12,580,898
Granted Patent B2
US 12,580,898 · App. 18/361,825 · Granted Mar 17, 2026

Master ledger and local host log extension detection and mitigation of forged authentication attacks

Inventors: Jason Crabtree (Vienna, VA); Richard Kelley (Woodbridge, VA)
Assignee: QOMPLX LLC
H04L63/0428H04L9/002H04L9/3213H04L9/3236H04L9/3239H04L63/0807H04L63/0815H04L63/1425H04L63/1433H04L63/145H04L9/50
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,580,898
App. No.
18/361,825
Filed
Jul 29, 2023
Granted
Mar 17, 2026
Kind
B2
Art Unit
2497
USPC
713/180
Abstract

A system and method for implementation of zero trust computer network security combined with stateful authentication object tracking, authentication object manipulation and forgery detection, and assessment of authentication and identity attack surface. The methodology involves gathering all authentication objects issued by a network, storing the authentication objects in a master ledger for use in stateful deterministic authentication object tracking, and running detection functions that compare authentication objects presented for access to network resources with the master ledger. In an embodiment, an authentication object agent is installed at the domain controller level. In another embodiment, a log extension utility is installed at the local host computer level to provide additional log data for additional cyberattack detections.

Claims (59)

1 . A system for computer detection of forged authentication object cybersecurity attacks, comprising:

a computing device comprising a memory, a processor, and a non-volatile data storage device;

an authentication object master ledger stored on the non-volatile data storage device, the authentication object master ledger comprising authentication objects captured from one or more domain controllers of a computer network;

an authentication object agent installed on and operating on the one or more domain controllers of the computer network, the authentication object agent configured to capture each authentication object received by each of the domain controllers from a key distribution center and send it to an authentication object security system;

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

receive the authentication objects from the authentication object agent installed on and operating on the one or more domain controllers; and

store each received authentication object or a unique identifier associated with each authentication object in the authentication object master ledger;

receive a first authentication object presented to a first domain controller of the one or more domain controllers from a first authentication object agent installed on and operating on the first domain controller, the first authentication object being presented to the first domain controller for access to a resource of the computer network or a federated service associated with the computer network;

compare the first authentication object or a unique identifier associated with the first authentication object with the master ledger to determine whether an identical authentication object or unique identifier already exists in the master ledger; and

where the first authentication object or a unique identifier associated with the first authentication object is not contained in the master ledger, instruct the first authentication object agent to send a destroy ticket command from the first domain controller to the key distribution center.

2 . The system of claim 1 , wherein the computing device is part of the computer network.

3 . The system of claim 1 , wherein the computing device is part of a cloud-based service.

4 . The system of claim 1 , wherein the unique identifier stored for each received authentication object is a cryptographic hash of each authentication object, and the unique identifier for the first authentication object is a cryptographic hash of the first authentication object.

5 . The system of claim 1 , wherein the authentication objects are tickets issued by a ticket granting service of the key distribution center.

6 . The system of claim 1 , further comprising:

an authentication object log extension database stored on the non-volatile data storage device, the authentication object log extension database comprising additional log data for authentication objects issued by the key distribution center, the additional log data comprising a start time, an end time, and a renewal time for each authentication object issued by the key distribution center; and

the authentication object log extension utility installed on and operating on one or more local host computers of the computer network, the authentication object log extension utility configured to perform the following for the local host computer on which it is installed:

enumerate every logon session on the local host computer;

query the local ticket cache of the local host computer to obtain a log data stream for each logon session;

generate the additional log data to supplement the log data stream for each logon session; and

store the additional log data as part of the log data stream for the logon session;

wherein the authentication object security system is further configured to cause the computing device to:

receive the additional log data generated by the authentication object log extension utility for each local host computer of the one or more local host computers;

monitor access requests by a client operating on a first local host computer of the one or more local host computers for access to resources on the computer network;

identify a first authentication object presented by a first local host computer for access to a network resource of the computer network, the first authentication object comprising a client name;

retrieve a user session name from the first local host computer associated with the attempted access using the first authentication object;

compare the client name with the user session name; and

where there is a mismatch between the client name and user session name, send a destroy ticket command to the key distribution service.

7 . The system of claim 6 , wherein the computing device is the local host computer, and the authentication object security system is operating on the local host computer.

8 . The system of claim 6 , wherein the computing device is part of a cloud-based service.

9 . A method for computer detection of forged authentication object cybersecurity attacks, comprising the steps of:

storing an authentication object master ledger stored on a non-volatile data storage device of a computing device comprising a memory, a processor, and the non-volatile data storage device, the authentication object master ledger comprising authentication objects captured from one or more domain controllers of a computer network;

installing an authentication object agent on the one or more domain controllers of the computer network, the authentication object agent configured to capture each authentication object received by each of the domain controllers from a key distribution center and send it to an authentication object security system;

using the authentication object security system stored in the memory and operating on the processor of the computing device to:

receive the authentication objects from the authentication object agent installed on and operating on the one or more domain controllers; and

store each received authentication object or a unique identifier associated with each authentication object for each received authentication object in the authentication object master ledger;

receive a first authentication object presented to a first domain controller of the one or more domain controllers from a first authentication object agent installed on and operating on the first domain controller, the first authentication object being presented to the first domain controller for access to a resource of the computer network or a federated service associated with the computer network;

compare the first authentication object or a unique identifier associated with the first authentication object with the master ledger to determine whether an identical authentication object or unique identifier already exists in the master ledger; and

where the first authentication object or a unique identifier associated with the first authentication object is not contained in the master ledger, instruct the first authentication object agent to send a destroy ticket command from the first domain controller to the key distribution center.

10 . The method of claim 9 , wherein the computing device is part of the computer network.

11 . The method of claim 9 , wherein the computing device is part of a cloud-based service.

12 . The method of claim 9 , wherein the unique identifier stored for each received authentication object is a cryptographic hash of each authentication object, and the unique identifier for the first authentication object is a cryptographic hash of the first authentication object.

13 . The method of claim 9 , wherein the authentication objects are tickets issued by a ticket granting service of the key distribution center.

14 . The method of claim 9 , further comprising the steps of:

storing an authentication object log extension database on the non-volatile data storage device, the authentication object log extension database comprising additional log data for authentication objects issued by the key distribution center, the additional log data comprising a start time, an end time, and a renewal time for each authentication object issued by the key distribution center; and

installing the authentication object log extension utility installed on one or more local host computers of the computer network, the authentication object log extension utility configured to perform the following for the local host computer on which it is installed:

enumerate every logon session on the local host computer;

query the local ticket cache of the local host computer to obtain a log data stream for each logon session;

generate the additional log data to supplement the log data stream for each logon session; and

store the additional log data as part of the log data stream for the logon session;

wherein the authentication object security system is further configured to cause the computing device to:

receive the additional log data generated by the authentication object log extension utility for each local host computer of the one or more local host computers;

monitor access requests by a client operating on a first local host computer of the one or more local host computers for access to resources on the computer network;

identify a first authentication object presented by a first local host computer for access to a network resource of the computer network, the first authentication object comprising a client name;

retrieve a user session name from the first local host computer associated with the attempted access using the first authentication object;

compare the client name with the user session name; and

where there is a mismatch between the client name and user session name, send a destroy ticket command to the key distribution service.

15 . The method of claim 14 , wherein the computing device is the local host computer, and the authentication object security method is operating on the local host computer.

16 . The method of claim 14 , wherein the computing device is part of a cloud-based service.

Assignments (5)
CHANGE OF ADDRESS Recorded Oct 1, 2024
From: QOMPLX LLC
To: QOMPLX LLC
Reel/Frame 069083/0279 →
CORRECTIVE ASSIGNMENT TO CORRECT THE THE SECOND INVENTORS NAME PREVIOUSLY RECORDED AT REEL: 064427 FRAME: 0906. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Nov 27, 2023
From: CRABTREE, JASON; KELLEY, RICHARD
To: QOMPLX, INC.
Reel/Frame 065691/0075 →
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 →
Continuity (55)
Continuation In Part 18297500 · Apr 7, 2023
Continuation In Part 18169203 · Feb 14, 2023
Continuation In Part 17245162 · Apr 30, 2021
Continuation 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 14925974 · Oct 28, 2015
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 17986850 · Nov 14, 2022
Continuation In Part 17567060 · Dec 31, 2021
Continuation In Part 17389863 · Jul 30, 2021
Continuation 16792754 · Feb 17, 2020
Continuation In Part 16779801 · Feb 3, 2020
Continuation In Part 16777270 · Jan 30, 2020
Continuation In Part 16720383 · Dec 19, 2019
Continuation 15823363 · Nov 27, 2017
Continuation In Part 15725274 · Oct 4, 2017
Continuation In Part 17170288 · Feb 8, 2021
Continuation In Part 17169924 · Feb 8, 2021
Continuation In Part 15837845 · Dec 11, 2017
Continuation In Part 17102561 · Nov 24, 2020
Continuation In Part 15790457 · Oct 23, 2017
Continuation In Part 15790327 · Oct 23, 2017
Continuation In Part 15616427 · Jun 7, 2017
Continuation In Part 15141752 · Apr 28, 2016
Continuation In Part 17105025 · Nov 25, 2020
Continuation 16836717 · Mar 31, 2020
Continuation In Part 15887496 · Feb 2, 2018
Continuation In Part 15823285 · Nov 27, 2017
Continuation In Part 15788718 · Oct 19, 2017
Continuation In Part 15788002 · Oct 19, 2017
Continuation In Part 15787601 · Oct 18, 2017
Continuation In Part 15616427 · Jun 7, 2017
Continuation In Part 15818733 · Nov 20, 2017
Continuation In Part 15725274 · Oct 4, 2017
Continuation In Part 17683242 · Feb 28, 2022
Continuation In Part 16896764 · Jun 9, 2020
Continuation 16191054 · Nov 14, 2018
Continuation In Part 15655113 · Jul 20, 2017
Provisional Application 62596105 · Dec 7, 2017
Provisional Application 62568291 · Oct 4, 2017
Provisional Application 62568298 · Oct 4, 2017
Provisional Application 62568312 · Oct 4, 2017
Provisional Application 62568305 · Oct 4, 2017
Provisional Application 62568307 · Oct 4, 2017
Related Publication 20240022546A1 · Jan 18, 2024
References Cited (44)
US 5669000A · Jessen et al. · 1997 [cited by applicant]
US 6256544B1 · Weissinger · 2001 [cited by applicant]
US 6477572B1 · Elderton et al. · 2002 [cited by applicant]
US 8949960B2 · Berkman et al. · 2015 [cited by applicant]
US 10462112B1 · Makmel et al. · 2019 [cited by applicant]
US 11005824B2 · Crabtree et al. · 2021 [cited by applicant]
US 20030041254A1 · Challener et al. · 2003 [cited by applicant]
US 20030145225A1 · Bruton et al. · 2003 [cited by applicant]
US 20060224891A1 · Ilac · 2006 [cited by examiner]
US 20070036314A1 · Kloberdans et al. · 2007 [cited by applicant]
US 20070150744A1 · Cheng et al. · 2007 [cited by applicant]
US 20090182672A1 · Doyle · 2009 [cited by applicant]
US 20090199002A1 · Erickson · 2009 [cited by applicant]
US 20090222562A1 · Liu et al. · 2009 [cited by applicant]
US 20110087888A1 · Rennie · 2011 [cited by applicant]
US 20120266244A1 · Green et al. · 2012 [cited by applicant]
US 20140156806A1 · Karpistsenko et al. · 2014 [cited by applicant]
US 20140205099A1 · Christodorescu · 2014 [cited by examiner]
US 20140279762A1 · Xaypanya et al. · 2014 [cited by applicant]
US 20150149979A1 · Talby et al. · 2015 [cited by applicant]
US 20150169294A1 · Brock et al. · 2015 [cited by applicant]
US 20150195192A1 · Vasseur et al. · 2015 [cited by applicant]
US 20150281225A1 · Schoen et al. · 2015 [cited by applicant]
US 20150317481A1 · Gardner et al. · 2015 [cited by applicant]
US 20150379424A1 · Dirac et al. · 2015 [cited by applicant]
US 20160028758A1 · Ellis et al. · 2016 [cited by applicant]
US 20160072845A1 · Chiviendacz et al. · 2016 [cited by applicant]
US 20160078361A1 · Brueckner et al. · 2016 [cited by applicant]
US 20160275123A1 · Lin et al. · 2016 [cited by applicant]
US 20160323280A1 · Sade · 2016 [cited by examiner]
US 20160364307A1 · Garg et al. · 2016 [cited by applicant]
US 20170019678A1 · Kim et al. · 2017 [cited by applicant]
US 20170126712A1 · Crabtree et al. · 2017 [cited by applicant]
US 20170139763A1 · Ellwein · 2017 [cited by applicant]
US 20170149802A1 · Huang et al. · 2017 [cited by applicant]
US 20170193110A1 · Crabtree et al. · 2017 [cited by applicant]
US 20170322959A1 · Tidwell et al. · 2017 [cited by applicant]
US 20170323089A1 · Duggal et al. · 2017 [cited by applicant]
US 20180300930A1 · Kennedy et al. · 2018 [cited by applicant]
US 20190082305A1 · Proctor · 2019 [cited by applicant]
US 20200235935A1 · Cerna, Jr. · 2020 [cited by applicant]
CN 105302532B · 2018 [cited by applicant]
WO 2014159150A1 · 2014 [cited by applicant]
WO 2017075543A1 · 2017 [cited by applicant]