IP Library Granted Patent US 12,367,292
Granted Patent B2
US 12,367,292 · App. 18/399,422 · Granted Jul 22, 2025

Providing user-induced variable identification of end-to-end computing system security impact information systems and methods

Inventors: Prithvi Narayana Rao (Allen, TX); Pramod Goyal (Ahmedabad, IN)
Assignee: CITIBANK, N.A.
G06F21/577G06F21/552
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,367,292
App. No.
18/399,422
Granted
Jul 22, 2025
Kind
B2
Abstract

Systems and methods for providing user-induced variable identification of end-to-end computing system security impact information via a user interface are disclosed. The system receives at a graphical user interface (GUI), a user calibration of a graphical security vulnerability element. The system then determines a set of computing system components that interact with data associated with the network operation based on a transmission of the network operation associated with a computing system. The system then determines a set of security vulnerabilities associated with each computing system component of the set of computing system components using a third-party resource. The system then applies a decision engine on the set of security vulnerabilities to determine a set of impacted computing-aspects associated with the set of computing system components. The system then generates for display a graphical representation of the set of impacted computing-aspects satisfying the security condition of the user calibration.

Claims (61)

1. A system for providing variable identification of end-to-end computing system security impact information via user interfaces, the system comprising:

at least one processor; and

at least one memory coupled to the at least one processor and storing instructions that, when executed by the at least one processor, perform operations comprising:

receiving, at a user interface, a user calibration of a security vulnerability element, wherein the user calibration adjusts the security vulnerability element to a position indicative of a security condition related to identifying impacted assessment domains of computing system threats;

determining, based on a processing of a network operation from a first device to a second device, a set of computing system components that are associated with the processing of the network operation;

receiving response data from each computing system component of the set of computing system components associated with one or more security-attributes of the respective computing system component;

determining a set of security vulnerabilities associated with each computing system component of the set of computing system components using (i) a third-party resource and (ii) the response data;

applying a model to generate a set of impacted assessment domains associated with the set of computing system components using the set of security vulnerabilities; and

generating for display at the user interface, a visual representation of the set of impacted assessment domains satisfying the security condition of the user calibration.

2. The system of claim 1 , further storing instructions that, when executed by the at least one processor, perform operations comprising:

training the model on training data comprising a set of labeled feature vectors, wherein each labeled feature vector of the set of labeled feature vectors indicates labels of (i) a given security vulnerability, (ii) a given computing system component, and (iii) a given impacted assessment domain.

3. The system of claim 1 , further storing instructions that, when executed by the at least one processor, perform operations comprising:

applying a second model to generate a set of security mitigation actions using (i) the set of impacted assessment domains and (ii) the set of security vulnerabilities, wherein each security mitigation action of the set of security mitigation actions is associated with a respective impacted assessment domain and a respectively corresponding security vulnerability;

determining an assessment domain impact level for each impacted assessment domain of the set of impacted assessment domains; and

in response to the assessment domain impact level for a respective impacted assessment domain of the set of impacted assessment domains satisfying a threshold assessment domain impact level, configuring a network component to apply a respective security mitigation action to one or more computing system components associated with the respective impacted assessment domain.

4. The system of claim 3 , further storing instructions that, when executed by the at least one processor, perform operations comprising:

training the second model on second training data comprising a second set of labeled feature vectors, wherein each labeled feature vector of the second set of labeled feature vectors indicates labels of (i) a given impacted assessment domain, (ii) a given security vulnerability, and (iii) a given security mitigation action.

5. The system of claim 4 , wherein the given security mitigation action is based on a platform-specific policy.

6. The system of claim 1 , further storing instructions that, when executed by the at least one processor, perform operations comprising:

receiving, at the user interface, a second user calibration of the security vulnerability element, wherein the second user calibration adjusts the security vulnerability element to a second position indicative of the security condition related to identifying security vulnerabilities; and

in response to receiving the second user calibration of the security vulnerability element, updating the visual representation of the set of impacted assessment domains satisfying the security condition of the second user calibration.

7. The system of claim 1 , wherein the response data is security-response data received in response to the processing of the network operation.

8. A method for providing user-induced variable identification of end-to-end computing system security impact information via user interfaces, the method comprising:

receiving a user calibration of a security vulnerability element, wherein the user calibration adjusts the security vulnerability element to a position indicative of a security condition related to identifying impacted computing-aspects of computing system threats;

determining, based on a processing of a network operation associated with a computing system, a set of computing system components that are associated with the processing of the network operation;

determining a set of security vulnerabilities associated with each computing system component of the set of computing system components using a third-party resource;

generating a set of impacted computing-aspects associated with the set of computing system components using the set of security vulnerabilities; and

generating for display at a user interface, a visual representation of the set of impacted computing-aspects satisfying the security condition of the user calibration.

9. The method of claim 8 , further comprising:

training a model on training data comprising a set of labeled feature vectors, wherein each labeled feature vector of the set of labeled feature vectors indicates labels of (i) a given security vulnerability, (ii) a given computing system component, and (iii) a given impacted computing-aspect; and

generating the set of impacted computing-aspects associated with the set of computing system components, via the model, using the set of security vulnerabilities.

10. The method of claim 8 , further comprising:

applying a model to generate a set of security mitigation actions using (i) the set of impacted computing-aspects and (ii) the set of security vulnerabilities, wherein each security mitigation action of the set of security mitigation actions is associated with a respective impacted computing-aspect and a respectively corresponding security vulnerability;

determining an computing-aspect impact level for each impacted computing-aspect of the set of impacted computing-aspects; and

in response to the computing-aspect impact level for a respective impacted computing-aspect of the set of impacted computing-aspects satisfying a threshold computing-aspect impact level, configuring a network component to apply a respective security mitigation action to one or more computing system components associated with the respective impacted computing-aspect.

11. The method of claim 10 , further comprising:

training the model on second training data comprising a second set of labeled feature vectors, wherein each labeled feature vector of the second set of labeled feature vectors indicates labels of (i) a given impacted computing-aspect, (ii) a given security vulnerability, and (iii) a given security mitigation action.

12. The method of claim 8 , further comprising:

receiving, at the user interface, a second user calibration of the security vulnerability element, wherein the second user calibration adjusts the security vulnerability element to a second position indicative of the security condition related to identifying security vulnerabilities; and

in response to receiving the second user calibration of the security vulnerability element, updating the visual representation of the set of impacted computing-aspects satisfying the security condition of the second user calibration.

13. The method of claim 8 , wherein security-response data is received in response to the processing of the network operation and used to further determine the set of security vulnerabilities.

14. One or more non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause operations comprising:

receiving a user calibration of a security vulnerability element, wherein the user calibration adjusts the security vulnerability element to a position indicative of a security condition related to identifying impacted computing-aspects of computing system threats;

determining, based on a processing of a network operation associated with a computing system, a set of computing system components that are associated with the processing of the network operation;

determining a set of security vulnerabilities associated with each computing system component of the set of computing system components using a third-party resource;

generating a set of impacted computing-aspects associated with the set of computing system components using the set of security vulnerabilities; and

generating for display at a user interface, a visual representation of the set of impacted computing-aspects satisfying the security condition of the user calibration.

15. The medium of claim 14 , wherein the operations further comprise:

training a model on training data comprising a set of labeled feature vectors, wherein each labeled feature vector of the set of labeled feature vectors indicates labels of (i) a given security vulnerability, (ii) a given computing system component, and (iii) a given impacted computing-aspect; and

generating the set of impacted computing-aspects associated with the set of computing system components, via the model, using the set of security vulnerabilities.

16. The medium of claim 14 , wherein the operations further comprise:

applying a model to generate a set of security mitigation actions using (i) the set of impacted computing-aspects and (ii) the set of security vulnerabilities, wherein each security mitigation action of the set of security mitigation actions is associated with a respective impacted computing-aspect and a respectively corresponding security vulnerability;

determining an computing-aspect impact level for each impacted computing-aspect of the set of impacted computing-aspects; and

in response to the computing-aspect impact level for a respective impacted computing-aspect of the set of impacted computing-aspects satisfying a threshold computing-aspect impact level, configuring a network component to apply a respective security mitigation action to one or more computing system components associated with the respective impacted computing-aspect.

17. The medium of claim 16 , wherein the operations further comprise:

training the model on second training data comprising a second set of labeled feature vectors, wherein each labeled feature vector of the second set of labeled feature vectors indicates labels of (i) a given impacted computing-aspect, (ii) a given security vulnerability, and (iii) a given security mitigation action.

18. The medium of claim 17 , wherein the given security mitigation action is based on a platform-specific policy.

19. The medium of claim 14 , wherein the operations further comprise:

receiving, at the user interface, a second user calibration of the security vulnerability element, wherein the second user calibration adjusts the security vulnerability element to a second position indicative of the security condition related to identifying security vulnerabilities; and

in response to receiving the second user calibration of the security vulnerability element, updating the visual representation of the set of impacted computing-aspects satisfying the security condition of the second user calibration.

20. The medium of claim 14 , wherein security-response data is received in response to the processing of the network operation and used to further determine the set of security vulnerabilities.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 12, 2024
From: RAO, PRITHVI NARAYANA; GOYAL, PRAMOD
To: CITIBANK, N.A.
Reel/Frame 066115/0929 →
Continuity (4)
Continuation 18327040 · May 31, 2023
Continuation In Part 18114194 · Feb 24, 2023
Continuation In Part 18098895 · Jan 19, 2023
Related Publication 20240403440A1 · Dec 5, 2024
References Cited (225)
US 8380817B2 · Okada · 2013 [cited by applicant]
US 8387020B1 · Maclachlan et al. · 2013 [cited by applicant]
US 9842045B2 · Heorhiadi et al. · 2017 [cited by applicant]
US 10620988B2 · Lauderdale et al. · 2020 [cited by applicant]
US 10943067B1 · Brown et al. · 2021 [cited by applicant]
US 11042647B1 · Joyce et al. · 2021 [cited by applicant]
US 11106801B1 · Levine et al. · 2021 [cited by applicant]
US 11133942B1 · Griffin · 2021 [cited by applicant]
US 11227047B1 · Vashisht et al. · 2022 [cited by applicant]
US 11227187B1 · Weinberger · 2022 [cited by applicant]
US 11328068B1 · Niedzwiedz et al. · 2022 [cited by applicant]
US 11410136B2 · Cook et al. · 2022 [cited by applicant]
US 11470106B1 · Lin et al. · 2022 [cited by applicant]
US 11503075B1 · Sirianni et al. · 2022 [cited by applicant]
US 11516222B1 · Srinivasan et al. · 2022 [cited by applicant]
US 11573848B2 · Linck et al. · 2023 [cited by applicant]
US 11652839B1 · Aloisio et al. · 2023 [cited by applicant]
US 11656852B2 · Mazurskiy · 2023 [cited by applicant]
US 11681811B1 · Dixit · 2023 [cited by applicant]
US 11683333B1 · Dominessy et al. · 2023 [cited by applicant]
US 11706241B1 · Cross et al. · 2023 [cited by applicant]
US 11720686B1 · Cross et al. · 2023 [cited by applicant]
US 11734418B1 · Epstein · 2023 [cited by applicant]
US 11741226B2 · Dixit · 2023 [cited by examiner]
US 11750717B2 · Walsh et al. · 2023 [cited by applicant]
US 11875123B1 · Ben David et al. · 2024 [cited by applicant]
US 11875130B1 · Bosnjakovic et al. · 2024 [cited by applicant]
US 11924027B1 · Mysore et al. · 2024 [cited by applicant]
US 11947435B2 · Boulineau et al. · 2024 [cited by applicant]
US 11960515B1 · Pallakonda et al. · 2024 [cited by applicant]
US 11983806B1 · Ramesh et al. · 2024 [cited by applicant]
US 11990139B1 · Sandrew · 2024 [cited by applicant]
US 11995412B1 · Mishra · 2024 [cited by applicant]
US 12001463B1 · Pallakonda et al. · 2024 [cited by applicant]
US 12026599B1 · Lewis et al. · 2024 [cited by applicant]
US 12028368B1 · Cohen et al. · 2024 [cited by applicant]
US 12107869B1 · Kannan et al. · 2024 [cited by applicant]
US 12135949B1 · Cameron et al. · 2024 [cited by applicant]
US 12149553B1 · Fly et al. · 2024 [cited by applicant]
US 12149558B1 · Brown et al. · 2024 [cited by applicant]
US 12155781B1 · Helfgott et al. · 2024 [cited by applicant]
US 12182258B2 · Stokes et al. · 2024 [cited by applicant]
US 20030007178A1 · Jeyachandran et al. · 2003 [cited by applicant]
US 20040098454A1 · Trapp et al. · 2004 [cited by applicant]
US 20050204348A1 · Horning et al. · 2005 [cited by applicant]
US 20060095918A1 · Hirose · 2006 [cited by applicant]
US 20070067848A1 · Gustave et al. · 2007 [cited by applicant]
US 20100275263A1 · Bennett et al. · 2010 [cited by applicant]
US 20100313189A1 · Beretta et al. · 2010 [cited by applicant]
US 20140137257A1 · Martinez et al. · 2014 [cited by applicant]
US 20140258998A1 · Adl-tabatabai et al. · 2014 [cited by applicant]
US 20170061132A1 · Hovor et al. · 2017 [cited by applicant]
US 20170262164A1 · Jain et al. · 2017 [cited by applicant]
US 20170279826A1 · Mohanty · 2017 [cited by examiner]
US 20170295197A1 · Parimi et al. · 2017 [cited by applicant]
US 20180020021A1 · Gilmore et al. · 2018 [cited by applicant]
US 20180239903A1 · Bodin et al. · 2018 [cited by applicant]
US 20180343114A1 · Ben-ari · 2018 [cited by applicant]
US 20190188706A1 · Mccurtis · 2019 [cited by applicant]
US 20190236661A1 · Hogg et al. · 2019 [cited by applicant]
US 20190286816A1 · Fu · 2019 [cited by applicant]
US 20200012493A1 · Sagy · 2020 [cited by applicant]
US 20200074470A1 · Deshpande et al. · 2020 [cited by applicant]
US 20200153855A1 · Kirti et al. · 2020 [cited by applicant]
US 20200219009A1 · Dao et al. · 2020 [cited by applicant]
US 20200233979A1 · Tahmasebi Maraghoosh et al. · 2020 [cited by applicant]
US 20200259852A1 · Wolff et al. · 2020 [cited by applicant]
US 20200309767A1 · Loo et al. · 2020 [cited by applicant]
US 20200310866A1 · Varadaraj et al. · 2020 [cited by applicant]
US 20200314191A1 · Madhavan et al. · 2020 [cited by applicant]
US 20200349054A1 · Dai et al. · 2020 [cited by applicant]
US 20200380118A1 · Miller et al. · 2020 [cited by applicant]
US 20200387608A1 · Miller et al. · 2020 [cited by applicant]
US 20210049288A1 · Li · 2021 [cited by applicant]
US 20210089941A1 · Chen et al. · 2021 [cited by applicant]
US 20210133182A1 · Anderson et al. · 2021 [cited by applicant]
US 20210185094A1 · Waplington et al. · 2021 [cited by applicant]
US 20210211431A1 · Albero et al. · 2021 [cited by applicant]
US 20210256125A1 · Miller et al. · 2021 [cited by applicant]
US 20210264547A1 · Li · 2021 [cited by applicant]
US 20210273957A1 · Boyer · 2021 [cited by examiner]
US 20210390465A1 · Werder et al. · 2021 [cited by applicant]
US 20220050928A1 · Shukla et al. · 2022 [cited by applicant]
US 20220114251A1 · Guim Bernat et al. · 2022 [cited by applicant]
US 20220114399A1 · Castiglione et al. · 2022 [cited by applicant]
US 20220147636A1 · Mahuli et al. · 2022 [cited by applicant]
US 20220164732A1 · Brannon · 2022 [cited by examiner]
US 20220166789A1 · Murray · 2022 [cited by examiner]
US 20220188460A1 · Hadar · 2022 [cited by examiner]
US 20220191236A1 · Henderson · 2022 [cited by examiner]
US 20220198304A1 · Szczepanik et al. · 2022 [cited by applicant]
US 20220201042A1 · Crabtree · 2022 [cited by examiner]
US 20220210200A1 · Crabtree · 2022 [cited by examiner]
US 20220210202A1 · Crabtree · 2022 [cited by examiner]
US 20220222089A1 · Joshi · 2022 [cited by examiner]
US 20220224702A1 · Dherange · 2022 [cited by examiner]
US 20220224723A1 · Crabtree · 2022 [cited by examiner]
US 20220237565A1 · Dzierzanowski · 2022 [cited by examiner]
US 20220263843A1 · Aslam · 2022 [cited by examiner]
US 20220263855A1 · Engelberg · 2022 [cited by examiner]
US 20220263860A1 · Crabtree · 2022 [cited by examiner]
US 20220278889A1 · Malleshaiah · 2022 [cited by examiner]
US 20220286438A1 · Burke et al. · 2022 [cited by applicant]
US 20220286474A1 · Kuppa · 2022 [cited by examiner]
US 20220294789A1 · Tikhomirov et al. · 2022 [cited by applicant]
US 20220294810A1 · Tyagi · 2022 [cited by examiner]
US 20220303295A1 · Erlingsson et al. · 2022 [cited by applicant]
US 20220303300A1 · Egan · 2022 [cited by examiner]
US 20220303302A1 · Hwang et al. · 2022 [cited by applicant]
US 20220303352A1 · Herzog · 2022 [cited by examiner]
US 20220311681A1 · Palladino et al. · 2022 [cited by applicant]
US 20220318654A1 · Lin et al. · 2022 [cited by applicant]
US 20220327620A1 · Ndoutoumou · 2022 [cited by applicant]
US 20220334818A1 · Mcfarland · 2022 [cited by applicant]
US 20220342846A1 · Kunchakarra et al. · 2022 [cited by applicant]
US 20220345457A1 · Jeffords et al. · 2022 [cited by applicant]
US 20220368728A1 · Murray et al. · 2022 [cited by applicant]
US 20220377093A1 · Crabtree et al. · 2022 [cited by applicant]
US 20220398149A1 · Mcfarland et al. · 2022 [cited by applicant]
US 20220400135A1 · Gamra · 2022 [cited by applicant]
US 20220405397A1 · Golan et al. · 2022 [cited by applicant]
US 20220414213A1 · Dixit · 2022 [cited by applicant]
US 20220417274A1 · Madanahalli et al. · 2022 [cited by applicant]
US 20230007039A1 · Waplington · 2023 [cited by applicant]
US 20230009999A1 · Higuchi et al. · 2023 [cited by applicant]
US 20230019072A1 · Okunlola · 2023 [cited by applicant]
US 20230032686A1 · Williams et al. · 2023 [cited by applicant]
US 20230033317A1 · Lin et al. · 2023 [cited by applicant]
US 20230035321A1 · Vijayaraghavan · 2023 [cited by applicant]
US 20230039855A1 · Greene · 2023 [cited by applicant]
US 20230052608A1 · Wattiau et al. · 2023 [cited by applicant]
US 20230067128A1 · Engelberg et al. · 2023 [cited by applicant]
US 20230071264A1 · Hakala et al. · 2023 [cited by applicant]
US 20230076372A1 · Engelberg et al. · 2023 [cited by applicant]
US 20230077527A1 · Sarkar · 2023 [cited by applicant]
US 20230113621A1 · Griffin et al. · 2023 [cited by applicant]
US 20230114719A1 · Thomas et al. · 2023 [cited by applicant]
US 20230117962A1 · Kaimal et al. · 2023 [cited by applicant]
US 20230118388A1 · Crabtree et al. · 2023 [cited by applicant]
US 20230123314A1 · Crabtree et al. · 2023 [cited by applicant]
US 20230132703A1 · Marsenic et al. · 2023 [cited by applicant]
US 20230135660A1 · Chapman et al. · 2023 [cited by applicant]
US 20230148116A1 · Stokes et al. · 2023 [cited by applicant]
US 20230164158A1 · Fellows et al. · 2023 [cited by applicant]
US 20230169397A1 · Smith et al. · 2023 [cited by applicant]
US 20230171282A1 · Bollinger · 2023 [cited by applicant]
US 20230177613A1 · Crabtree et al. · 2023 [cited by applicant]
US 20230205888A1 · Tyagi et al. · 2023 [cited by applicant]
US 20230205891A1 · Yellapragada et al. · 2023 [cited by applicant]
US 20230208869A1 · Bisht et al. · 2023 [cited by applicant]
US 20230208870A1 · Yellapragada et al. · 2023 [cited by applicant]
US 20230208871A1 · Yellapragada et al. · 2023 [cited by applicant]
US 20230229542A1 · Watkins et al. · 2023 [cited by applicant]
US 20230259860A1 · Sarkar · 2023 [cited by applicant]
US 20230269272A1 · Dambrot et al. · 2023 [cited by applicant]
US 20230274003A1 · Liu et al. · 2023 [cited by applicant]
US 20230359789A1 · Andre et al. · 2023 [cited by applicant]
US 20230362200A1 · Crabtree et al. · 2023 [cited by applicant]
US 20230396641A1 · Hebbagodi et al. · 2023 [cited by applicant]
US 20230412635A1 · Binyamini et al. · 2023 [cited by applicant]
US 20240020538A1 · Socher et al. · 2024 [cited by applicant]
US 20240037245A1 · Kahan et al. · 2024 [cited by applicant]
US 20240054233A1 · Ohayon et al. · 2024 [cited by applicant]
US 20240054249A1 · Loubet Moundi et al. · 2024 [cited by applicant]
US 20240095077A1 · Singh et al. · 2024 [cited by applicant]
US 20240129345A1 · Kassam et al. · 2024 [cited by applicant]
US 20240256678A1 · Thompson · 2024 [cited by applicant]
US 20240323202A1 · Niv et al. · 2024 [cited by applicant]
US 20240333743A1 · Bazalgette et al. · 2024 [cited by applicant]
US 20240333753A1 · Cross et al. · 2024 [cited by applicant]
US 20240340301A1 · Thompson · 2024 [cited by applicant]
US 20240340302A1 · Wang et al. · 2024 [cited by applicant]
US 20240346151A1 · Goswami et al. · 2024 [cited by applicant]
US 20240356984A1 · Gamra · 2024 [cited by applicant]
US 20240356986A1 · Crabtree et al. · 2024 [cited by applicant]
US 20240364725A1 · Sinha et al. · 2024 [cited by applicant]
US 20240364749A1 · Crabtree et al. · 2024 [cited by applicant]
US 20240403420A1 · Lal et al. · 2024 [cited by applicant]
US 20240403428A1 · Lal et al. · 2024 [cited by applicant]
US 20240403437A1 · Szigeti et al. · 2024 [cited by applicant]
US 20240403445A1 · Straub et al. · 2024 [cited by applicant]
US 20240406145A1 · Crabtree et al. · 2024 [cited by applicant]
US 20240411896A1 · Myers et al. · 2024 [cited by applicant]
US 20240414191A1 · Humphrey et al. · 2024 [cited by applicant]
US 20240414211A1 · Boyer et al. · 2024 [cited by applicant]
US 20250005167A1 · Millar et al. · 2025 [cited by applicant]
US 20250013753A1 · Conway · 2025 [cited by applicant]
US 20250021464A1 · Lang et al. · 2025 [cited by applicant]
WO 2021160499A1 · 2021 [cited by applicant]
WO 2024020416A1 · 2024 [cited by applicant]
Aggarwal, Nitin , “Why measuring your new AI is essential to its succes”, KPIs for gen AI: Why measuring your new AI is essential to its succes, 7 pages. [cited by applicant]
AI , “What is AI Verify?”, What is AI Verify—AI Verify Foundation. [cited by applicant]
Altman, Sam , “Sam Altman Admits That OpenAI Doesn't Actually Understand How Its AI Works”, Sam Altman Admits That OpenAI Doesn't Actually Understand How Its AI Works—“We certainly have not solved interpretability.”, 4 … [cited by applicant]
Shah, Harshay , “Decomposing and Editing Predictions by Modeling Model Computation”, Decomposing and Editing Predictions by Modeling Model Computation, 5 pages. [cited by applicant]
Empower Your Team with a Compliance Co-Pilot, Sedric, retrieved on Sep. 25, 2024. https://www.sedric.ai/. [cited by applicant]
Cranium, Adopt & Accelerate AI Safely, retrieved on Nov. 7, 2024, from https://cranium.ai/. [cited by applicant]
Farris, K., A., et al., “Vulcon: A System for Vulnerability Prioritization, Mitigation, and Management,” ACM Transactions on Privacy and Security, vol. 21, No. 4, Article 16. Publication date: Jun. 2018, 28 pages. [cited by applicant]
Generative machine learning models; IPCCOM000272835D, Aug. 17, 2023. (Year: 2023). [cited by applicant]
Guldimann, P., et al. “COMPL-AI Framework: A Technical Interpretation and LLM Benchmarking Suite for the EU Artificial Intelligence Act,” arXiv:2410.07959v1 [cs.CL] Oct. 10, 2024, 38 pages. [cited by applicant]
Mathews, A. W., “What AI Can Do in Healthcare—and What It Should Never Do,” The Wall Street Journal, published on Aug. 21, 2024, retrieved on Sep. 5, 2024 https://www.wsj.com. [cited by applicant]
Nauta, M., et al., “From Anecdotal Evidence to Quantative Evaluation Methods: A Systematic Review of Evaluating Explainable AI” ACM Computing Surveys, vol. 55 No. 13s Article 295, 2023 [retrieved Jul. 3, 2024]. [cited by applicant]
Peers, M., “What California AI Bill Could Mean,” The Briefing, published and retrieved Aug. 30, 2024, 8 pages, https://www.theinformation.com/articles/what-california-ai-bill-could-mean. [cited by applicant]
AI Risk Management Framework NIST, retrieved on Jun. 17, 2024, https://www.nist.gov/itl/ai-risk-management-framework. [cited by applicant]
Independent analysis of AI language models and API providers. Artificial Analysis, retrieved on Jun. 13, 2024, https://artificialanalysis.ai/, 11 pages. [cited by applicant]
Brown, D., et al., “The Great AI Challenge: We Test Five Top Bots on Useful, Everyday Skills,” The Wall Street Journal, published May 25, 2024. [cited by applicant]
Dong, Y., et al., “Building Guardrails for Large Language Models,” https://ar5iv.labs.arxiv.org/html/2402.01822v1, published May 29, 2024, 20 pages. [cited by applicant]
International Search Report and Written Opinion Received received in Application No. PCT/US23/85942, dated Feb. 15, 2024, 6 pages. [cited by applicant]
Kojima, Takeshi, et al. “Large Language Models are Zero-Shot Reasoners,” 36th Conference on Neural Information Processing Systems (NeurIPS 2022), arXiv:2205.11916 [cs.CL], Jan. 29, 2023, 42 pages. [cited by applicant]
Mavrepis, P., et al., “XAI for All: Can Large Language Models Simplify Explainable AI?,” https://arxiv.org/abs/2401.13110, Jan. 23, 2024, 10 pages. [cited by applicant]
Wei, Jason, et al. “Chain-of-Thought Prompting Elicits Reasoning in Large Language Models,” 36th Conference on Neural Information Processing Systems (NeurIPS 2022), arXiv:2201.11903 [cs.CL], Jan. 10, 2023, 43 pages. [cited by applicant]
Zhao, H., et al., “Explainability for Large Language Models: A Survey,” https://arxiv.org/abs/2309.01029, Nov. 28, 2024, 38 pages. [cited by applicant]
Zhou, Y., Liu, Y., Li, X., Jin, J., Qian, H., Liu, Z., Li, C., Dou, Z., Ho, T., & Yu, P. S. (2024). Trustworthiness in Retrieval-Augmented Generation Systems: A Survey. ArXiv. /abs/2409.10102. [cited by applicant]
Aggarwal, Nitin , “Why measuring your new AI is essential to its succes”, KPIs for gen AI: Why measuring your new AI is essential to its succes, 7 pages, Jun. 11, 2024. [cited by applicant]
AI , “What is AI Verify?”, What is AI Verify—AI Verify Foundation, Jun. 11, 2024. [cited by applicant]
Altman, Sam , “Sam Altman Admits That OpenAI Doesn't Actually Understand How Its AI Works”, Sam Altman Admits That OpenAI Doesn't Actually Understand How Its AI Works—“We certainly have not solved interpretability.”, 4 … [cited by applicant]
Anthrop/C , “Mapping the Mind of a Large Language Model”, Mapping the Mind of a Large Language Model, May 21, 2024. [cited by applicant]
Claburn, Thomas , “OpenAI's GPT-4 can exploit real vulnerabilities by reading security advisories”, OpenAI's GPT-4 can exploit real vulnerabilities by reading security advisories, Apr. 17, 2024, 3 pages. [cited by applicant]
Marshall, Andrew , “Threat Modeling AI/ML Systems and Dependencies”, Threat Modeling AI/ML Systems and Dependencies, Nov. 2, 2022, 27 pages. [cited by applicant]
Roose, Kevin , “A.I. Has a Measurement Problem”, A.I. Has a Measurement Problem, Apr. 15, 2024, 5 pages. [cited by applicant]
Roose, Kevin , “A.I.'s Black Boxes Just Got a Little Less Mysterious”, A.I.'s Black Boxes Just Got a Little Less Mysterious, May 21, 2024, 5 pages. [cited by applicant]
Shah, Harshay , “Decomposing and Editing Predictions by Modeling Model Computation”, Decomposing and Editing Predictions by Modeling Model Computation, 5 pages, Jun. 11, 2024. [cited by applicant]
Shankar, Ram , “Failure Modes in Machine Learning”, , Nov. 2019, 14 pages. [cited by applicant]
Teo, Josephine , “Singapore launches Project Moonshot”, Singapore launches Project Moonshot—a generative Artificial Intelligence testing toolkit to address LLM safety and security challenges, May 31, 2024, 8 pages. [cited by applicant]
Coalition for Content Provenance and Authenticity, Contents Credentials C2PA Technological Specification, v2.1,Sep. 20, 2024. (Year: 2024). [cited by applicant]
Stokes, et al. “Preventing Machine Learning Poisoning Attacks Using Authentication and Provenance”, MILCOM 2021—2021 IEEE Military Communications Conference (MILCOM), 2021, pp. 181-188. (Year: 2021). [cited by applicant]
Cited By (1)
US 12,712,909