Methods for detecting and mitigating malicious network activity based on dynamic application context and devices thereof
US-2020186563-A1 · Jun 11, 2020 · US
US12536302B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12536302-B2 |
| Application number | US-202318457420-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 29, 2023 |
| Priority date | Aug 29, 2023 |
| Publication date | Jan 27, 2026 |
| Grant date | Jan 27, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An example computer system for live threat modeling for an enterprise can include: one or more processors; and non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to: prepare abstracts for applications associated with the enterprise to form a threat model; monitor development phases of the applications; and apply the threat model to the applications during each of the development phases to identify risk.
Opening claim text (preview).
What is claimed is: 1 . A computer system for live threat modeling for an enterprise, comprising: one or more processors; and non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to: prepare abstracts for applications associated with the enterprise to form a threat model, wherein the abstracts are dynamic structured data representations of the applications throughout development phases of the applications; monitor the development phases of the applications; apply the threat model to incremental changes to the applications as defined by the abstracts during each of the development phases to identify risk; and automatically update the threat model through one or more calls to an application programming interface in near-real time using the abstracts. 2 . The computer system of claim 1 , wherein the abstracts define build information for the applications, functionality associated with the applications, and dependencies associated with the applications. 3 . The computer system of claim 1 , wherein the threat model is stored in a database, and the database is automatically updated. 4 . The computer system of claim 1 , wherein the development phases include: a design phase during which the applications are coded; a build phase during which the applications are compiled; and a deployment phase during which the applications are introduced into a production environment. 5 . The computer system of claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to generate a dashboard to provide threat information associated with the enterprise. 6 . The computer system of claim 5 , wherein the dashboard includes one or more menus to filter the threat information. 7 . The computer system of claim 6 , wherein the one or more menus include a first menu to filter by line of business and a second menu to filter by one or more of the applications. 8 . The computer system of claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to mitigate the risk associated with the applications. 9 . A method for live threat modeling for an enterprise, comprising: preparing abstracts for applications associated with the enterprise to form a threat model, wherein the abstracts are dynamic structured data representations of the applications throughout development phases of the applications; monitoring the development phases of the applications; applying the threat model to incremental changes to the applications as defined by the abstracts during each of the development phases to identify risk; and automatically updating the threat model through one or more calls to an application programming interface in near-real time using the abstracts. 10 . The method of claim 9 , wherein the abstracts define build information for the applications, functionality associated with the applications, and dependencies associated with the applications. 11 . The method of claim 9 , wherein the threat model is stored in a database, and the database is automatically updated. 12 . The method of claim 9 , wherein the development phases include: a design phase during which the applications are coded; a build phase during which the applications are compiled; and a deployment phase during which the applications are introduced into a production environment. 13 . The method of claim 9 , further comprising generating a dashboard to provide threat information associated with the enterprise. 14 . The method of claim 13 , wherein the dashboard includes one or more menus to filter the threat information. 15 . The method of claim 14 , wherein the one or more menus include a first menu to filter by line of business and a second menu to filter by one or more of the applications. 16 . The method of claim 9 , further comprising mitigating the risk associated with the applications.
Test or assess software · CPC title
Software metrics · CPC title
Assessing vulnerabilities and evaluating computer system security · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.