Method and system for managing application vulnerabilities

Patent metadata

Field	Value
Publication number	US-12034762-B2
Application number	US-202217659207-A
Country	US
Kind code	B2
Filing date	Apr 14, 2022
Priority date	Mar 2, 2022
Publication date	Jul 9, 2024
Grant date	Jul 9, 2024

Abstract

A method for providing vulnerability management to facilitate application development and deployment is disclosed. The method includes receiving a monitoring request that includes an identifier, the identifier corresponding to an application; onboarding the application by using the identifier; generating a scheduled task for the application based on an outcome of the onboarding, the scheduled task relating to source code vulnerability analytics; automatically initiating, via an application programming interface, the scheduled task based on a predetermined parameter; determining whether a set of source codes that corresponds to the application includes a vulnerability based on a result of the automatically initiated scheduled task; and generating a ticket when the vulnerability is included in the set of source codes.

First claim

What is claimed is:

1. A method for providing vulnerability management to facilitate application development and deployment, the method being implemented by at least one processor, the method comprising:
receiving, by the at least one processor, at least one monitoring request that includes at least one identifier, the at least one identifier corresponding to an application;
onboarding, by the at least one processor, the application by using the at least one identifier;
generating, by the at least one processor, at least one scheduled task for the application based on an outcome of the onboarding, the at least one scheduled task relating to source code vulnerability analytics;
automatically initiating, by the at least one processor via an application programming interface, the at least one scheduled task based on a predetermined parameter;
determining, by the at least one processor, whether a set of source codes that corresponds to the application includes at least one vulnerability based on a result of the automatically initiated at least one scheduled task; and
generating, by the at least one processor, at least one ticket when the at least one vulnerability is included in the set of source codes.

2. The method of claim 1 , wherein the at least one ticket relates to a work item of a responsible party associated with the application, the work item corresponding to an activity in a backlog that is managed by the responsible party.

3. The method of claim 1 , wherein the at least one ticket includes a standardized template that facilitates issue tracking and monitoring, the standardized template including vulnerability detection tool information, vulnerability labeling information, and developer assignment information.

4. The method of claim 1 , further comprising:
identifying, by the at least one processor, at least one labeling strategy for the application based on the at least one vulnerability and a severity level;
generating, by the at least one processor, at least one graphical element for the application, the at least one graphical element including a dashboard that contains information from the at least one ticket and the at least one labeling strategy; and
displaying, by the at least one processor via a graphical user interface, the at least one graphical element.

5. The method of claim 1 , further comprising:
compiling, by the at least one processor, data that relates to at least one from among the application and the at least one vulnerability, the data including deadline information relating to resolution of the at least one vulnerability; and
updating, by the at least one processor, the at least one ticket to include the data.

6. The method of claim 1 , further comprising:
automatically determining, by the at least one processor using at least one model, at least one mitigation action that relates to the at least one vulnerability; and
updating, by the at least one processor, the at least one ticket to include information that relates to the at least one mitigation action.

7. The method of claim 6 , further comprising:
automatically initiating, by the at least one processor, the at least one mitigation action based on a predetermined user setting; and
generating, by the at least one processor, at least one execution report, the at least one execution report including data that corresponds to the automatic determining of the at least one mitigation action and the automatic initiating of the at least one mitigation action.

8. The method of claim 1 , further comprising:
automatically determining, by the at least one processor, whether at least one pull request that relates to the at least one vulnerability is generated, the at least one pull request relating to a previously generated mitigation action for the at least one vulnerability;
associating, by the at least one processor, the at least one pull request with the at least one ticket when the at least one pull request is generated; and
updating, by the at least one processor, the at least one ticket to include information that relates to the at least one pull request.

9. The method of claim 1 , wherein onboarding the application further comprises:
pulling, by the at least one processor using the application programming interface, data that corresponds to the application based on the at least one identifier;
requesting, by the at least one processor via a graphical user interface, at least one privilege setting that corresponds to the application, the at least one privilege setting including at least one from among a scanning privilege setting and a reading privilege setting;
generating, by the at least one processor, a configuration file that corresponds to the application based on the pulled data and the at least one privilege setting; and
persisting, by the at least one processor, the configuration file in a source code repository that is hosting the application.

10. A computing device configured to implement an execution of a method for providing vulnerability management to facilitate application development and deployment, the computing device comprising:
a processor;
a memory; and
a communication interface coupled to each of the processor and the memory,
wherein the processor is configured to:
receive at least one monitoring request that includes at least one identifier, the at least one identifier corresponding to an application;
onboard the application by using the at least one identifier;
generate at least one scheduled task for the application based on an outcome of the onboarding, the at least one scheduled task relating to source code vulnerability analytics;
automatically initiate, via an application programming interface, the at least one scheduled task based on a predetermined parameter;
determine whether a set of source codes that corresponds to the application includes at least one vulnerability based on a result of the automatically initiated at least one scheduled task; and
generate at least one ticket when the at least one vulnerability is included in the set of source codes.

11. The computing device of claim 10 , wherein the at least one ticket relates to a work item of a responsible party associated with the application, the work item corresponding to an activity in a backlog that is managed by the responsible party.

12. The computing device of claim 10 , wherein the at least one ticket includes a standardized template that facilitates issue tracking and monitoring, the standardized template including vulnerability detection tool information, vulnerability labeling information, and developer assignment information.

13. The computing device of claim 10 , wherein the processor is further configured to:
identify at least one labeling strategy for the application based on the at least one vulnerability and a severity level;
generate at least one graphical element for the application, the at least one graphical element including a dashboard that contains information from the at least one ticket and the at least one labeling strategy; and
display, via a graphical user interface, the at least one graphical element.

14. The computing device of claim 10 , wherein the processor is further configured to:
compile data that relates to at least one from among the application and the at least one vulnerability, the data including deadline information relating to resolution of the at least one vulnerability; and
update the at least one ticket to include the data.

15. The computing device of claim 10 , wherein the processor is further configured to:
automatically determine, by using at least one m

Assignees

• Jpmorgan Chase Bank Na

Inventors

• Block Monika T S
• Kotwal Animesh
• Shah Purvesh
• Murthy Shamanth
• Lakshmi Magesh

Classifications

• H04L63/1425

  Traffic logging, e.g. anomaly detection · CPC title

• H04L63/1416

  Event detection, e.g. attack signature detection · CPC title

• H04L63/1433 Primary

  Vulnerability analysis · CPC title