IP Library Granted Patent US 12,301,613
Granted Patent B1
US 12,301,613 · App. 18/800,553 · Granted May 13, 2025

Computer-based systems configured for network characterization and management based on automated key terrain identification and methods of use thereof

Inventors: Vaibhav Anand (Chicago, IL); Charles Joseph Bonfield (Raleigh, NC); Jae Gook Ro (Chantilly, VA); Brandon Lee Knight (South Lake Tahoe, CA); Sarthak Sahu (Pasadena, CA); Ciro Donalek (Pasadena, CA); Michael Amori (Pasadena, CA)
Assignee: Virtualitics, Inc.
H04L63/1433H04L63/1408
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,301,613
App. No.
18/800,553
Granted
May 13, 2025
Kind
B1
Abstract

A method includes scanning a network having a first and second host, obtaining, via the scanning, a first and second type information of the first and second host, respectively, the first or second type information including a device category the first or second host belongs to, obtaining, via the scanning, a first and second scaling factor of the first and second host, respectively, calculating, a first criticality score of the first host based on the first type information and the first scaling factor, calculating a second criticality score of the second host based on the second type information and the second scaling factor, and facilitating to apply a security patch on the first host prior to the second host when the first criticality score is higher than the second criticality score.

Claims (65)

1. A computer-implemented method comprising:

scanning, by a computing device, a network having at least a first and second host;

obtaining, by the computing device via the scanning, a first type information of the first host, and second type information of the second host, the first type information comprising a first device category associated with the first host, the second type information comprising a second device category associated with the second host, wherein the first or second type information comprise a criticality range with a minimum and maximum value for each device category;

obtaining, by the computing device via the scanning, a first scaling factor of the first host, and a second scaling factor of the second host, wherein the first scaling factor or the second scaling factor is determined based on one or more of a plurality of component-specific scaling functions, comprising:

a first component-specific scaling function associated with a number of services running on the respective host,

a second component-specific scaling function associated with a functionality of the respective host, and

a third component-specific scaling function associated with a use case of the respective host;

calculating, by the computing device, a first criticality score of the first host based on the first type information and the first scaling factor, wherein the first criticality score is a product of multiplying the first type information and the first scaling factor;

calculating, by the computing device, a second criticality score of the second host based on the second type information and the second scaling factor, wherein the second criticality score is a product of multiplying the second type information and the second scaling factor; and

facilitating, by the computing device, to apply a security patch on the first host prior to the second host when the first criticality score is higher than the second criticality score.

2. The method of claim 1 , wherein the first or second device category is one of workstation, router, server, printer, camera or a combination thereof.

3. The method of claim 1 , wherein the minimum value for the device category of the first or second host is determined by a machine learning model.

4. The method of claim 1 , wherein calculating the first or second criticality score comprises using, as a multiplication factor, the minimum value for the device category of the first or second type information.

5. The method of claim 1 , wherein the functionality of the first or second host is identified based on a network map.

6. The method of claim 1 , wherein the functionality of the first or second host is inferred by network traffic and interactions.

7. The method of claim 1 , wherein the use case of the first or second host is determined by a location of the respective host.

8. The method of claim 1 , wherein the network scanning and calculating the criticality scores are conducted repeatedly at a predetermined frequency.

9. A computer-implemented method comprising:

scanning, by a computing device, a network having at least a first and second host;

obtaining, by the computing device via the scanning, a first type information of the first host, and second type information of the second host, the first type information comprising a first device category associated with the first host, the second type information comprising a second device category associated with the second host, wherein the first or second type information comprise a criticality range with a minimum and maximum value for each device category;

obtaining, by the computing device via the scanning, a first scaling factor of the first host, and a second scaling factor of the second host, wherein the first scaling factor or the second scaling factor is determined based on one or more of a plurality of component-specific scaling functions, comprising:

a first component-specific scaling function associated with a number of services running on the respective host,

a second component-specific scaling function associated with a functionality of the respective host, and

a third component-specific scaling function associated with a use case of the respective host;

calculating, by the computing device, a first criticality score of the first host by multiplying the first type information and the first scaling factor, wherein the first criticality score is a product of multiplying the first type information and the first scaling factor;

calculating, by the computing device, a second criticality score of the second host by multiplying the second type information and the second scaling factor, wherein the second criticality score is a product of multiplying the second type information and the second scaling factor; and

facilitating, by the computing device, to apply a security patch on the first host prior to the second host when the first criticality score is higher than the second criticality score.

10. The method of claim 9 , wherein the first or second device category is one of workstation, router, server, printer, camera or a combination thereof.

11. The method of claim 9 , wherein the minimum value for the device category of the first or second host is determined by a machine learning model.

12. The method of claim 9 , wherein calculating the first or second criticality score comprises using, as a multiplication factor, the minimum value for the device category of the first or second type information.

13. The method of claim 9 , wherein the functionality of the first or second host is identified based on a network map.

14. The method of claim 9 , wherein the functionality of the first or second host is inferred by network traffic and interactions.

15. The method of claim 9 , wherein the use case of the first or second host is determined by a location of the first or second host.

16. The method of claim 9 , wherein the network scanning and calculating the criticality scores are conducted repeatedly at a predetermined frequency.

17. A system, comprising:

one or more processors; and

a memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, cause the one or more processors to:

scan a network having at least a first and second host;

obtain, via the scanning, a first type information of the first host, and second type information of the second host, the first type information comprising a first device category associated with the first host, the second type information comprising a second device category associated with the second host, wherein the first or second type information comprise a criticality range with a minimum and maximum value for each device category;

obtain, via the scanning, a first and second scaling factor of the first and second host, respectively, wherein the first scaling factor or the second scaling factor is determined based on one or more of a plurality of component-specific scaling functions, comprising:

a first component-specific scaling function associated with a number of services running on the respective host,

a second component-specific scaling function associated with a functionality of the respective host, and

a third component-specific scaling function associated with a use case of the respective host;

calculate a first criticality score of the first host based the first type information and the first scaling factor, wherein the first criticality score is a product of multiplying the first type information;

calculate a second criticality score of the second host based on the second type information and the second scaling factor, wherein the second criticality score is a product of multiplying the second type information and the second scaling factor; and

facilitate to apply a security patch on the first host prior to the second host when the first criticality score is higher than the second criticality score.

18. The system of claim 17 , wherein the first or second device category is one of workstation, router, server, printer, camera or a combination thereof.

19. The system of claim 17 , wherein calculating the first or second criticality score comprises using, as a multiplication factor, the minimum value for the device category of the first or second type information.

20. The system of claim 17 , wherein the functionality of the first or second host is identified based on a network map.

21. The system of claim 17 , wherein the functionality of the first or second host is inferred by network traffic and interactions.

22. The system of claim 17 , wherein the use case of the first or second host is determined by a location of the respective host.

23. A system, comprising:

one or more processors; and

a memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, cause the one or more processors to:

scan a network having at least a first and second host;

obtain, via the scanning, a first type information of the first host, and second type information of the second host, the first type information comprising a first device category associated with the first host, the second type information comprising a second device category associated with the second host, wherein the first or second type information comprise a criticality range with a minimum and maximum value for each device category;

obtain, via the scanning, a first scaling factor of the first host, and a second scaling factor of the second host, wherein the first scaling factor or the second scaling factor is determined based on one or more of a plurality of component-specific scaling functions, comprising:

a first component-specific scaling function associated with a number of services running on the respective host,

a second component-specific scaling function associated with a functionality of the respective host, and

a third component-specific scaling function associated with a use case of the respective host;

calculate a first criticality score of the first host by multiplying the first type information and the first scaling factor;

calculate a second criticality score of the second host by multiplying the second type information and the second scaling factor; and

facilitate to apply a security patch on the first host prior to the second host when the first criticality score is higher than the second criticality score.

24. The system of claim 23 , wherein the first or second device category is one of workstation, router, server, printer, camera or a combination thereof.

25. The system of claim 23 , wherein the calculating the first or second criticality score comprises using, as a multiplication factor, the minimum value for the device category of the first or second type information.

Continuity (1)
Provisional Application 63649207 · May 17, 2024
References Cited (64)
US 8332947B1 · Bregman · 2012 [cited by examiner]
US 8555388B1 · Wang et al. · 2013 [cited by applicant]
US 9747570B1 · Vescio · 2017 [cited by applicant]
US 11528189B1 · Egri et al. · 2022 [cited by applicant]
US 11537706B1 · Sharifi Mehr · 2022 [cited by examiner]
US 11677773B2 · Iyer · 2023 [cited by examiner]
US 11734157B2 · Sahu et al. · 2023 [cited by applicant]
US 12113675B1 · Gupta · 2024 [cited by examiner]
US 20060272011A1 · Ide et al. · 2006 [cited by applicant]
US 20160352569A1 · Galliher, III et al. · 2016 [cited by applicant]
US 20170374094A1 · Agarmore · 2017 [cited by examiner]
US 20180124091A1 · Sweeney et al. · 2018 [cited by applicant]
US 20180324219A1 · Xie · 2018 [cited by examiner]
US 20180336353A1 · Manadhata · 2018 [cited by examiner]
US 20180351987A1 · Patel · 2018 [cited by examiner]
US 20190289029A1 · Chawla et al. · 2019 [cited by applicant]
US 20190296979A1 · Gupta et al. · 2019 [cited by applicant]
US 20200167705A1 · Risoldi · 2020 [cited by examiner]
US 20200311298A1 · Dunjic · 2020 [cited by examiner]
US 20200322369A1 · Raghuramu · 2020 [cited by examiner]
US 20200351294A1 · Davis · 2020 [cited by examiner]
US 20200412757A1 · Siddiq · 2020 [cited by applicant]
US 20210099475A1 · Eshghi · 2021 [cited by examiner]
US 20210173940A1 · Mylrea · 2021 [cited by examiner]
US 20210211450A1 · Aleidan · 2021 [cited by examiner]
US 20210211452A1 · Patel · 2021 [cited by examiner]
US 20210218765A1 · Rodriguez Bravo · 2021 [cited by examiner]
US 20210266340A1 · Grounds · 2021 [cited by examiner]
US 20210344713A1 · Kras et al. · 2021 [cited by applicant]
US 20220046045A1 · Rao et al. · 2022 [cited by applicant]
US 20220046048A1 · Koo et al. · 2022 [cited by applicant]
US 20220060509A1 · Crabtree et al. · 2022 [cited by applicant]
US 20220172211A1 · Muthuswamy · 2022 [cited by examiner]
US 20220191230A1 · Morgan · 2022 [cited by examiner]
US 20220263855A1 · Engelberg · 2022 [cited by examiner]
US 20220353169A1 · Balinzo · 2022 [cited by examiner]
US 20220400131A1 · Shao · 2022 [cited by examiner]
US 20230004655A1 · Poulin et al. · 2023 [cited by applicant]
US 20230042671A1 · Zaman · 2023 [cited by examiner]
US 20230047450A1 · Koo et al. · 2023 [cited by applicant]
US 20230208870A1 · Yellapragada et al. · 2023 [cited by applicant]
US 20230208871A1 · Yellapragada · 2023 [cited by examiner]
US 20230262093A1 · Gupta et al. · 2023 [cited by applicant]
US 20230300161A1 · Jenks · 2023 [cited by examiner]
US 20230334361A1 · Yamanaka · 2023 [cited by examiner]
US 20230336579A1 · Ellsworth · 2023 [cited by examiner]
US 20230336581A1 · Dunn · 2023 [cited by examiner]
US 20230412630A1 · Revankar · 2023 [cited by examiner]
US 20240007350A1 · Gupta · 2024 [cited by examiner]
US 20240095150A1 · Sahu et al. · 2024 [cited by applicant]
US 20240187439A1 · Sand · 2024 [cited by examiner]
US 20240323216A1 · Gershanov · 2024 [cited by examiner]
US 20240330815A1 · Subramaniam · 2024 [cited by examiner]
US 20240333683A1 · Šestan · 2024 [cited by examiner]
US 20240338455A1 · Madison, Jr. · 2024 [cited by examiner]
US 20240356960A1 · Griffin et al. · 2024 [cited by applicant]
CN 106790190A · 2017 [cited by applicant]
CN 107347074A · 2017 [cited by applicant]
CN 112291232A · 2021 [cited by applicant]
CN 116800548A · 2023 [cited by applicant]
EP 3220595A1 · 2017 [cited by applicant]
WO 2022125957A2 · 2022 [cited by applicant]
WO 2023021499A1 · 2023 [cited by applicant]
WO 2023064007A1 · 2023 [cited by applicant]
Cited By (1)
US 12,684,007