IP Library Granted Patent US 12,299,116
Granted Patent B2
US 12,299,116 · App. 16/939,993 · Granted May 13, 2025

Threat mitigation system and method

Inventors: Brian P. Murphy (Tampa, FL); Joe Partlow (Tampa, FL); Colin O'Connor (Tampa, FL); Jason Pfeiffer (Tampa, FL); Brian Philip Murphy (St. Petersburg, FL)
Assignee: RELIAQUEST HOLDINGS, LLC
G06F21/554G06F3/04842G06N7/01G06N20/00H04L63/1416H04L63/1425H04L63/1433H04L63/1441G06F2221/034G06F2221/2115H04L2463/102
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,299,116
App. No.
16/939,993
Granted
May 13, 2025
Kind
B2
Abstract

A computer-implemented method, computer program product and computing system for: a computer-implemented method is executed on a computing device and includes: rendering a threat mitigation user interface that identifies objects within a computing platform in response to a security event; rendering an inspection window that defines object information concerning a selected object within the threat mitigation user interface; and enabling a third-party to effectuate a specific targeted action that is based, at least in part, upon the object information defined within the inspection window.

Claims (51)

1. A computer-implemented method, executed on a computing device, comprising:

rendering a threat mitigation user interface that identifies objects within a computing platform in response to a security event;

gathering one or more of the identified objects in response to the security event, wherein the one or more objects include one or more of a time-based traffic map object, a service splunk object, a service “CB Response” object, an outbound traffic by port graphical object, and a data sources graphical object;

rendering an inspection window of a graphical user interface that defines object information concerning a selected object within the threat mitigation user interface, wherein the inspection window is provided as a slide out inspection window within the graphical user interface; and

enabling a third-party to effectuate a specific targeted action that is based, at least in part, upon the object information defined within the inspection window, wherein enabling the third-part to effectuate a specific targeted action includes:

rendering an action list that defines one or more targeted actions that are based, at least in part, upon the object information defined within the inspection window; and

enabling the third-party to select the specific targeted action from the one or more targeted actions defined within the action list.

2. The computer-implemented method of claim 1 wherein the inspection window is a popup inspection window.

3. The computer-implemented method of claim 1 further comprising:

detecting the security event within the computing platform based upon identified suspect activity.

4. The computer-implemented method of claim 3 wherein detecting the security event within the computing platform based upon identified suspect activity includes:

monitoring a plurality of sources to identify suspect activity within the computing platform.

5. The computer-implemented method of claim 1 further comprising:

defining the objects within the computing platform in response to the security event.

6. The computer-implemented method of claim 5 wherein defining the objects within the computing platform in response to the security event includes:

gathering the objects within the computing platform in response to the security event from a plurality of sources associated with the computing platform.

7. The computer-implemented method of claim 1 further comprising defining the action list including actions that are based upon the object information defined within the inspection window.

8. A computer program product residing on a non-transitory computer readable medium having a plurality of instructions stored thereon which, when executed by a processor, cause the processor to perform operations comprising:

rendering a threat mitigation user interface that identifies objects within a computing platform in response to a security event;

gathering one or more of the identified objects in response to the security event, wherein the one or more objects include one or more of a time-based traffic map object, a service splunk object, a service “CB Response” object, an outbound traffic by port graphical object, and a data sources graphical object;

rendering an inspection window of a graphical user interface that defines object information concerning a selected object within the threat mitigation user interface, wherein the inspection window is provided as a slide out inspection window within the graphical user interface; and

enabling a third-party to effectuate a specific targeted action that is based, at least in part, upon the object information defined within the inspection window, wherein enabling the third-part to effectuate a specific targeted action includes:

rendering an action list that defines one or more targeted actions that are based, at least in part, upon the object information defined within the inspection window; and

enabling the third-party to select the specific targeted action from the one or more targeted actions defined within the action list.

9. The computer program product of claim 8 wherein the inspection window is a popup inspection window.

10. The computer program product of claim 8 further comprising:

detecting the security event within the computing platform based upon identified suspect activity.

11. The computer program product of claim 10 wherein detecting the security event within the computing platform based upon identified suspect activity includes:

monitoring a plurality of sources to identify suspect activity within the computing platform.

12. The computer program product of claim 8 further comprising:

defining the objects within the computing platform in response to the security event.

13. The computer program product of claim 12 wherein defining the objects within the computing platform in response to the security event includes:

gathering the objects within the computing platform in response to the security event from a plurality of sources associated with the computing platform.

14. The computer program product of claim 8 further comprising defining the action list including actions that are based upon the object information defined within the inspection window.

15. A computing system including a processor and memory configured to perform operations comprising:

rendering a threat mitigation user interface that identifies objects within a computing platform in response to a security event;

gathering one or more of the identified objects in response to the security event, wherein the one or more objects include one or more of a time-based traffic map object, a service splunk object, a service “CB Response” object, an outbound traffic by port graphical object, and a data sources graphical object;

rendering an inspection window of a graphical user interface that defines object information concerning a selected object within the threat mitigation user interface, wherein the inspection window is provided as a slide out inspection window within the graphical user interface; and

enabling a third-party to effectuate a specific targeted action that is based, at least in part, upon the object information defined within the inspection window, wherein enabling the third-part to effectuate a specific targeted action includes:

rendering an action list that defines one or more targeted actions that are based, at least in part, upon the object information defined within the inspection window; and

enabling the third-party to select the specific targeted action from the one or more targeted actions defined within the action list.

16. The computing system of claim 15 wherein the inspection window is a popup inspection window.

17. The computing system of claim 15 further comprising:

detecting the security event within the computing platform based upon identified suspect activity.

18. The computing system of claim 17 wherein detecting the security event within the computing platform based upon identified suspect activity includes:

monitoring a plurality of sources to identify suspect activity within the computing platform.

19. The computing system of claim 15 further comprising:

defining the objects within the computing platform in response to the security event.

20. The computing system of claim 19 wherein defining the objects within the computing platform in response to the security event includes:

gathering the objects within the computing platform in response to the security event from a plurality of sources associated with the computing platform.

21. The computing system of claim 15 further comprising defining the action list including actions that are based upon the object information defined within the inspection window.

Assignments (4)
RELEASE OF SECURITY INTEREST Recorded May 1, 2024
From: SIXTH STREET SPECIALTY LENDING, INC.
To: RELIAQUEST HOLDINGS, LLC
Reel/Frame 067277/0607 →
SECURITY INTEREST Recorded Apr 30, 2024
From: RELIAQUEST HOLDINGS, LLC
To: GOLUB CAPITAL LLC, AS COLLATERAL AGENT
Reel/Frame 067274/0381 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 18, 2022
From: MURPHY, BRIAN P.; PARTLOW, JOE; O'CONNOR, COLIN; PFEIFFER, JASON; MURPHY, BRIAN PHILIP
To: RELIAQUEST HOLDINGS, LLC
Reel/Frame 060842/0138 →
SECURITY INTEREST Recorded Oct 8, 2020
From: RELIAQUEST HOLDINGS, LLC
To: SIXTH STREET SPECIALTY LENDING, INC., AS COLLATERAL AGENT
Reel/Frame 054013/0548 →
Continuity (3)
Provisional Application 62883797 · Aug 7, 2019
Provisional Application 62879105 · Jul 26, 2019
Related Publication 20210029143A1 · Jan 28, 2021
References Cited (102)
US 1097205A · Ames · 1914 [cited by applicant]
US 8266544B1 · Kay et al. · 2012 [cited by applicant]
US 8966392B2 · Antony et al. · 2015 [cited by applicant]
US 9166995B1 · Roundy · 2015 [cited by applicant]
US 9384112B2 · Petersen et al. · 2016 [cited by applicant]
US 9516053B1 · Muddu et al. · 2016 [cited by applicant]
US 10237292B2 · Chauhan et al. · 2019 [cited by applicant]
US 10284587B1 · Schlatter et al. · 2019 [cited by applicant]
US 10298602B2 · Higbee et al. · 2019 [cited by applicant]
US 10567415B2 · Doppke et al. · 2020 [cited by applicant]
US 10574630B2 · Morris et al. · 2020 [cited by applicant]
US 10592938B2 · Hogg et al. · 2020 [cited by applicant]
US 10601778B2 · Fields et al. · 2020 [cited by applicant]
US 10728263B1 · Neumann · 2020 [cited by applicant]
US 10846434B1 · Ben-Zvi · 2020 [cited by examiner]
US 10972505B2 · Palumbo et al. · 2021 [cited by applicant]
US 11005870B2 · Yan · 2021 [cited by examiner]
US 11038915B1 · Friedrichs et al. · 2021 [cited by applicant]
US 11144853B1 · Waterman · 2021 [cited by examiner]
US 11182720B2 · Venna et al. · 2021 [cited by applicant]
US 11501184B1 · Mahadik et al. · 2022 [cited by applicant]
US 11636128B1 · Bigdelu et al. · 2023 [cited by applicant]
US 11921864B2 · Murphy et al. · 2024 [cited by applicant]
US 20040111507A1 · Villado et al. · 2004 [cited by applicant]
US 20040243802A1 · Jorba · 2004 [cited by examiner]
US 20050060567A1 · Shannon · 2005 [cited by examiner]
US 20100115617A1 · Weber et al. · 2010 [cited by applicant]
US 20100169476A1 · Chandrashekar · 2010 [cited by examiner]
US 20100186094A1 · Shannon · 2010 [cited by examiner]
US 20110118240A2 · Alig et al. · 2011 [cited by applicant]
US 20120084860A1 · Cao et al. · 2012 [cited by applicant]
US 20130174259A1 · Pearcy et al. · 2013 [cited by applicant]
US 20150207804A1 · Van et al. · 2015 [cited by applicant]
US 20150249676A1 · Koyanagi et al. · 2015 [cited by applicant]
US 20150304351A1 · Oberheide · 2015 [cited by examiner]
US 20150341389A1 · Kurakami · 2015 [cited by applicant]
US 20160127374A1 · O'Connell et al. · 2016 [cited by applicant]
US 20160164908A1 · Satish et al. · 2016 [cited by applicant]
US 20160241561A1 · Bubany et al. · 2016 [cited by applicant]
US 20160164907A1 · Satish et al. · 2016 [cited by applicant]
US 20160381063A1 · Oberheide · 2016 [cited by examiner]
US 20170034195A1 · Lee et al. · 2017 [cited by applicant]
US 20170118240A1 · Devi et al. · 2017 [cited by applicant]
US 20170279822A1 · Christopher et al. · 2017 [cited by applicant]
US 20170318051A1 · Stirtzinger et al. · 2017 [cited by applicant]
US 20180097822A1 · Huang et al. · 2018 [cited by applicant]
US 20180159893A1 · Satish et al. · 2018 [cited by applicant]
US 20180191781A1 · Palani et al. · 2018 [cited by applicant]
US 20180232521A1 · Jeansonne et al. · 2018 [cited by applicant]
US 20180248904A1 · Villella et al. · 2018 [cited by applicant]
US 20190109872A1 · Dhakshinamoorthy et al. · 2019 [cited by applicant]
US 20190124108A1 · Doyle · 2019 [cited by applicant]
US 20190132351A1 · Linde et al. · 2019 [cited by applicant]
US 20190158517A1 · Muddu · 2019 [cited by examiner]
US 20190166145A1 · Muddu et al. · 2019 [cited by applicant]
US 20190207962A1 · Wang · 2019 [cited by examiner]
US 20190245883A1 · Gorodissky · 2019 [cited by examiner]
US 20190260804A1 · Beck et al. · 2019 [cited by applicant]
US 20190318100A1 · Bhatia et al. · 2019 [cited by applicant]
US 20190377876A1 · Murphy et al. · 2019 [cited by applicant]
US 20190392152A1 · Patel et al. · 2019 [cited by applicant]
US 20200089848A1 · Abdelaziz et al. · 2020 [cited by applicant]
US 20200193018A1 · Van Dyke · 2020 [cited by applicant]
US 20200287793A1 · Buck et al. · 2020 [cited by applicant]
US 20200287941A1 · Venkateswaran et al. · 2020 [cited by applicant]
US 20210029159A1 · Murphy · 2021 [cited by examiner]
US 20210120014A1 · Argoety et al. · 2021 [cited by applicant]
US 20210250369A1 · Avist et al. · 2021 [cited by applicant]
US 20210329029A1 · Vasseur et al. · 2021 [cited by applicant]
US 20210374238A1 · Leung et al. · 2021 [cited by applicant]
US 20220164440A1 · Murphy · 2022 [cited by examiner]
US 20220180368A1 · Immaneni et al. · 2022 [cited by applicant]
US 20220277076A1 · Murphy et al. · 2022 [cited by applicant]
WO 2018216000A1 · 2018 [cited by applicant]
WO 2021021722A1 · 2021 [cited by applicant]
WO 2021021728A1 · 2021 [cited by applicant]
WO 2021021733A1 · 2021 [cited by applicant]
WO 2021021737A1 · 2021 [cited by applicant]
International Search Report and Written Opinion issued in related International Application No. PCT/US2020/043719 on Oct. 15, 2020; 15 pages. [cited by applicant]
International Search Report and Written Opinion issued in related International Application No. PCT/US2020/043726 on Oct. 15, 2020; 15 pages. [cited by applicant]
International Search Report and Written Opinion issued in related International Application No. PCT/US2020/043734 on Oct. 15, 2020; 17 pages. [cited by applicant]
International Search Report and Written Opinion issued in related International Application No. PCT/US2020/043741 on Oct. 15, 2020; 18 pages. [cited by applicant]
Final Office Action issued in U.S. Appl. No. 16/940,020 on Oct. 31, 2022. [cited by applicant]
Final Office Action issued in U.S. Appl. No. 16/939,973 on Sep. 22, 2022. [cited by applicant]
Final Office Acttion issued in U.S. Appl. No. 16/940,059 on Sep. 29, 2022. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 16/940,059 on Feb. 3, 2023. [cited by applicant]
Final Office Action issued in related U.S. Appl. No. 16/940,059 on Aug. 17, 2023. [cited by applicant]
Final Office Action issued in related U.S. Appl. No. 16/939,973 on Sep. 12, 2023. [cited by applicant]
Final Office Action issued in realated U.S. Appl. No. 16/940,020 on Oct. 18, 2023. [cited by applicant]
Notice of Allowance issued in related U.S. Appl. No. 16/940,020 on May 15, 2024. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 16/939,973 on May 30, 2024. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 16/939,973 on Feb. 17, 2023. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 16/940,020 on Mar. 17, 2023. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 16/940,059 on issue Date; Mar. 13, 2024. [cited by applicant]
Non-Final Office Action issued in U.S. Appl. No. 16/939,973 on Jun. 8, 2022. [cited by applicant]
Non-Final Office Action issued in U.S. Appl. No. 16/940,020 on Jul. 12, 2022. [cited by applicant]
Non-Final Office Action issued in U.S. Appl. No. 16/940,059 on Apr. 13, 2022. [cited by applicant]
Final Office Action issued in related U.S. Appl. No. 16/939,973 on Sep. 13, 2024. [cited by applicant]
Notice of Allowance issued in related U.S. Appl. No. 16/940,020 on Jul. 18, 2024. [cited by applicant]
Final Office Action issued in related U.S. Appl. No. 16/940,059 on Oct. 16, 2024. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 16/940,059 on Mar. 12, 2025. [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 16/939,973 on Mar. 26, 2025. [cited by applicant]