IP Library Granted Patent US 12,400,007
Granted Patent B2
US 12,400,007 · App. 18/469,490 · Granted Aug 26, 2025

Comparative real-time end-to-end security vulnerabilities determination and visualization

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,400,007
App. No.
18/469,490
Granted
Aug 26, 2025
Kind
B2
Abstract

Systems and methods for determining and displaying comparative platform-specific security vulnerabilities with respect to cloud-based computing platforms are disclosed. To compare platform-specific security vulnerabilities of cloud-based computing platforms, the system detects a user interaction at a webpage for a network operation. The system then determines a first set of computing aspects associated with a set of cloud-based computing platforms using response data received from a processing of the network operation. The system then identifies a second set of computing aspects associated with a comparative cloud-based computing system platform and determines an overall-computing aspect impact level for associated computing aspects of the second set of computing aspects. The system then generates for display at a graphical user interface (GUI), a graphical layout indicating a graphical representation of each determined overall-computing aspect impact level for the respective cloud-based computing system platforms.

Claims (85)

1. A system for determining comparative real-time end-to-end security vulnerabilities, 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:

detecting a network operation transferring data from a mobile computing system platform to a set of cloud-based computing system platforms, wherein each cloud-based computing system platform of the set of cloud-based computing system platforms is associated with a cloud-based platform service provider;

determining a first set of assessment-domains associated with each cloud-based computing system platform of the set of cloud-based computing system platforms based on the transferring of the data;

identifying a second set of assessment-domains associated with a standard cloud-based computing system platform using an assessment-domain-mapping data structure;

determining an overall assessment-domain impact level for a set of associated assessment-domains using (i) the first set of assessment-domains associated with each cloud-based computing system platform and (ii) the second set of assessment-domains; and

generating an output indicating a representation of normalized assessment-domain impact levels of the set of associated assessment-domains for each respective cloud-based computing system platform of the set of cloud-based computing system platforms.

2. The system of claim 1 , wherein determining the overall assessment-domain impact level for the set of associated assessment-domains further comprises:

comparing, for each cloud-based computing system platform, the first set of assessment-domains of the respective cloud-based computing system platform to the second set of assessment-domains to determine a matching set of assessment-domains, the matching set of assessment-domains representing the set of associated assessment-domains;

obtaining, from a third-party security entity, a set of security-vulnerability responses, wherein each response of the set of security-vulnerability responses indicates at least one security threat associated with a respective assessment domain of the matching set of assessment-domains;

assigning a threat value to each security-vulnerability response of the set of security-vulnerability responses by comparing a respective security-vulnerability response to a platform-specific policy, wherein the platform-specific policy includes security-vulnerability responses mapped to a respective threat level; and

determining the overall assessment-domain impact level for each matching assessment-domain of the set of matching assessment-domains respective to the cloud-based computing system platform by computing a weighted average of assigned threat values of the respective matching assessment-domains.

3. The system of claim 1 , wherein determining the overall assessment-domain impact level for the set of associated assessment-domains further comprises:

comparing, for each cloud-based computing system platform, the first set of assessment-domains of the respective cloud-based computing system platform to the second set of assessment-domains to determine a mismatched set of assessment-domains, the mismatched set of assessment-domains representing the set of associated assessment-domains;

obtaining, from a third-party security entity, a set of security-vulnerability responses, wherein each response of the set of security-vulnerability responses indicate at least one security threat associated with a respective assessment domain of the mismatched set of assessment-domains;

assigning a threat value to each security-vulnerability response of the set of security-vulnerability responses by comparing a respective security-vulnerability response to a platform-specific policy, wherein the platform-specific policy includes security-vulnerability responses mapped to a respective threat level; and

determining the overall assessment-domain impact level for each mismatched assessment-domain of the set of mismatched assessment-domains respective to the cloud-based computing system platform by computing a weighted average of assigned threat values of the respective mismatched assessment-domains.

4. The system of claim 1 , wherein determining the overall assessment-domain impact level for the set of associated assessment-domains further comprises:

comparing, for each cloud-based computing system platform, the first set of assessment-domains of the respective cloud-based computing system platform to the second set of assessment-domains to determine a (i) matching set of assessment-domains and (ii) a mismatched set of assessment-domains, the matching set of assessment-domains and the mismatched set of assessment-domains representing the set of associated assessment-domains;

obtaining, from a third-party security entity, a set of security-vulnerability responses, wherein each response of the set of security-vulnerability responses indicates at least one security threat associated with a respective assessment domain of the matching set of assessment-domains respective to the cloud-based computing system platform;

assigning a threat value to each security-vulnerability response of the set of security-vulnerability responses by comparing a respective security-vulnerability response to a platform-specific policy, wherein the platform-specific policy includes security-vulnerability responses mapped to a respective threat level;

determining an assessment-domain impact level for each matching assessment-domain of the set of matching assessment-domains respective to the cloud-based computing system platform by computing a weighted average of assigned threat values of the respective matching assessment-domains;

assigning a placeholder assessment-domain impact level for each mismatched assessment-domain of the set of mismatched assessment-domains respective to the cloud-based computing system platform; and

determining the overall assessment-domain impact levels for the set of associated assessment-domains using the (i) the assessment-domain impact level of each matching assessment-domain of the set of matching assessment-domains and (ii) the placeholder assessment-domain impact level for each mismatched assessment domain of the set of mismatched assessment domains, wherein the overall assessment-domain impact levels are respective cloud-based computing system platforms of the set of cloud-based computing system platforms.

5. A method for determining comparative real-time end-to-end security vulnerabilities, the method comprising:

detecting a network operation processing data between one computing system platform and a set of cloud-based computing system platforms;

determining a first set of computing aspects associated with each cloud-based computing system platform of the set of cloud-based computing system platforms based on the processing of the network operation;

identifying a second set of computing aspects associated with a comparative cloud-based computing system platform;

determining an overall-computing aspect impact level for a set of associated computing aspects between (i) the first set of computing aspects associated with each cloud-based computing system platform and (ii) the second set of computing aspects;

generating an output indicating a representation of each overall-computing aspect impact level of the set of associated computing aspects; and

in response to detecting that a given overall-computing aspect impact level for a given associated computing aspect of the set of associated computing aspects satisfies a threshold overall-computing aspect impact level, configuring a network component associated with an entity to process a second network operation via the cloud-based computing system platform associated with the satisfied overall-computing aspect impact level, wherein the given overall-computing aspect impact level for the given associated computing aspect of the set of associated computing aspects satisfying the threshold overall-computing aspect impact level is detected.

6. The method of claim 5 , wherein determining the overall-computing aspect impact level for the set of associated computing aspects further comprises:

comparing, for each cloud-based computing system platform, the first set of computing aspects of a respective cloud-based computing system platform to the second set of computing aspects to determine a matching set of computing aspects, the matching set of computing aspects representing the set of associated computing aspects;

obtaining, from a third-party security entity, a set of security-vulnerability descriptions, wherein each description of the set of security-vulnerability descriptions indicates at least one security threat associated with a respective computing aspect of the matching set of computing aspects;

assigning a threat value to each security-vulnerability description of the set of security-vulnerability descriptions by comparing a respective security-vulnerability description to a platform-specific policy, wherein the platform-specific policy includes security-vulnerability descriptions mapped to a respective threat level; and

determining the overall-computing aspect impact level for each matching computing aspect of the set of matching computing aspects respective to the cloud-based computing system platform by computing a weighted average of assigned threat values of the respective matching computing aspects.

7. The method of claim 5 , wherein determining the overall-computing aspect impact level for the set of associated computing aspects further comprises:

comparing, for each cloud-based computing system platform, the first set of computing aspects of the respective cloud-based computing system platform to the second set of computing aspects to determine a mismatched set of computing aspects, the mismatched set of computing aspects representing the set of associated computing aspects;

obtaining, from a third-party security entity, a set of security-vulnerability descriptions, wherein each description of the set of security-vulnerability descriptions indicates at least one security threat associated with a respective computing aspect of the mismatched set of computing aspects;

assigning a threat value to each security-vulnerability description of the set of security-vulnerability descriptions by comparing a respective security-vulnerability description to a platform-specific policy, wherein the platform-specific policy includes security-vulnerability descriptions mapped to a respective threat level; and

determining the overall-computing aspect impact level for each mismatched computing aspect of the set of mismatched computing aspects respective to the cloud-based computing system platform by computing a weighted average of assigned threat values of the respective mismatched computing aspects.

8. The method of claim 5 , wherein determining the overall-computing aspect impact level for the set of associated computing aspects further comprises:

comparing, for each cloud-based computing system platform, the first set of computing aspects of a respective cloud-based computing system platform to the second set of computing aspects to determine a (i) matching set of computing aspects and (ii) a mismatched set of computing aspects, the matching set of computing aspects and the mismatched set of computing aspects representing the set of associated computing aspects;

obtaining, from a third-party security entity, a set of security-vulnerability descriptions, wherein each description of the set of security-vulnerability descriptions indicates at least one security threat associated with a respective computing aspect of the matching set of computing aspects respective to the cloud-based computing system platform;

assigning a threat value to each security-vulnerability description of the set of security-vulnerability descriptions by comparing a respective security-vulnerability description to a platform-specific policy, wherein the platform-specific policy includes security-vulnerability descriptions mapped to a respective threat level;

determining a computing aspect impact level for each matching computing aspect of the set of matching computing aspects respective to the cloud-based computing system platform by computing a weighted average of assigned threat values of the respective matching computing aspects;

assigning a placeholder computing aspect impact level for each mismatched computing aspect of the set of mismatched computing aspects respective to the cloud-based computing system platform; and

determining the overall-computing aspect impact levels for the set of associated computing aspects using (i) the computing aspect impact level of each matching computing aspect of the set of matching computing aspects and (ii) the placeholder computing aspect impact level for each mismatched computing aspect of the set of mismatched computing aspects, wherein the overall-computing aspect impact levels are respective cloud-based computing system platforms of the set of cloud-based computing system platforms.

9. The method of claim 5 , further comprising:

in response to detecting that the overall-computing aspect impact level for the set of associated computing aspects satisfies a threshold overall-computing aspect impact level, configuring a network component associated with an entity to process a second network operation via the cloud-based computing system platform associated with the satisfied overall-computing aspect impact level, wherein the set of associated computing aspects satisfying the threshold overall-computing aspect impact level is detected.

10. The method of claim 5 , wherein determining the overall-computing aspect impact level for the set of associated computing aspects further comprises:

applying a blackboard artificial intelligence model to generate the overall-computing aspect impact levels for the set of associated computing aspects by using (i) the first set of computing aspects associated with each cloud-based computing system platform (ii) the second set of computing aspects, and (iii) security-vulnerability descriptions obtained from a third-party security entity.

11. The method of claim 5 , wherein determining the first set of computing aspects associated with each cloud-based computing system platform of the set of cloud-based computing system platforms further comprises:

receiving response data from each respective cloud-based computing system platform based on the processing of the network operation, wherein the response data is a set of logging information returned by each respective cloud-based computing system platform in response to the network operation being processed.

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

detecting a network operation processing data between one computing system platform and a set of cloud-based computing system platforms;

determining a first set of computing aspects associated with each cloud-based computing system platform of the set of cloud-based computing system platforms based on the processing of the network operation;

identifying a second set of computing aspects associated with a comparative cloud-based computing system platform;

determining an overall-computing aspect impact level for a set of associated computing aspects between (i) the first set of computing aspects associated with each cloud-based computing system platform and (ii) the second set of computing aspects;

generating an output indicating a representation of each overall-computing aspect impact level of the set of associated computing aspects; and

in response to detecting that the overall-computing aspect impact level for the set of associated computing aspects satisfies a threshold overall-computing aspect impact level, configuring a network component associated with an entity to process a second network operation via the cloud-based computing system platform associated with the satisfied overall-computing aspect impact level.

13. The medium of claim 12 , wherein determining the overall-computing aspect impact level for the set of associated computing aspects further comprises:

comparing, for each cloud-based computing system platform, the first set of computing aspects of a respective cloud-based computing system platform to the second set of computing aspects to determine a matching set of computing aspects, the matching set of computing aspects representing the set of associated computing aspects;

obtaining, from a third-party security entity, a set of security-vulnerability descriptions, wherein each description of the set of security-vulnerability descriptions indicates at least one security threat associated with a respective computing aspect of the matching set of computing aspects;

assigning a threat value to each security-vulnerability description of the set of security-vulnerability descriptions by comparing a respective security-vulnerability description to a platform-specific policy, wherein the platform-specific policy includes security-vulnerability descriptions mapped to a respective threat level; and

determining the overall-computing aspect impact level for each matching computing aspect of the set of matching computing aspects respective to the cloud-based computing system platform by computing a weighted average of assigned threat values of the respective matching computing aspects.

14. The medium of claim 12 , wherein determining the overall-computing aspect impact level for the set of associated computing aspects further comprises:

comparing, for each cloud-based computing system platform, the first set of computing aspects of the respective cloud-based computing system platform to the second set of computing aspects to determine a mismatched set of computing aspects, the mismatched set of computing aspects representing the set of associated computing aspects;

obtaining, from a third-party security entity, a set of security-vulnerability descriptions, wherein each description of the set of security-vulnerability descriptions indicates at least one security threat associated with a respective computing aspect of the mismatched set of computing aspects;

assigning a threat value to each security-vulnerability description of the set of security-vulnerability descriptions by comparing a respective security-vulnerability description to a platform-specific policy, wherein the platform-specific policy includes security-vulnerability descriptions mapped to a respective threat level; and

determining the overall-computing aspect impact level for each mismatched computing aspect of the set of mismatched computing aspects respective to the cloud-based computing system platform by computing a weighted average of assigned threat values of the respective mismatched computing aspects.

15. The medium of claim 12 , wherein determining the overall-computing aspect impact level for the set of associated computing aspects further comprises:

comparing, for each cloud-based computing system platform, the first set of computing aspects of a respective cloud-based computing system platform to the second set of computing aspects to determine a (i) matching set of computing aspects and (ii) a mismatched set of computing aspects, the matching set of computing aspects and the mismatched set of computing aspects representing the set of associated computing aspects;

obtaining, from a third-party security entity, a set of security-vulnerability descriptions, wherein each description of the set of security-vulnerability descriptions indicates at least one security threat associated with a respective computing aspect of the matching set of computing aspects respective to the cloud-based computing system platform;

assigning a threat value to each security-vulnerability description of the set of security-vulnerability descriptions by comparing a respective security-vulnerability description to a platform-specific policy, wherein the platform-specific policy includes security-vulnerability descriptions mapped to a respective threat level;

determining a computing aspect impact level for each matching computing aspect of the set of matching computing aspects respective to the cloud-based computing system platform by computing a weighted average of assigned threat values of the respective matching computing aspects;

assigning a placeholder computing aspect impact level for each mismatched computing aspect of the set of mismatched computing aspects respective to the cloud-based computing system platform; and

determining the overall-computing aspect impact levels for the set of associated computing aspects using (i) the computing aspect impact level of each matching computing aspect of the set of matching computing aspects and (ii) the placeholder computing aspect impact level for each mismatched computing aspect of the set of mismatched computing aspects, wherein the overall-computing aspect impact levels are respective cloud-based computing system platforms of the set of cloud-based computing system platforms.

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

in response to detecting that a given overall-computing aspect impact level for a given associated computing aspect of the set of associated computing aspects satisfies a threshold overall-computing aspect impact level, configuring a network component associated with an entity to process a second network operation via the cloud-based computing system platform associated with the satisfied overall-computing aspect impact level.

17. The medium of claim 12 , wherein determining the overall-computing aspect impact level for the set of associated computing aspects further comprises:

applying a blackboard artificial intelligence model to generate the overall-computing aspect impact levels for the set of associated computing aspects by using (i) the first set of computing aspects associated with each cloud-based computing system platform (ii) the second set of computing aspects, and (iii) security-vulnerability descriptions obtained from a third-party security entity.

18. The medium of claim 12 , wherein determining the first set of computing aspects associated with each cloud-based computing system platform of the set of cloud-based computing system platforms further comprises:

receiving response data from each respective cloud-based computing system platform based on the processing of the network operation, wherein the response data is a set of logging information returned by each respective cloud-based computing system platform in response to the network operation being processed.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 12, 2024
From: RAO, PRITHVI NARAYANA; GOYAL, PRAMOD
To: CITIBANK, N.A.
Reel/Frame 067981/0612 →
Continuity (4)
Continuation 18327040 · May 31, 2023
Continuation In Part 18114194 · Feb 24, 2023
Continuation In Part 18098895 · Jan 19, 2023
Related Publication 20240256677A1 · Aug 1, 2024
References Cited (158)
US 8380817B2 · Okada · 2013 [cited by applicant]
US 8387020B1 · Maclachlan et al. · 2013 [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 11133942B1 · Griffin · 2021 [cited by applicant]
US 11227187B1 · Weinberger · 2022 [cited by applicant]
US 11290483B1 · Kannan · 2022 [cited by examiner]
US 11328068B1 · Niedzwiedz et al. · 2022 [cited by applicant]
US 11410136B2 · Cook et al. · 2022 [cited by applicant]
US 11516222B1 · Srinivasan et al. · 2022 [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 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-tabatabal et al. · 2014 [cited by applicant]
US 20170061132A1 · Hovor 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 20220078210A1 · Crabtree · 2022 [cited by examiner]
US 20220086162A1 · Badawy · 2022 [cited by examiner]
US 20220092953A1 · Krishnan · 2022 [cited by examiner]
US 20220100332A1 · Haworth · 2022 [cited by examiner]
US 20220101326A1 · Kim · 2022 [cited by examiner]
US 20220109685A1 · Hankins · 2022 [cited by examiner]
US 20220114251A1 · Guim Bernat et al. · 2022 [cited by applicant]
US 20220124115A1 · Grabois · 2022 [cited by examiner]
US 20220138327A1 · Panicker · 2022 [cited by examiner]
US 20220147636A1 · Mahuli et al. · 2022 [cited by applicant]
US 20220147815A1 · Conwell · 2022 [cited by examiner]
US 20220150275A1 · McNee · 2022 [cited by examiner]
US 20220164732A1 · Brannon et al. · 2022 [cited by applicant]
US 20220166789A1 · Murray et al. · 2022 [cited by applicant]
US 20220188460A1 · Hadar et al. · 2022 [cited by applicant]
US 20220191236A1 · Henderson · 2022 [cited by applicant]
US 20220201042A1 · Crabtree et al. · 2022 [cited by applicant]
US 20220210200A1 · Crabtree et al. · 2022 [cited by applicant]
US 20220210202A1 · Crabtree et al. · 2022 [cited by applicant]
US 20220222089A1 · Joshi et al. · 2022 [cited by applicant]
US 20220224702A1 · Dherange et al. · 2022 [cited by applicant]
US 20220224723A1 · Crabtree et al. · 2022 [cited by applicant]
US 20220237565A1 · Dzierzanowski et al. · 2022 [cited by applicant]
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 20220303352A1 · Herzog · 2022 [cited by examiner]
US 20220334818A1 · Mcfarland · 2022 [cited by applicant]
US 20220398149A1 · Mcfarland et al. · 2022 [cited by applicant]
US 20220405397A1 · Golan et al. · 2022 [cited by applicant]
US 20220417274A1 · Madanahalli et al. · 2022 [cited by applicant]
US 20230032686A1 · Williams et al. · 2023 [cited by applicant]
US 20230035321A1 · Vijayaraghavan · 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 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 20230169397A1 · Smith 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 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 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 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]
Cranium, Adopt & Accelerate AI Safely, retrieved on Nov. 7, 2024, from https://cranium.ai/. [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]
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]
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]