IP Library › Granted Patent US 12,701,123
Granted Patent B2
US 12,701,123 · App. 17/655,140 · Granted Aug 4, 2026

Use of a trust score plan

Inventors: Charles Damian O'Neill (Ballymena, GB); Simon James (Newtownards, GB); Hayden Paul Shorter (Bangor, GB); Kieran Gerald McPeake (Belfast, GB)
Assignee: Hewlett Packard Enterprise Development LP
H04L63/1416H04L63/102H04L63/1425H04L63/20
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,701,123
App. No.
17/655,140
Granted
Aug 4, 2026
Kind
B2
Abstract

This disclosure describes techniques that include assessing trust in a system, and in particular, assessing trust for entities based on a trust score plan. In one example, this disclosure describes a method that includes identifying, by the computing system, a selected trust score plan from a plurality of trust score plans associated with a network entity in a computer network; storing, by a computing system, information collected about the network entity in the computer network; determining, by the computing system and based on the identified trust score plan and the stored information, a trust score for the network entity; and modifying, by the computing system and based on the trust score for the network entity, operations within the computer network.

Claims (56)

1 . A method comprising:

identifying, by a computing system, a first trust score plan associated with a first network device in a computer network;

identifying, by the computing system, a second trust score plan associated with a second network device in the computer network;

storing, by the computing system, information collected about the first network device and the second network device;

determining, by the computing system and based on the first trust score plan and the stored information, a first trust score for the first network device;

determining, by the computing system and based on the second trust score plan and the stored information, a second trust score for the second network device; and

modifying, by the computing system and based the second trust score not exceeding a threshold, traffic within the computer network to divert traffic away from the second network device.

2 . The method of claim 1 , wherein identifying the first trust score plan includes:

identifying the first trust score plan based on input.

3 . The method of claim 1 , wherein storing information collected about the first network device includes:

storing information received from a plurality of source services.

4 . The method of claim 1 , wherein determining the first trust score includes:

determining the first trust score in response to a trigger.

5 . The method of claim 4 , wherein the trigger is one of:

input, an event, or a periodic alarm.

6 . The method of claim 5 , wherein the trigger includes information about a context in which the trigger was initiated, and wherein identifying the first trust score plan includes:

identifying the first trust score plan based on the context.

7 . The method of claim 1 , further comprising:

enabling, by the computing system, modification of the first trust score plan to generate a modified first trust score plan.

8 . The method of claim 7 , further comprising:

determining, by the computing system and based on the modified first trust score plan and the stored information, a new trust score for the first network device; and

modifying, by the computing system and based on the new trust score for the first network device, operations within the computer network.

9 . The method of claim 1 , wherein determining the first trust score includes:

generating a trust score result that includes the first trust score and supporting information, wherein the supporting information enables reproduction of calculations underlying the first trust score.

10 . The method of claim 1 , wherein modifying traffic includes changing configurations to at least one of:

a router, a firewall, an access control system, an asset management system, or an alarm system.

11 . The method of claim 1 , wherein modifying traffic includes at least one of:

changing routing algorithms, limiting access to one or more network devices, marking one or more network devices as unavailable, or triggering an alarm.

12 . A system comprising processing circuitry and a storage device, wherein the processing circuitry has access to the storage device and is configured to:

identify a first trust score plan associated with a first network device in a computer network;

identify a second trust score plan associated with a second network device in the computer network;

store information collected about the first network device and the second network device;

determine, based on the first trust score plan and the stored information, a first trust score for the first network device;

determine, based on the second trust score plan and the stored information, a second trust score for the second network device; and

modify, based on the second trust score not exceeding a threshold, traffic within the computer network to divert traffic away from the second network device.

13 . The system of claim 12 , wherein to identify the first trust score plan, the processing circuitry is further configured to includes:

identify the first trust score plan based on input.

14 . The system of claim 12 , wherein to store information collected about the first network device, the processing circuitry is further configured to:

store information received from a plurality of source services within the computer network.

15 . The system of claim 12 , wherein to determine the first trust score, the processing circuitry is further configured to:

determine the first trust score in response to a trigger.

16 . The system of claim 15 , wherein the trigger is one of:

input, an event, or a periodic alarm.

17 . The system of claim 16 , wherein the trigger includes information about a context in which the trigger was initiated, and wherein to identify the first trust score plan, the processing circuitry is further configured to:

identify the first trust score plan based on the context.

18 . The system of claim 12 , wherein the processing circuitry is further configured to:

enable modification of the first trust score plan to generate a modified first trust score plan.

19 . The system of claim 12 , wherein to determine the first trust score, the processing circuitry is further configured to:

generate a trust score result that includes the first trust score and supporting information, wherein the supporting information enables reproduction of calculations underlying the first trust score.

20 . Non-transitory computer-readable media comprising instructions that, when executed, configure processing circuitry of a computing system to:

identify a first trust score plan associated with a first network device in a computer network;

identify a second trust score plan associated with a second network device in the computer network;

store information collected about the first network device and the second network device;

determine, based on the first trust score plan and the stored information, a first trust score for the first network device;

determine, based on the second trust score plan and the stored information, a second trust score for the second network device; and

modify, based on the second trust score not exceeding a threshold, traffic within the computer network to divert traffic away from the second network device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 16, 2022
From: O'NEILL, CHARLES DAMIAN; JAMES, SIMON; SHORTER, HAYDEN PAUL; MCPEAKE, KIERAN GERALD
To: JUNIPER NETWORKS, INC.
Reel/Frame 059286/0748 →
Continuity (1)
Related Publication 20230300150A1 · Sep 21, 2023
References Cited (170)
US 7558884B2 · Fuller et al. · 2009 [cited by applicant]
US 7788700B1 · Feezel et al. · 2010 [cited by applicant]
US 7895068B2 · LaSalle et al. · 2011 [cited by applicant]
US 7900259B2 · Jeschke et al. · 2011 [cited by applicant]
US 8205257B1 · Satish et al. · 2012 [cited by applicant]
US 8549622B2 · Byrne et al. · 2013 [cited by applicant]
US 8595282B2 · Nachenberg · 2013 [cited by applicant]
US 8776180B2 · Kumar et al. · 2014 [cited by applicant]
US 9363283B1 · Herrera-Yagiie et al. · 2016 [cited by applicant]
US 9679254B1 · Mawji et al. · 2017 [cited by applicant]
US 9769174B2 · Rieke et al. · 2017 [cited by applicant]
US 9860275B2 · Kleinpeter et al. · 2018 [cited by applicant]
US 9942259B2 · Madhu et al. · 2018 [cited by applicant]
US 10055466B2 · Trudel et al. · 2018 [cited by applicant]
US 10068095B1 · Segal et al. · 2018 [cited by applicant]
US 10225839B2 · Watts · 2019 [cited by applicant]
US 10237293B2 · Hajmasan et al. · 2019 [cited by applicant]
US 10432605B1 · Lester et al. · 2019 [cited by applicant]
US 10491594B2 · Yan · 2019 [cited by applicant]
US 10511510B2 · Ricci · 2019 [cited by applicant]
US 10855619B1 · Andrews et al. · 2020 [cited by applicant]
US 10855725B2 · Pai et al. · 2020 [cited by applicant]
US 10924377B2 · Chauhan · 2021 [cited by applicant]
US 10958673B1 · Chen et al. · 2021 [cited by applicant]
US 11038766B2 · Shen et al. · 2021 [cited by applicant]
US 11321464B2 · Govardhan · 2022 [cited by applicant]
US 11386129B2 · Chrapko et al. · 2022 [cited by applicant]
US 11503061B1 · Lin et al. · 2022 [cited by applicant]
US 11640569B2 · Chrapko · 2023 [cited by applicant]
US 11683331B2 · Grammel et al. · 2023 [cited by applicant]
US 11695558B2 · Ray et al. · 2023 [cited by applicant]
US 11863434B2 · Maino · 2024 [cited by examiner]
US 12074879B2 · O'Neill et al. · 2024 [cited by applicant]
US 12170670B2 · O'Neill et al. · 2024 [cited by applicant]
US 20050132229A1 · Zhang et al. · 2005 [cited by applicant]
US 20060212925A1 · Shull et al. · 2006 [cited by applicant]
US 20060248573A1 · Pannu et al. · 2006 [cited by applicant]
US 20070107059A1 · Chasin et al. · 2007 [cited by applicant]
US 20070147594A1 · Aaron et al. · 2007 [cited by applicant]
US 20090100504A1 · Conner et al. · 2009 [cited by applicant]
US 20090165116A1 · Morris · 2009 [cited by applicant]
US 20090172776A1 · Makagon et al. · 2009 [cited by applicant]
US 20100220613A1 · Hendriks et al. · 2010 [cited by applicant]
US 20110072508A1 · Agarwal · 2011 [cited by examiner]
US 20110280160A1 · Yang · 2011 [cited by applicant]
US 20130097317A1 · Sheleheda et al. · 2013 [cited by applicant]
US 20130138290A1 · Falkenstein · 2013 [cited by applicant]
US 20130249928A1 · Buhr et al. · 2013 [cited by applicant]
US 20130298192A1 · Kumar et al. · 2013 [cited by applicant]
US 20130298242A1 · Kumar et al. · 2013 [cited by applicant]
US 20130298244A1 · Kumar et al. · 2013 [cited by applicant]
US 20140164342A1 · Liapis · 2014 [cited by applicant]
US 20140259140A1 · Subramanian · 2014 [cited by applicant]
US 20140278879A1 · Gilman et al. · 2014 [cited by applicant]
US 20140325586A1 · Halliday · 2014 [cited by examiner]
US 20150074390A1 · Stoback et al. · 2015 [cited by applicant]
US 20150156208A1 · Kirkham et al. · 2015 [cited by applicant]
US 20150180903A1 · Cooper et al. · 2015 [cited by applicant]
US 20150288709A1 · Singhal · 2015 [cited by examiner]
US 20150304327A1 · Burstein et al. · 2015 [cited by applicant]
US 20150312267A1 · Thomas · 2015 [cited by applicant]
US 20160191540A1 · Fuka et al. · 2016 [cited by applicant]
US 20160261613A1 · Farmer et al. · 2016 [cited by applicant]
US 20160277424A1 · Mawji et al. · 2016 [cited by applicant]
US 20160292288A1 · Walton et al. · 2016 [cited by applicant]
US 20160373486A1 · Kraemer · 2016 [cited by applicant]
US 20160381079A1 · Ben-Shalom et al. · 2016 [cited by applicant]
US 20170140305A1 · Moss · 2017 [cited by applicant]
US 20170171231A1 · Reybok, Jr. et al. · 2017 [cited by applicant]
US 20180075563A1 · Ananthanpillai et al. · 2018 [cited by applicant]
US 20180091453A1 · Jakobsson · 2018 [cited by applicant]
US 20180183827A1 · Zorlular et al. · 2018 [cited by applicant]
US 20180219865A1 · Das · 2018 [cited by applicant]
US 20190182286A1 · Zini · 2019 [cited by applicant]
US 20190182287A1 · Hanley et al. · 2019 [cited by applicant]
US 20190199759A1 · Anderson et al. · 2019 [cited by applicant]
US 20190207954A1 · Ahuja et al. · 2019 [cited by applicant]
US 20190268366A1 · Zeng et al. · 2019 [cited by applicant]
US 20190310929A1 · Wright et al. · 2019 [cited by applicant]
US 20190342323A1 · Henderson et al. · 2019 [cited by applicant]
US 20200012796A1 · Trepagnier et al. · 2020 [cited by applicant]
US 20200067935A1 · Carnes, III et al. · 2020 [cited by applicant]
US 20200302540A1 · Xiu · 2020 [cited by applicant]
US 20200322348A1 · Kathail · 2020 [cited by examiner]
US 20200356676A1 · Gorlamandala · 2020 [cited by applicant]
US 20200396241A1 · Crabtree et al. · 2020 [cited by applicant]
US 20210029152A1 · Charles et al. · 2021 [cited by applicant]
US 20210075794A1 · Gazit et al. · 2021 [cited by applicant]
US 20210273968A1 · Shaieb et al. · 2021 [cited by applicant]
US 20210409405A1 · Salajegheh et al. · 2021 [cited by applicant]
US 20220043913A1 · Keith, Jr. · 2022 [cited by applicant]
US 20220103588A1 · Shaw · 2022 [cited by applicant]
US 20220103592A1 · Semel et al. · 2022 [cited by applicant]
US 20220166788A1 · Grammel et al. · 2022 [cited by applicant]
US 20220168653A1 · Weising et al. · 2022 [cited by applicant]
US 20220201042A1 · Crabtree et al. · 2022 [cited by applicant]
US 20220210142A1 · Sohail et al. · 2022 [cited by applicant]
US 20220329630A1 · Li · 2022 [cited by applicant]
US 20220345394A1 · Vasseur et al. · 2022 [cited by applicant]
US 20230083952A1 · O'Neill et al. · 2023 [cited by applicant]
US 20230128998A1 · Ping et al. · 2023 [cited by applicant]
US 20230185943A1 · Zhang et al. · 2023 [cited by applicant]
US 20230188527A1 · O'Neill et al. · 2023 [cited by applicant]
US 20230300150A1 · O'Neill et al. · 2023 [cited by applicant]
US 20240223589A1 · Grammel et al. · 2024 [cited by applicant]
US 20240364694A1 · O'Neill et al. · 2024 [cited by applicant]
US 20250030739A1 · O'Neill et al. · 2025 [cited by applicant]
US 20250047680A1 · O'Neill et al. · 2025 [cited by applicant]
CN 1716177A · 2006 [cited by applicant]
CN 101507229A · 2009 [cited by applicant]
CN 102171657A · 2011 [cited by applicant]
CN 105009155A · 2015 [cited by applicant]
CN 105378790A · 2016 [cited by applicant]
CN 106575323A · 2017 [cited by applicant]
CN 107391151A · 2017 [cited by applicant]
CN 108075925A · 2018 [cited by applicant]
CN 109196505A · 2019 [cited by applicant]
CN 109564669A · 2019 [cited by applicant]
CN 109891422A · 2019 [cited by applicant]
CN 109948911A · 2019 [cited by applicant]
CN 110249588A · 2019 [cited by applicant]
CN 110313009A · 2019 [cited by applicant]
CN 110603801A · 2019 [cited by applicant]
EP 1832059A1 · 2007 [cited by applicant]
EP 3343864A1 · 2018 [cited by applicant]
EP 4002795A1 · 2022 [cited by applicant]
WO 2006070172A1 · 2006 [cited by applicant]
WO 2006094275A2 · 2006 [cited by applicant]
WO 2021202833A1 · 2021 [cited by applicant]
Final Office Action from U.S. Appl. No. 17/474,871 dated Jan. 31, 2024, 12 pp. [cited by applicant]
“Cybersecurity of 5G networks EU Toolbox of risk mitigating measures,” Nis Cooperation Group, CG Publication, Jan. 2020, 45 pp. [cited by applicant]
“Overview of Risks Introduced By 5G Adoption in the United States,” Critical Infrastructure Security and Resilience Note, Cybersecurity and Infrastructure Security Agency, Jul. 31, 2019, 16 pp. [cited by applicant]
“Time Guidance for Network Operators, Chief Information Officers, and Chief Information Security Officers,” Cybersecurity and Infrastructure Security Agency, Jun. 2020, 18 pp. [cited by applicant]
Conran, “Zero Trust Networking (ZTN): don't trust anything,” The Network Architect, Sep. 18, 2018, 7 pp. [cited by applicant]
U.S. Appl. No. 16/949,996, filed Nov. 23, 2020, naming inventors Grammel et al. [cited by applicant]
U.S. Appl. No. 17/474,871, filed Sep. 14, 2021, naming inventors O'Neill et al. [cited by applicant]
U.S. Appl. No. 17/644,555, filed Dec. 15, 2021, naming inventors O'Neill et al. [cited by applicant]
Office Action from U.S. Appl. No. 17/474,871 dated Oct. 6, 2023, 11 pp. [cited by applicant]
U.S. Appl. No. 18/148,762, filed Dec. 30, 2022, naming inventors Grammel et al. [cited by applicant]
Office Action from U.S. Appl. No. 16/949,996 dated Sep. 15, 2022, 11 pp. [cited by applicant]
Response to Office Action mailed Oct. 6, 2023, from U.S. Appl. No. 17/474,871, filed Jan. 5, 2024, 9 pp. [cited by applicant]
Jian et al., “Dynamic Evaluation Method of Network Trust based on Congnitive Behavior,” Communications Technology, vol. 49, No. 9, Sep. 2016, 6 pp. [cited by applicant]
Lu et al., “Trust Evaluation in Networked Manufacturing Environment,” Journal of WUT, vol. 35 No. 2, Apr. 2013, 4 pp. [cited by applicant]
Response to Extended Search Report dated Nov. 25, 2022, from counterpart European Application No. 22177761.8 filed Mar. 18, 2024, 14 pp. [cited by applicant]
Response to Office Action mailed Nov. 22, 2023, from U.S. Appl. No. 17/644,555, filed Mar. 22, 2024, 9 pp. [cited by applicant]
Response to Final Office Action dated Jan. 31, 2024 from U.S. Appl. No. 17/474,871, filed Apr. 1, 2024, 8 pp. [cited by applicant]
Office Action from U.S. Appl. No. 17/644,555 dated Nov. 22, 2023, 16 pp. [cited by applicant]
U.S. Appl. No. 18/353,575, filed Jul. 17, 2023, by O'Neill et al. [cited by applicant]
Extended Search Report from counterpart European Application No. 22177761.8 dated Nov. 25, 2022, 7 pp. [cited by applicant]
Response to Office Action mailed Sep. 15, 2022, from U.S. Appl. No. 16/949,996, filed Dec. 13, 2022, 10 pp. [cited by applicant]
Corrected Notice of Allowance from U.S. Appl. No. 16/949,996 dated Mar. 16, 2023, 5 pp. [cited by applicant]
CIS Benchmarks, “CIS Cisco IOS 15 Benchmark”, National Institute of Standards and Technology, vol. 4, No. 1, Apr. 11, 2022, 214 pp., URL: https://ncp.nist.gov/checklist/599. [cited by applicant]
Notice of Allowance from U.S. Appl. No. 16/949,996 dated Feb. 16, 2023, 9 pp. [cited by applicant]
Omeyer, “7 Top Metrics for Measuring Your Technical Debt”, Jan. 13, 2022, 6 pp., URL: https://dev.to/alexomeyer/8-top-metrics-for-measuring-your-technical-debt-5bnm. [cited by applicant]
Notice of Allowance from U.S. Appl. No. 17/474,871 dated Apr. 18, 2024, 8 pp. [cited by applicant]
Mandaglio et al., Generalized Preference Learning for Trust Network Inference, IEEE, Dec. 2, 2019, pp. 174583-174596. ( Year: 2019). [cited by applicant]
Notice of Allowance from U.S. Appl. No. 17/474,871 dated Jul. 11, 2024, 3 pp. [cited by applicant]
Notice of Allowance from U.S. Appl. No. 17/644,555 dated Aug. 7, 2024, p. 14. [cited by applicant]
Zhang et al., Mining Users Trust From E-commerce Reviews Based on Sentiment Similarity Analysis, IEEE, Jan. 31, 2019, pp. 13523-13535. (Year: 2019). [cited by applicant]
Office Action from U.S. Appl. No. 18/770,596 dated Dec. 4, 2024, 9 pp. [cited by applicant]
Corrected Notice of Allowance from U.S. Appl. No. 17/644,555 dated Oct. 9, 2024, 3 pp. [cited by applicant]
First Office Action and Search Report from counterpart Chinese Application No. 202210760004.4 dated May 12, 2025, 15 pp. Translation Attached. [cited by applicant]
Communication pursuant to Article 94(3) EPC from counterpart European Application No. 22177761.8 dated Jun. 3, 2025, 5 pp. [cited by applicant]
Corrected Notice of Allowance from U.S. Appl. No. 18/770,596 dated May 28, 2025, 2 pp. [cited by applicant]
Notice of Allowability from U.S. Appl. No. 18/770,596 dated Mar. 26, 2025, 8 pp. [cited by applicant]
Response to Office Action dated Dec. 4, 2024 from U.S. Appl. No. 18/770,596, filed Feb. 27, 2025, 8 pp. [cited by applicant]
Extended Search Report from counterpart European Application No. 25155589.2 dated Apr. 1, 2025, 11 pp. [cited by applicant]
Office Action from U.S. Appl. No. 18/922,748 dated Feb. 24, 2026, 17 pp. [cited by applicant]
Osborn et al., “BeyondCorp—Design to Deployment at Google”, vol. 41, No. 1, Mar. 1, 2016, pp. 28-35, URL: https://www.usenix.org/system/files/login/articles/login_spring16_06_osborn.pdf. [cited by applicant]
Response to Communication pursuant to Article 94(3) EPC dated Jun. 3, 2025, from counterpart European Application No. 22177761.8 filed Oct. 2, 2025, 10 pp. [cited by applicant]