Abstract: The embodiments herein provide a method and a system for developer identification and ticket assignment. The method comprises applying owner identification logics through a plurality of application security testing methodologies such as SAST, DAST and SCA tool. The method further comprises making an API call through a vulnerability management platform to a code repository to identify the developer who has changed the portion of the code recently; assigning a ticket to the identified developer and saving the developer in the vulnerability management platform; viewing the status of the ticket through various options such as insight view, CTO view, Engineering Manager view and Developer view; and providing training requirements and assessing the effectiveness of training.

Abstract: The embodiments herein provide a method for managing knowledge for solving vulnerability issues using an organizational knowledgebase. The method includes linking a vulnerability management platform knowledgebase (KB) article to an organization's core documents. The method further includes applying a vulnerability management platform formula, to enhance the knowledge management and security practices within the organization's knowledgebase. The method for applying the vulnerability management platform formula comprises tagging (CVEs) or (CWEs), to the vulnerability platform knowledgebase (KB) articles; attaching rich articles as links to a ticket tracking system; linking the vulnerability management platform KB articles to a new ticket created; and automatically linking a code commit to the vulnerability management platform KB articles.

Abstract: The embodiments herein provide a method and a system for security risk identification and controlling release management of software application. The method provides security risk identification in a software application as well as integrated tools to direct the efforts of developers to build and maintain secure software. The method provides a unique approach of defining a plurality of Service Level Agreement (SLA) to control a release build for a software application by checking vulnerabilities. Furthermore, the method is flexible enough to adapt in most complicated enterprises and different Software Development Life Cycle (SDLC) processes.