System and a method for managing knowledge for solving vulnerable issues using organizational knowledge base

A method for managing knowledge for solving vulnerability issues using an organizational knowledgebase, the method comprising the steps of:

• a. linking vulnerability management platform knowledgebase (KB) articles to an organization's core documents, thereby rendering information contained in the vulnerability management platform knowledgebase articles accessible through authoritative sources, including policy documents, guidelines, and technical specifications of the organization's core documents;
• b. applying a vulnerability management platform formula to enhance knowledge management and security practices within the organizational knowledgebase and wherein the step of applying the vulnerability management platform formula comprises the following steps:
• i. tagging at least one of common vulnerabilities and exposures (CVEs) and common weakness enumeration (CWEs) to the vulnerability management platform knowledgebase articles, and wherein the step of tagging at least one of the CVEs and the CWEs involves categorizing the vulnerability management platform knowledgebase articles with standardized identifiers that represent specific vulnerabilities or weaknesses, thereby enabling users to find articles related to specific security issues, and wherein the step of tagging at least one of the CVEs and the CWEs to the vulnerability management platform knowledgebase articles further includes the following steps:
• a. identifying at least one of the CVEs and the CWEs related to the organization's systems, software, and infrastructure, and identifying known vulnerabilities, weaknesses, and exposures likely to impact the organization's assets;
• b. reviewing existing vulnerability management platform knowledgebase articles to identify content that addresses at least one of identified CVEs and CWEs;
• c. adding a new vulnerability management platform knowledgebase article in an event any of the existing vulnerability management platform knowledgebase articles do not cover an identified vulnerability;
• d. linking related CVEs and related CWEs with corresponding vulnerability management platform knowledgebase articles that have been reviewed;
• e. establishing a standardized taxonomy to tag and link the related CVEs and the related CWEs to the corresponding vulnerability management platform knowledgebase articles, such that the standardized taxonomy aligns with the standardized identifiers, said standardized identifiers including CVE identifiers and CWE identifiers;
• and
• f. verifying that a link between the related CVEs and the related CWEs and the corresponding vulnerability management platform knowledgebase articles is accurate, and thereby enabling the users to search for and find specific CVEs, specific CWEs, and specific vulnerability management platform knowledgebase articles;
• ii. attaching rich articles as links to a ticket tracking system;
• iii. linking the vulnerability management platform knowledgebase articles to a newly created ticket;
• and
• iv. automatically linking a code commit to the vulnerability management platform knowledgebase articles;
• c. defining and configuring a plurality of Service Level Agreements (SLAs) on at least one of an application level and a sub-application level to set timelines for acknowledging and mitigating security concerns.