Security vulnerability grading evaluation method and device, equipment and storage medium
By combining the two dimensions of vulnerability technology difficulty and asset importance, the network security vulnerabilities are graded and evaluated, which solves the problem of low accuracy of vulnerability assessment in the existing technology and achieves more accurate risk assessment and assessment.
Patent Information
- Application Number
- CN202410927314.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-11
- Publication Date
- 2024-11-12
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The existing rules for the division of risk levels of network security vulnerabilities only consider the technical difficulty of security vulnerabilities and fail to fully consider the internal environmental factors of the business system, resulting in low accuracy in vulnerability rating evaluation and unable to meet the actual needs of the business system.
Evaluate the technical difficulty of a security vulnerability being triggered and the importance of assets affected by a security vulnerability in the target business system, and combine the general technical dimensions and proprietary business dimensions to rank the vulnerability and use computer equipment and storage Media achieves matching vulnerability technology grading and asset importance grading.
The accuracy of vulnerability rating assessment is improved, so that the evaluation results can better reflect the specific risk needs of the business system, and enhance the pertinence and accuracy of vulnerability assessment.
Smart Images

Figure CN118940273A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network security technology, and in particular to a security vulnerability grading and assessment method, device, equipment and storage medium. Background Art
[0002] Business systems such as credit reporting systems and corporate internal management systems often require regular vulnerability scans to ensure the normal operation and security of the business systems, so as to promptly discover security vulnerabilities in the business systems.
[0003] At present, for the security vulnerabilities scanned in the business system, the security vulnerability level to which the security vulnerability belongs is usually assessed according to the general network security vulnerability risk level classification rules. However, since the general network security vulnerability risk level classification rules only consider the technical difficulty of triggering the security vulnerability, and do not take into account the internal environmental factors of the business system operation, the accuracy of the security vulnerability grading assessment results is low, which cannot meet the actual vulnerability rating needs of the business system. Summary of the invention
[0004] In view of this, the purpose of the present application is to provide a security vulnerability rating and assessment method, apparatus, equipment and storage medium, which respectively classifies and assesses the security vulnerabilities scanned in the target business system from two main assessment dimensions: the technical difficulty of triggering the security vulnerability and the importance of the assets affected by the security vulnerability in the target business system. The final rating and assessment results can not only reflect the security risks of the security vulnerabilities in the general technical dimension, but also reflect the security risks of the security vulnerabilities in the proprietary business dimension corresponding to the target business system. This allows the security vulnerability rating and assessment results to match the specific risk assessment requirements of the target business system, which is conducive to improving the accuracy of the security vulnerability rating and assessment.
[0005] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings.
[0006] In a first aspect, an embodiment of the present application provides a method for grading and evaluating a security vulnerability, the method comprising:
[0007] For the security vulnerabilities scanned in the target business system, according to the vulnerability description information of the security vulnerability, from multiple vulnerability classifications under the technical assessment dimension, determine the vulnerability classification whose classification description information matches the vulnerability description information as the vulnerability technical classification corresponding to the security vulnerability under the technical assessment dimension;
[0008] According to the target asset associated with the security vulnerability, determine, from multiple asset classifications under the asset evaluation dimension, an asset classification whose classification description information matches the asset description information of the target asset as the asset importance classification corresponding to the security vulnerability under the asset evaluation dimension; wherein the target asset represents an asset in the target business system that is affected by the security vulnerability;
[0009] The security vulnerability level to which the security vulnerability belongs is determined based on the vulnerability technology classification and the asset importance classification.
[0010] In a second aspect, an embodiment of the present application provides a security vulnerability rating and assessment device, the rating and assessment device comprising:
[0011] A first grading module is used to determine, for a security vulnerability scanned in a target business system, based on vulnerability description information of the security vulnerability, from multiple vulnerability grades under a technical assessment dimension, a vulnerability grade whose grade description information matches the vulnerability description information as the vulnerability technical grade corresponding to the security vulnerability under the technical assessment dimension;
[0012] A second classification module is used to determine, according to the target asset associated with the security vulnerability, from multiple asset classifications under the asset evaluation dimension, an asset classification whose classification description information matches the asset description information of the target asset as the asset importance classification corresponding to the security vulnerability under the asset evaluation dimension; wherein the target asset represents an asset in the target business system that is affected by the security vulnerability;
[0013] The grading assessment module is used to determine the security vulnerability level to which the security vulnerability belongs based on the vulnerability technology grading and the asset importance grading.
[0014] In a third aspect, an embodiment of the present application provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above-mentioned security vulnerability rating assessment method when executing the computer program.
[0015] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned security vulnerability rating assessment method are executed.
[0016] The technical solution provided by the embodiments of the present application may have the following beneficial effects:
[0017] The embodiments of the present application provide a method, apparatus, device and storage medium for grading and assessing a security vulnerability scanned in a target business system. For a security vulnerability scanned in a target business system, based on the vulnerability description information of the security vulnerability, from multiple vulnerability classifications under a technical assessment dimension, a vulnerability classification whose graded description information matches the vulnerability description information is determined as the vulnerability technical classification of the security vulnerability; based on a target asset associated with the security vulnerability, from multiple asset classifications under an asset assessment dimension, an asset classification whose graded description information matches the asset description information of the target asset is determined as the asset importance classification of the security vulnerability; and based on the vulnerability technical classification and the asset importance classification, the security vulnerability level to which the security vulnerability belongs is determined.
[0018] In this way, the present application classifies and evaluates the security vulnerabilities scanned in the target business system from two main evaluation dimensions: the technical difficulty of triggering the security vulnerability and the importance of the assets affected by the security vulnerability in the target business system. The final classification and evaluation results can not only reflect the security risks of the security vulnerabilities in the general technical dimension, but also reflect the security risks of the security vulnerabilities in the proprietary business dimension corresponding to the target business system. In this way, the classification and evaluation results of the security vulnerabilities can match the specific risk assessment requirements of the target business system, which is conducive to improving the accuracy of the security vulnerability classification and evaluation. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0020] Figure 1 A schematic diagram of a process for evaluating a security vulnerability provided by an embodiment of the present application is shown;
[0021] Figure 2 A schematic diagram of a process for determining a vulnerability technology classification corresponding to a security vulnerability under a technical assessment dimension provided by an embodiment of the present application is shown;
[0022] Figure 3 A flow chart of a method for determining the asset importance classification corresponding to a security vulnerability in the asset assessment dimension provided by an embodiment of the present application is shown;
[0023] Figure 4 A schematic diagram of the structure of a security vulnerability rating and assessment device provided in an embodiment of the present application is shown;
[0024] Figure 5A schematic diagram of the structure of an electronic device 500 provided in an embodiment of the present application. DETAILED DESCRIPTION
[0025] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of sequence, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of the present application, or remove one or more operations from the flowchart.
[0026] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.
[0027] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.
[0028] At present, for the security vulnerabilities scanned in the business system, the security vulnerability level to which the security vulnerability belongs is usually assessed according to the general network security vulnerability risk level classification rules. However, since the general network security vulnerability risk level classification rules only consider the technical difficulty of triggering the security vulnerability, and do not take into account the internal environmental factors of the business system operation, the accuracy of the security vulnerability grading assessment results is low, which cannot meet the actual vulnerability rating needs of the business system.
[0029] Based on this, the embodiments of the present application provide a method, apparatus, device and storage medium for rating and evaluating security vulnerabilities, which respectively rate and evaluate security vulnerabilities scanned in the target business system from two main evaluation dimensions: the technical difficulty of triggering the security vulnerability and the importance of assets affected by the security vulnerability in the target business system. The final rating and evaluation results can not only reflect the security risks of the security vulnerabilities in the general technical dimension, but also reflect the security risks of the security vulnerabilities in the proprietary business dimension corresponding to the target business system. This allows the rating and evaluation results of the security vulnerabilities to match the specific risk assessment requirements of the target business system, which is conducive to improving the accuracy of the security vulnerability rating and evaluation.
[0030] To facilitate understanding of the embodiments of the present application, a security vulnerability rating assessment method, apparatus, device and storage medium provided in the embodiments of the present application are described in detail below.
[0031] Reference Figure 1 As shown, Figure 1 A schematic flow chart of a security vulnerability rating and evaluation method provided in an embodiment of the present application is shown, wherein the rating and evaluation method comprises steps S101-S103; specifically:
[0032] S101, for the security vulnerability scanned in the target business system, according to the vulnerability description information of the security vulnerability, from multiple vulnerability classifications under the technical assessment dimension, determine the vulnerability classification whose classification description information matches the vulnerability description information as the vulnerability technical classification corresponding to the security vulnerability under the technical assessment dimension.
[0033] Here, the target business system represents a business application system used to carry out the target business; wherein, the specific target business corresponding to the target business system can be determined based on the actual business development content of the company; for example, the target business system may include but is not limited to: a credit reporting system (mainly used to store the user's credit information, so as to provide the user's credit information to the relevant financial institutions when they need to assess the user's credit risk), a credit system (the corresponding target business is the credit business), an insurance system (the corresponding target business is the insurance business) and other business application systems; for the specific business application system type to which the above-mentioned target business system belongs (which is also equivalent to the business type to which the above-mentioned target business belongs), the embodiments of the present application do not impose mandatory restrictions.
[0034] Specifically, within the company, the vulnerability discoverer (i.e., the staff member in the company who is responsible for performing security vulnerability scans) can perform security vulnerability scans on the target business system (i.e., detect and analyze whether there are security vulnerabilities in the target business system, determine the authenticity of the existence of the security vulnerabilities, etc.) manually (e.g., manually start the security vulnerability scanning program, which is equivalent to the security vulnerability scanning time being determined manually according to the vulnerability scanning needs) or automatically (e.g., set the security vulnerability scanning program to perform regular scans of the target business system at preset time intervals). When it is determined that a security vulnerability has been scanned in the target business system, the vulnerability description information of the scanned security vulnerability can be reported to the security group (i.e., the vulnerability discoverer can package the vulnerability description information of the scanned security vulnerability and send it to the management terminal corresponding to the security group).
[0035] In an embodiment of the present application, the vulnerability description information of a security vulnerability can be divided into the following two types: Type 1, description information related to the security vulnerability itself (such as the triggering method, triggering conditions, triggering permissions, and the impact that the security vulnerability may have on the target business system after being triggered, etc.); Type 2, description information related to the target assets associated with the security vulnerability in the target business system; wherein, the target assets represent the assets in the target business system that are affected by the security vulnerability (assets include but are not limited to: data assets such as information data stored in the target business system, and equipment assets such as various software and hardware equipment in the target business system).
[0036] Here, for each security vulnerability scanned in the target business system, considering that the general network security vulnerability risk level classification rules also classify and evaluate security vulnerabilities from a technical dimension, therefore, when determining the vulnerability technical level corresponding to a security vulnerability from the technical evaluation dimension, it is possible to refer to the general network security vulnerability risk level classification rules (for example, the classification provisions in the "GB / T30279-2020 Information Security Technology Network Security Vulnerability Classification and Grading Guide"), combined with the business characteristics of the target business system itself (such as the characteristics of the system operation and maintenance environment, the business process characteristics of the target business, etc.) and the impact that the security vulnerability may have on the target business system (that is, the harm that the security vulnerability may cause to the target business system after being triggered), pre-set multiple vulnerability levels under the above technical evaluation dimension and the classification description information of each vulnerability classification (equivalent to the specific definition of the vulnerability classification), so that the vulnerability description information of the security vulnerability (mainly the "description information related to the security vulnerability itself" corresponding to the above type 1) can be compared with the classification description information of each vulnerability classification under the above technical evaluation dimension, and the vulnerability classification whose classification description information matches the above vulnerability description information is determined as the vulnerability technical classification corresponding to the security vulnerability under the above technical evaluation dimension.
[0037] S102, according to the target asset associated with the security vulnerability, determine, from multiple asset classifications under the asset evaluation dimension, an asset classification whose classification description information matches the asset description information of the target asset as the asset importance classification corresponding to the security vulnerability under the asset evaluation dimension.
[0038] Here, in combination with the relevant instructions in the above step S101, it can be seen that the target assets associated with the security vulnerability can represent the assets in the target business system that are affected by the security vulnerability; wherein, the target assets may include but are not limited to: data assets such as information data stored in the target business system, and equipment assets such as various software and hardware equipment in the target business system; the specific asset type to which the above target assets belong is not mandatory in the embodiments of this application.
[0039] Specifically, unlike the general network security vulnerability risk level classification rules that only consider the grading and assessment results of security vulnerabilities in the technical dimension, in the embodiment of the present application, in addition to determining the vulnerability technical level corresponding to the scanned security vulnerability in the above-mentioned technical assessment dimension according to the method described in the above-mentioned step S101, it is also possible to evaluate the asset importance of the above-mentioned target assets associated with the security vulnerability in the target business system from the asset assessment dimension according to the vulnerability description information of the security vulnerability (mainly the "description information related to the target assets associated with the security vulnerability in the target business system" in the above-mentioned type 2, which is also equivalent to the asset description information of the target assets), and obtain the asset importance level corresponding to the security vulnerability in the above-mentioned asset assessment dimension, so that the final grading and assessment results of the security vulnerability can better match the specific risk assessment requirements of the target business system (equivalent to the fact that based on the existence of the above-mentioned asset importance grading, the final grading and assessment results of the security vulnerability can effectively reflect the future security risks of the target assets affected by the security vulnerability).
[0040] Specifically, similar to the multiple vulnerability classifications under the above-mentioned technical assessment dimension, under the asset assessment dimension, it is also possible to pre-set multiple asset classifications under the above-mentioned asset assessment dimension and the classification description information of each asset classification (equivalent to the specific definition of the asset classification) in combination with the business characteristics of the target business system itself, so that the vulnerability description information of the security vulnerability (mainly the "description information related to the target assets associated with the security vulnerability in the target business system" in the above-mentioned type 2, which is also equivalent to the asset description information of the target asset) and the classification description information of each asset classification under the above-mentioned asset assessment dimension can be compared, and the asset classification whose classification description information matches the asset description information of the above-mentioned target asset is determined as the asset importance classification corresponding to the security vulnerability under the above-mentioned asset assessment dimension.
[0041] S103, determining the security vulnerability level to which the security vulnerability belongs according to the vulnerability technology classification and the asset importance classification.
[0042] Here, as an optional embodiment, it can be considered that the above-mentioned technical evaluation dimension and the above-mentioned asset evaluation dimension play an equally important role in the rating and evaluation of security vulnerabilities. At this time, when determining the final rating and evaluation result of the security vulnerability (that is, the security vulnerability level to which the security vulnerability belongs), there is no difference in weight between the above-mentioned vulnerability technical classification and the above-mentioned asset importance classification of the security vulnerability. The final rating and evaluation result of the security vulnerability can be determined according to the method described in step a1 below, specifically:
[0043] Step a1: using the vulnerability technology classification and the asset importance classification corresponding to the security vulnerability as target index information, and retrieving the security vulnerability rating whose location information matches the target index information from a pre-stored security vulnerability rating list as the security vulnerability level to which the security vulnerability belongs; wherein the security vulnerability rating list contains multiple security vulnerability ratings.
[0044] Specifically, before executing the grading and assessment method described in the above steps S101-S103, a vulnerability rating list for determining the final grading and assessment results of security vulnerabilities can be pre-created and stored in a manner that each vulnerability grade under the above technical assessment dimension corresponds to a column (or a row) in the vulnerability rating list, and each asset grade under the above asset assessment dimension corresponds to a row (or a column) in the vulnerability rating list; wherein, in the created vulnerability rating list, the security vulnerability rating corresponding to each cross-item (i.e., the cross-item of the above vulnerability grade and the above asset grade in the vulnerability rating list) can be set in sequence according to the diagonal direction (equivalent to the above vulnerability grade and the above asset grade in the vulnerability rating list being comprehensively sorted from high to low), so that, after determining the above vulnerability technical grade and the above asset importance grade of a security vulnerability, the security vulnerability level to which the security vulnerability belongs can be determined directly from the above vulnerability rating list by looking up a table.
[0045] For example, the multiple vulnerabilities in the above technical assessment dimension are classified as: very dangerous, high risk, medium risk, and low risk, and the multiple assets in the above asset assessment dimension are classified as: level 5, level 4, level 3, level 2, and level 1 (the larger the level, the more important the asset), and the vulnerability rating list can be shown in Table 1 below:
[0046]
[0047] Table 1
[0048] Here, as another optional embodiment, the rating weights corresponding to the above-mentioned technical assessment dimension and the above-mentioned asset assessment dimension can also be pre-configured according to the actual vulnerability rating and assessment requirements of the target business system. At this time, when determining the final rating and assessment result of the security vulnerability (that is, the security vulnerability level to which the security vulnerability belongs), the above-mentioned vulnerability technology classification and the above-mentioned asset importance classification of the security vulnerability can be weightedly summed according to the rating weights corresponding to the above-mentioned technical assessment dimension and the above-mentioned asset assessment dimension to obtain a weighted summation result, and based on the weighted summation result, the security risk level where the above-mentioned weighted summation result is located can be determined from a plurality of pre-set security risk levels as the final rating and assessment result of the security vulnerability.
[0049] As an exemplary explanation, taking the multiple vulnerability classifications under the above-mentioned technical assessment dimension as follows: level 4, level 3, level 2, level 1, and the multiple asset classifications under the above-mentioned asset assessment dimension as follows: level 5, level 4, level 3, level 2, level 1 (the larger the level, the more important the asset), as an example, if the grading weight corresponding to the above-mentioned technical assessment dimension is 0.6 and the grading weight corresponding to the above-mentioned asset assessment dimension is 0.4, then when the vulnerability technical classification of the security vulnerability is level 4 and the asset importance classification is level 5, the weighted summation result corresponding to the security vulnerability can be calculated to be level 4.4 by weighted summation, and from the pre-set multiple security risk levels of “ultra-high risk” (the weighted summation result is between levels 4-5), “high risk” (the weighted summation result is between levels 3-4), “medium risk” (the weighted summation result is between levels 2-3), and low risk (the weighted summation result is below level 2), the security risk level “ultra-high risk” where the weighted summation result of level 4.4 is located is determined as the final grading assessment result of the security vulnerability (that is, the security vulnerability level to which the security vulnerability belongs).
[0050] Taking the target business system as a credit reporting system as an example, the specific implementation process of the above steps S101-S103 is described in detail below:
[0051] Regarding the specific implementation process of the above-mentioned step S101, in an optional implementation manner, a specific definition of each vulnerability classification under the technical assessment dimension (i.e., the classification description information of each vulnerability classification) can be given in the form of text information, and by comparing the vulnerability description information of the security vulnerability with the classification description information of each vulnerability classification, from multiple vulnerability classifications, the vulnerability classification whose classification description information matches the vulnerability description information (i.e., the highest degree of information overlap) is determined as the vulnerability technical classification corresponding to the security vulnerability under the above-mentioned technical assessment dimension.
[0052] In the embodiment of the present application, when the target business system belongs to the credit reporting system, under the technical evaluation dimension, four vulnerability classifications can be included: "ultra-risk" (i.e., ultra-high risk), "high risk" (i.e., high risk), "medium risk" (i.e., medium risk), and "low risk" (i.e., low risk). The specific classification description information of each vulnerability classification is as follows:
[0053] Extremely critical: A vulnerability that can easily cause particularly serious consequences to the target object (i.e., target asset). The specific classification description information is as follows:
[0054] 1. Vulnerabilities that directly obtain the permissions of the core server (core server of the target business system), including but not limited to: uploading Webshell (script Trojan), arbitrary code execution, remote command execution, etc.;
[0055] 2. Serious information leakage vulnerabilities of the core system (core system of the target business system), including but not limited to SQL (Structured Query Language) injection (a network attack method) of the core database, leakage of a large number of users' serious sensitive identity information (including at least 3 sensitive fields, sensitive fields can be: name / ID card, bank card information, mobile phone number / email, password, address), leakage of core data within the enterprise, etc.;
[0056] 3. Serious logical design or process defects in the core system, including but not limited to: batch modification of arbitrary account password loopholes, etc.;
[0057] 4. Vulnerabilities that seriously affect the availability of core systems, such as denial of service vulnerabilities that can directly paralyze core system operations.
[0058] High risk: Vulnerabilities that can easily cause serious consequences to the target object. The specific classification description information is as follows:
[0059] 1. Vulnerabilities that directly obtain permissions for important business servers (business servers in the target business system), including but not limited to: arbitrary command execution, webshell upload, and arbitrary code execution;
[0060] 2. Security vulnerabilities that directly lead to important information leakage in the target business system, including but not limited to: SQL injection vulnerabilities in important databases and leakage of a large number of source codes of important businesses;
[0061] 3. Serious unauthorized access, including but not limited to: bypassing authentication to access important system backends (i.e., the backends of important systems in the target business system), and stealing important identity information of users in batches;
[0062] 4. Serious logical design or process defects, including but not limited to: arbitrary password reset vulnerabilities in important systems;
[0063] Medium risk: vulnerabilities that can cause general consequences to the target object, or cause serious consequences to the target object with difficulty. The specific classification description information is as follows:
[0064] 1. Vulnerabilities that require interaction to obtain user identity information, including but not limited to: core and important system storage XSS (Cross-Site Scripting) vulnerabilities;
[0065] 2. Any file operation vulnerability, including but not limited to: any file read, write, delete, download, etc.;
[0066] 3. Ordinary unauthorized access, including but not limited to: bypassing restrictions to modify user information, perform user operations, read user information, and bypassing restrictions to access non-important system backgrounds;
[0067] 4. Relatively serious information leakage vulnerabilities, including but not limited to: leakage of sensitive information files (such as leakage of database connection passwords).
[0068] Low risk: Vulnerabilities that can cause minor consequences to the target object, or relatively difficult to cause moderately serious consequences to the target object, or very difficult to cause serious consequences to the target object. The specific classification description information is as follows:
[0069] 1. Reflected XSS, non-important system storage XSS;
[0070] 2. CSRF (Cross-site request forgery) of sensitive operations, URL (Uniform Resource Locator) jump, and unauthorized operations with limited harm;
[0071] 3. Minor information leakage, including but not limited to: information leakage of non-core systems, leakage of non-important information (such as unusable database connection passwords, etc.), and local SQL injection in client applications;
[0072] 4. Vulnerabilities that are difficult to exploit but pose security risks, including but not limited to: difficult-to-exploit SQL injection points and client local denial of service.
[0073] Regarding the specific implementation process of the above-mentioned step S101, in another optional implementation, each of the above-mentioned vulnerability grades can also be defined under the technical evaluation dimension from two subdimensions: the technical difficulty of triggering the security vulnerability and the degree of impact on the target business system after the security vulnerability is triggered. At this time, the classification description information of each of the above-mentioned vulnerability grades can be referred to, and the evaluation indicators related to the above-mentioned two subdimensions can be extracted from the above-mentioned classification description information, and the specific indicator value of each evaluation indicator corresponding to the security vulnerability can be determined according to the vulnerability description information of the security vulnerability, so as to quantify the matching degree between the vulnerability description information representing the security vulnerability and the classification description information of each of the above-mentioned vulnerability grades through these indicator values, which is conducive to improving the accuracy of the grading evaluation of security vulnerabilities under the technical evaluation dimension.
[0074] Here, in the above optional implementation, Figure 2 A flow chart of a method for determining a vulnerability technology classification corresponding to a security vulnerability under a technical assessment dimension provided in an embodiment of the present application is shown, such as Figure 2 As shown, during the execution of the above step S101, the method includes steps S201-S203, specifically:
[0075] S201, according to the vulnerability description information of the security vulnerability, determine, from the multiple exploitability classifications under the technical assessment dimension, the exploitability classification whose classification description information matches the vulnerability description information as the target exploitability classification corresponding to the security vulnerability.
[0076] Here, the target exploitability rating is used to characterize the technical difficulty of triggering the security vulnerability; among them, under the technical evaluation dimension, the exploitability rating reflects the technical possibility of triggering the security vulnerability (equivalent to the technical difficulty of triggering a security vulnerability).
[0077] Specifically, in order to evaluate the technical difficulty of triggering a security vulnerability (that is, to determine the target exploitability grade corresponding to a security vulnerability), multiple exploitability indicators (that is, indicators used to measure the technical difficulty of triggering a security vulnerability) can be preset. The preset multiple exploitability indicators can be used as an exploitability indicator group, and the combination of different values of each exploitability indicator in the exploitability indicator group corresponds to different exploitability grades. At this time, it is only necessary to determine the specific indicator value of each exploitability indicator corresponding to the security vulnerability based on the vulnerability description information of the security vulnerability, and then according to the specific combination of these indicator values, the target exploitability grade to which the security vulnerability belongs can be determined from the above-mentioned multiple exploitability grades.
[0078] In the embodiment of the present application, as an optional embodiment, the target exploitability level to which the security vulnerability belongs can be determined according to the method described in the following steps b1-b2, specifically:
[0079] Step b1: Determine the index values of multiple exploitability indicators to which the security vulnerability belongs according to the vulnerability description information of the security vulnerability.
[0080] Here, the above-mentioned multiple exploitability indicators include but are not limited to: the access path of the security vulnerability, trigger conditions (which are also equivalent to the trigger requirements that need to be met to trigger the security vulnerability), trigger permissions (equivalent to the user permissions required to trigger the security vulnerability), and interaction conditions (equivalent to whether triggering the security vulnerability requires the participation / cooperation of the user or the target business system).
[0081] Specifically, taking the target business system as a credit reporting system as an example, the specific indicator definitions and indicator values of the above-mentioned multiple exploitability indicators can be referred to as shown in the following Table 2:
[0082]
[0083]
[0084] Table 2
[0085] Step b2: From the multiple exploitability classifications under the technical evaluation dimension, determine the exploitability classification whose classification description information matches the indicator values of the multiple exploitability indicators to which the security vulnerability belongs as the target exploitability classification.
[0086] Here, the classification description information of each of the utilization classifications is determined according to a combination of different indicator values of the above-mentioned multiple utilization indicators.
[0087] Specifically, taking the multiple exploitability indicators shown in Table 2 as an example, under the technical evaluation dimension, the exploitability level can be divided into 1-9 levels (equivalent to 9 exploitability levels, represented by numbers 1-9 respectively). The larger the level of the exploitability level, the higher the possibility of the security vulnerability being exploited (that is, the lower the technical difficulty of triggering the security vulnerability, the easier it is to be triggered). At this time, the hierarchical description information of the above 9 exploitability levels (equivalent to the indicator value combination of multiple exploitability indicators corresponding to each exploitability level) can be shown in Table 3 below:
[0088]
[0089]
[0090]
[0091] Table 3
[0092] For example, as shown in Table 3 above, if the indicator values of multiple exploitability indicators belonging to a security vulnerability are "access path: local, trigger condition: low, trigger permission: none, interaction condition: not required" (for the row represented by sequence number 5 in Table 3 above), then according to Table 3 above, it can be determined that the target exploitability level corresponding to the security vulnerability is level 8.
[0093] S202, according to the vulnerability description information of the security vulnerability, determine, from the multiple vulnerability impact classifications under the technical assessment dimension, a vulnerability impact classification whose classification description information matches the vulnerability description information as a target vulnerability impact classification corresponding to the security vulnerability.
[0094] Here, the target vulnerability impact rating is used to characterize the degree of impact of the security vulnerability on the target business system after it is triggered. Among them, under the technical assessment dimension, the vulnerability impact rating reflects the degree of impact on the target business system after the security vulnerability is successfully exploited (that is, successfully triggered) (equivalent to the technical difficulty of triggering a security vulnerability).
[0095] In the embodiment of the present application, as an optional embodiment, the target vulnerability impact classification to which the security vulnerability belongs can be determined according to the method described in the following steps c1-c2, specifically:
[0096] Step c1: extracting vulnerability impact description information related to the impact of the security vulnerability on the target business system after being triggered from the vulnerability description information of the security vulnerability.
[0097] Specifically, the above-mentioned vulnerability impact description information includes but is not limited to: first description information used to determine whether a security vulnerability will cause business interruption in the target business system after being triggered, second description information used to determine whether a security vulnerability will cause core information leakage in the target business system after being triggered, third description information used to determine whether general permissions (such as ordinary user permissions) in the target business system can be obtained after the security vulnerability is triggered, and fourth description information used to determine whether a security vulnerability will cause non-core information leakage in the target business system after being triggered, etc. The specific information content of the above-mentioned vulnerability impact description information is not mandatory in the embodiments of the present application.
[0098] Step c2: According to the vulnerability impact description information, determine, from the multiple vulnerability impact classifications under the technical assessment dimension, a vulnerability impact classification whose classification description information matches the vulnerability impact description information as the target vulnerability impact classification.
[0099] Specifically, taking the target business coefficient belonging to the credit reporting system as an example, under the technical assessment dimension, the vulnerability impact classification can be divided into 1-3 levels (equivalent to 3 vulnerability impact classifications, represented by numbers 1-3 respectively). The larger the level of the vulnerability impact classification, the greater the impact of the security vulnerability on the target business system after it is triggered (that is, the greater the harm to the target business system after the security vulnerability is triggered). At this time, the classification description information of the above 3 vulnerability impact classifications can be as follows
[0100] As shown in Table 4:
[0101]
[0102]
[0103] Table 4
[0104] S203, using the target exploitability classification and the target vulnerability impact classification corresponding to the security vulnerability as index information, retrieve the vulnerability classification whose location information matches the index information from a pre-stored vulnerability technical classification list as the vulnerability technical classification corresponding to the security vulnerability under the technical assessment dimension.
[0105] Here, the vulnerability technical classification list includes multiple vulnerability classifications under the technical assessment dimension; wherein, the tabulation method of the vulnerability technical classification list is similar to the tabulation method of the security vulnerability rating list in the above steps.
[0106] Specifically, before executing the above steps S201-S203, a vulnerability technical grading list for determining the vulnerability technical grading corresponding to the security vulnerability under the technical assessment dimension can be pre-created and stored in such a manner that each exploitability grading under the above technical assessment dimension corresponds to a column (or a row) in the vulnerability technical grading list, and each vulnerability impact grading corresponds to a row (or a column) in the vulnerability technical grading list; wherein, in the created vulnerability technical grading list, the vulnerability grading corresponding to each cross-item (i.e., the cross-item of the above exploitability grading and the above vulnerability impact grading in the vulnerability technical grading list) can be sequentially set in the direction of the diagonal (equivalent to the above exploitability grading and the above vulnerability impact grading in the vulnerability technical grading list being comprehensively sorted from high to low), so that, after determining the above target exploitability grading and the above target vulnerability impact grading of a security vulnerability, the vulnerability technical grading corresponding to the security vulnerability can be determined directly from the above vulnerability technical grading list by looking up a table.
[0107] For example, the multiple exploitability levels under the above technical evaluation dimension are: 1-9 (the higher the level, the higher the possibility of the security vulnerability being exploited, and the lower the technical difficulty of triggering the security vulnerability), and the multiple vulnerability impact levels are: 1-3 (the higher the level, the greater the impact on the target business system after the security vulnerability is triggered). The vulnerability technical classification list can be shown in Table 5 below:
[0108]
[0109] Table 5
[0110] Regarding the specific implementation process of the above-mentioned step S102, in an optional implementation manner, under the asset valuation dimension, multiple asset importance indicators that can measure the importance of assets in the target business system can be extracted from the hierarchical description information of the asset classification, and based on the asset description information of the target assets affected by the security vulnerability, the specific indicator value of each asset importance indicator corresponding to the target asset is determined, so as to quantify the degree of match between the asset description information of the target asset and the hierarchical description information of each of the above-mentioned asset classifications through these indicator values, which is conducive to improving the accuracy of the classification assessment of security vulnerabilities under the asset valuation dimension.
[0111] Here, in the above optional implementation, Figure 3 A flow chart of a method for determining the asset importance classification corresponding to a security vulnerability in the asset assessment dimension provided by an embodiment of the present application is shown, such as Figure 3 As shown, during the execution of the above step S102, the method includes steps S301-S302, specifically:
[0112] S301, determining the index values of multiple asset importance indexes to which the target asset belongs according to the target asset associated with the security vulnerability.
[0113] Here, when the target business system belongs to a credit reporting system, the above-mentioned multiple asset importance indicators include but are not limited to: the location of the target asset in the target business system (for example, whether the location of the target asset in the target business system belongs to the main business system or the non-main business system), the exposure surface of the target asset (which can be determined based on the part of the target asset that is visible to the outside), and the access type (which can be determined based on the user permissions allowed to access the target asset).
[0114] S302: Determine, from among the multiple asset classifications under the asset evaluation dimension, an asset classification whose classification description information matches the index values of the multiple asset importance indexes to which the target asset belongs as the asset importance classification.
[0115] Here, the classification description information of each asset classification is determined according to a combination of different indicator values of the above-mentioned multiple asset importance indicators.
[0116] Specifically, taking the above-mentioned multiple asset importance indicators as an example, under the asset evaluation dimension, the asset importance can be divided into 1-5 levels (equivalent to including 5 asset classifications, represented by numbers 1-5 respectively). The larger the level of the asset classification, the higher the importance of the target asset affected by the security vulnerability in the target business system. At this time, the classification description information of the above-mentioned 5 asset classifications (which is also equivalent to the indicator value combination of the above-mentioned multiple asset importance indicators corresponding to each asset classification) can be shown in the following Table 6:
[0117]
[0118]
[0119] Table 6
[0120] For example, as shown in Table 6 above, if the indicator values of the above multiple asset importance indicators to which a security vulnerability belongs are "location of target asset in target business system: main business system, exposure of target asset: Internet, access type: whitelist" (for a row represented by sequence number 2 in Table 6 above), then according to Table 6 above, it can be determined that the asset importance level corresponding to the security vulnerability is level 4.
[0121] Based on the above-mentioned classification and assessment method provided in the embodiment of the present application, for the security vulnerabilities scanned in the target business system, according to the vulnerability description information of the security vulnerability, from multiple vulnerability classifications under the technical assessment dimension, the vulnerability classification whose classification description information matches the vulnerability description information is determined as the vulnerability technical classification of the security vulnerability; according to the target assets associated with the security vulnerability, from multiple asset classifications under the asset assessment dimension, the asset classification whose classification description information matches the asset description information of the target assets is determined as the asset importance classification of the security vulnerability; according to the vulnerability technical classification and the asset importance classification, the security vulnerability level to which the security vulnerability belongs is determined.
[0122] In this way, the present application classifies and evaluates the security vulnerabilities scanned in the target business system from two main evaluation dimensions: the technical difficulty of triggering the security vulnerability and the importance of the assets affected by the security vulnerability in the target business system. The final classification and evaluation results can not only reflect the security risks of the security vulnerabilities in the general technical dimension, but also reflect the security risks of the security vulnerabilities in the proprietary business dimension corresponding to the target business system. In this way, the classification and evaluation results of the security vulnerabilities can match the specific risk assessment requirements of the target business system, which is conducive to improving the accuracy of the security vulnerability classification and evaluation.
[0123] Based on the same inventive concept, the present application also provides a rating and assessment device corresponding to the above-mentioned security vulnerability rating and assessment method. Since the principle of solving the problem by the rating and assessment device in the embodiment of the present application is similar to the above-mentioned security vulnerability rating and assessment method in the embodiment of the present application, the implementation of the rating and assessment device can refer to the implementation of the above-mentioned rating and assessment method, and the repeated parts will not be repeated.
[0124] Reference Figure 4 As shown, Figure 4 A schematic diagram of the structure of a security vulnerability rating and evaluation device provided in an embodiment of the present application is shown, wherein the rating and evaluation device comprises:
[0125] The first classification module 401 is used to determine, for the security vulnerability scanned in the target business system, according to the vulnerability description information of the security vulnerability, from multiple vulnerability classifications under the technical evaluation dimension, the vulnerability classification whose classification description information matches the vulnerability description information as the vulnerability technical classification corresponding to the security vulnerability under the technical evaluation dimension;
[0126] The second classification module 402 is used to determine, according to the target asset associated with the security vulnerability, from multiple asset classifications under the asset evaluation dimension, an asset classification whose classification description information matches the asset description information of the target asset as the asset importance classification corresponding to the security vulnerability under the asset evaluation dimension; wherein the target asset represents an asset in the target business system that is affected by the security vulnerability;
[0127] The grading and evaluation module 403 is used to determine the security vulnerability level to which the security vulnerability belongs according to the vulnerability technology grading and the asset importance grading.
[0128] In an optional implementation, when determining, from among multiple vulnerability classifications under the technical evaluation dimension, based on the vulnerability description information of the security vulnerability, a vulnerability classification whose classification description information matches the vulnerability description information as the vulnerability technical classification corresponding to the security vulnerability under the technical evaluation dimension, the first classification module 401 is configured to:
[0129] According to the vulnerability description information of the security vulnerability, from the multiple exploitability levels under the technical assessment dimension, determine the exploitability level whose level description information matches the vulnerability description information as the target exploitability level corresponding to the security vulnerability; wherein the target exploitability level is used to characterize the technical difficulty of triggering the security vulnerability;
[0130] According to the vulnerability description information of the security vulnerability, from the multiple vulnerability impact classifications under the technical assessment dimension, determine the vulnerability impact classification whose classification description information matches the vulnerability description information as the target vulnerability impact classification corresponding to the security vulnerability; wherein the target vulnerability impact classification is used to characterize the degree of impact of the security vulnerability on the target business system after being triggered;
[0131] Using the target exploitability classification and the target vulnerability impact classification corresponding to the security vulnerability as index information, retrieve the vulnerability classification whose location information matches the index information from a pre-stored vulnerability technical classification list as the vulnerability technical classification corresponding to the security vulnerability under the technical assessment dimension; wherein the vulnerability technical classification list includes multiple vulnerability classifications under the technical assessment dimension.
[0132] In an optional implementation, when determining, based on the vulnerability description information of the security vulnerability, from a plurality of exploitability levels under the technical assessment dimension, an exploitability level whose level description information matches the vulnerability description information as a target exploitability level corresponding to the security vulnerability, the first leveling module 401 is configured to:
[0133] Determine the index values of multiple exploitability indicators to which the security vulnerability belongs according to the vulnerability description information of the security vulnerability; wherein the multiple exploitability indicators include: the access path, trigger condition, trigger permission, and interaction condition of the security vulnerability;
[0134] From the multiple exploitability classifications under the technical evaluation dimension, determine the exploitability classification whose classification description information matches the indicator values of the multiple exploitability indicators to which the security vulnerability belongs as the target exploitability classification; wherein the classification description information of each of the exploitability classifications is determined based on a combination of different indicator values of the multiple exploitability indicators.
[0135] In an optional implementation, when determining, according to the vulnerability description information of the security vulnerability, from the multiple vulnerability impact classifications under the technical assessment dimension, a vulnerability impact classification whose classification description information matches the vulnerability description information as a target vulnerability impact classification corresponding to the security vulnerability, the first classification module 401 is used to:
[0136] Extracting vulnerability impact description information related to the impact of the security vulnerability on the target business system after the security vulnerability is triggered from the vulnerability description information of the security vulnerability;
[0137] According to the vulnerability impact description information, from a plurality of vulnerability impact classifications under the technical assessment dimension, a vulnerability impact classification whose classification description information matches the vulnerability impact description information is determined as the target vulnerability impact classification.
[0138] In an optional implementation, when determining, from among the multiple asset classifications under the asset evaluation dimension, the target asset associated with the security vulnerability, an asset classification whose classification description information matches the asset description information of the target asset as the asset importance classification corresponding to the security vulnerability under the asset evaluation dimension, the second classification module 402 is configured to:
[0139] According to the target asset associated with the security vulnerability, determine the index values of multiple asset importance indexes to which the target asset belongs; wherein the multiple asset importance indexes include: the location of the target asset in the target business system, the exposure surface of the target asset, and the access type;
[0140] From the multiple asset classifications under the asset evaluation dimension, determine the asset classification whose classification description information matches the indicator values of the multiple asset importance indicators to which the target asset belongs as the asset importance classification; wherein the classification description information of each asset classification is determined based on a combination of different indicator values of the multiple asset importance indicators.
[0141] In an optional implementation, when determining the security vulnerability level to which the security vulnerability belongs according to the vulnerability technology classification and the asset importance classification, the classification and evaluation module 403 is used to:
[0142] Using the vulnerability technology classification and the asset importance classification corresponding to the security vulnerability as target index information, retrieve the security vulnerability rating whose location information matches the target index information from a pre-stored security vulnerability rating list as the security vulnerability level to which the security vulnerability belongs; wherein the security vulnerability rating list contains multiple security vulnerability ratings.
[0143] In an optional implementation, the target business system includes: a credit reporting system.
[0144] Based on the same inventive concept, the present application also provides an electronic device corresponding to the above-mentioned security vulnerability rating and assessment method. Since the principle of solving the problem by the electronic device in the embodiment of the present application is similar to the above-mentioned security vulnerability rating and assessment method in the embodiment of the present application, the implementation of the electronic device can refer to the implementation of the above-mentioned security vulnerability rating and assessment method, and the repeated parts will not be repeated.
[0145] Figure 5A structural diagram of an electronic device 500 provided in an embodiment of the present application includes: a processor 501, a memory 502 and a bus 503, the memory 502 stores machine-readable instructions executable by the processor 501, and when the electronic device runs a security vulnerability rating assessment method such as in the embodiment, the processor 501 communicates with the memory 502 through the bus 503, and the processor 501 executes the machine-readable instructions, wherein the processor 501 implements the above-mentioned security vulnerability rating assessment method when executing the machine-readable instructions.
[0146] Specifically, the above-mentioned memory 502 and processor 501 can be general-purpose memory and processor, which are not specifically limited here. When the processor 501 runs the computer program stored in the memory 502, it can execute the above-mentioned security vulnerability rating assessment method.
[0147] Corresponding to the security vulnerability rating and assessment method in the present application, an embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned security vulnerability rating and assessment method are executed.
[0148] Specifically, the storage medium can be a general storage medium, such as a mobile disk, a hard disk, etc. When the computer program on the storage medium is run, the above-mentioned security vulnerability grading and assessment method can be executed.
[0149] In the embodiments provided in the present application, it should be understood that the disclosed systems and methods can be implemented in other ways. The system embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of systems or units, which can be electrical, mechanical or other forms.
[0150] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0151] In addition, each functional unit in the embodiments provided in the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0152] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0153] It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are only used to distinguish the description and are not to be understood as indicating or implying relative importance.
[0154] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application. They should all be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.
Claims
1. A security vulnerability rating and assessment method, characterized in that: The grading assessment method includes: For the security vulnerabilities scanned in the target business system, according to the vulnerability description information of the security vulnerability, from multiple vulnerability classifications under the technical assessment dimension, determine the vulnerability classification whose classification description information matches the vulnerability description information as the vulnerability technical classification corresponding to the security vulnerability under the technical assessment dimension; According to the target asset associated with the security vulnerability, determine, from multiple asset classifications under the asset evaluation dimension, an asset classification whose classification description information matches the asset description information of the target asset as the asset importance classification corresponding to the security vulnerability under the asset evaluation dimension; wherein the target asset represents an asset in the target business system that is affected by the security vulnerability; The security vulnerability level to which the security vulnerability belongs is determined based on the vulnerability technology classification and the asset importance classification.
2. The grading and evaluation method according to claim 1, characterized in that: The step of determining, according to the vulnerability description information of the security vulnerability, from multiple vulnerability classifications under the technical evaluation dimension, a vulnerability classification whose classification description information matches the vulnerability description information as the vulnerability technical classification corresponding to the security vulnerability under the technical evaluation dimension, includes: According to the vulnerability description information of the security vulnerability, from the multiple exploitability levels under the technical assessment dimension, determine the exploitability level whose level description information matches the vulnerability description information as the target exploitability level corresponding to the security vulnerability; wherein the target exploitability level is used to characterize the technical difficulty of triggering the security vulnerability; According to the vulnerability description information of the security vulnerability, from the multiple vulnerability impact classifications under the technical assessment dimension, determine the vulnerability impact classification whose classification description information matches the vulnerability description information as the target vulnerability impact classification corresponding to the security vulnerability; wherein the target vulnerability impact classification is used to characterize the degree of impact of the security vulnerability on the target business system after being triggered; Using the target exploitability classification and the target vulnerability impact classification corresponding to the security vulnerability as index information, retrieve the vulnerability classification whose location information matches the index information from a pre-stored vulnerability technical classification list as the vulnerability technical classification corresponding to the security vulnerability under the technical assessment dimension; wherein the vulnerability technical classification list includes multiple vulnerability classifications under the technical assessment dimension.
3. The grading and evaluation method according to claim 2, characterized in that: The determining, according to the vulnerability description information of the security vulnerability, from a plurality of exploitability levels under the technical assessment dimension, an exploitability level whose level description information matches the vulnerability description information as a target exploitability level corresponding to the security vulnerability, includes: Determine the index values of multiple exploitability indicators to which the security vulnerability belongs according to the vulnerability description information of the security vulnerability; wherein the multiple exploitability indicators include: the access path, trigger condition, trigger permission, and interaction condition of the security vulnerability; From the multiple exploitability classifications under the technical evaluation dimension, determine the exploitability classification whose classification description information matches the indicator values of the multiple exploitability indicators to which the security vulnerability belongs as the target exploitability classification; wherein the classification description information of each of the exploitability classifications is determined based on a combination of different indicator values of the multiple exploitability indicators.
4. The grading and evaluation method according to claim 2, characterized in that: The step of determining, according to the vulnerability description information of the security vulnerability, from a plurality of vulnerability impact classifications under the technical assessment dimension, a vulnerability impact classification whose classification description information matches the vulnerability description information as a target vulnerability impact classification corresponding to the security vulnerability, includes: Extracting vulnerability impact description information related to the impact of the security vulnerability on the target business system after the security vulnerability is triggered from the vulnerability description information of the security vulnerability; According to the vulnerability impact description information, from a plurality of vulnerability impact classifications under the technical assessment dimension, a vulnerability impact classification whose classification description information matches the vulnerability impact description information is determined as the target vulnerability impact classification.
5. The grading and evaluation method according to claim 1, characterized in that: The step of determining, according to the target asset associated with the security vulnerability, from a plurality of asset classifications under the asset evaluation dimension, an asset classification whose classification description information matches the asset description information of the target asset as the asset importance classification corresponding to the security vulnerability under the asset evaluation dimension, includes: According to the target asset associated with the security vulnerability, determine the index values of multiple asset importance indexes to which the target asset belongs; wherein the multiple asset importance indexes include: the location of the target asset in the target business system, the exposure surface of the target asset, and the access type; From the multiple asset classifications under the asset evaluation dimension, determine the asset classification whose classification description information matches the indicator values of the multiple asset importance indicators to which the target asset belongs as the asset importance classification; wherein the classification description information of each asset classification is determined based on a combination of different indicator values of the multiple asset importance indicators.
6. The grading and evaluation method according to claim 1, characterized in that: Determining the security vulnerability level to which the security vulnerability belongs according to the vulnerability technology classification and the asset importance classification includes: Using the vulnerability technology classification and the asset importance classification corresponding to the security vulnerability as target index information, retrieve the security vulnerability rating whose location information matches the target index information from a pre-stored security vulnerability rating list as the security vulnerability level to which the security vulnerability belongs; wherein the security vulnerability rating list contains multiple security vulnerability ratings.
7. The grading and evaluation method according to claim 1, characterized in that: The target business system includes: a credit reporting system.
8. A security vulnerability grading and assessment device, characterized in that: The grading and evaluation device comprises: A first grading module is used to determine, for a security vulnerability scanned in a target business system, based on vulnerability description information of the security vulnerability, from multiple vulnerability grades under a technical assessment dimension, a vulnerability grade whose grade description information matches the vulnerability description information as the vulnerability technical grade corresponding to the security vulnerability under the technical assessment dimension; A second classification module is used to determine, according to the target asset associated with the security vulnerability, from multiple asset classifications under the asset evaluation dimension, an asset classification whose classification description information matches the asset description information of the target asset as the asset importance classification corresponding to the security vulnerability under the asset evaluation dimension; wherein the target asset represents an asset in the target business system that is affected by the security vulnerability; The grading assessment module is used to determine the security vulnerability level to which the security vulnerability belongs based on the vulnerability technology grading and the asset importance grading.
9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and when the machine-readable instructions are executed by the processor, the steps of the grading and evaluation method as described in any one of claims 1 to 7 are performed.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the grading and evaluation method according to any one of claims 1 to 7 are executed.
Citation Information
Patent Citations
Vulnerability processing method and device, storage medium and electronic equipment
CN116542520A
Vulnerability assessment method, electronic equipment and storage medium
CN116881931A
Cited By
Vulnerability management method and device, electronic equipment and medium
CN119696829A
Multi-dimensional quantitative evaluation method for network security vulnerabilities
CN119814462A
