Security requirements analysis method, device, computer equipment and storage medium

Abstract

The present application relates to a security requirements analysis method, apparatus, computer equipment, storage medium and computer program product. The method comprises: obtaining functional attributes of a target software system corresponding to at least two functional dimensions, determining a first security requirements set of the target software system according to the functional attributes, and obtaining a business scenario of the target software system, determining a second security requirements set of the target software system according to the business scenario, and then determining the security requirements of the target software system according to the first security requirements set and the second security requirements set. The security requirements determined by the above method are not only strongly related to the business scenario, but also strongly related to the properties of the target software system itself, which improves the adaptability of the determined security requirements to the target software system itself, and correspondingly improves the security performance of the designed target software system.

Description

Technical Field

[0001] The present application relates to the field of information security technology, and in particular to a security requirements analysis method, apparatus, computer equipment, storage medium and computer program product. Background Art

[0002] Security requirements analysis is the process of obtaining the security requirements corresponding to the actual business functions of the system. The purpose of security requirements analysis is to clarify the security requirements and goals of the system to guide the design and development of the system.

[0003] The traditional security requirements analysis method is to obtain the security requirements corresponding to each business scenario from the security requirements library based on the business scenarios of the software system to determine the security requirements that meet each business scenario of the software system.

[0004] However, the security requirements determined by the above security requirements analysis method are strongly related to the business scenarios of the software system, and have poor adaptability to the software system itself, which in turn makes the security performance of the software system poor. Summary of the invention

[0005] Based on this, it is necessary to provide a security requirements analysis method, apparatus, computer equipment, computer-readable storage medium and computer program product to address the above technical issues.

[0006] In a first aspect, the present application provides a security requirements analysis method. The method comprises:

[0007] Acquire functional attributes of the target software system, and determine a first set of security requirements of the target software system according to the functional attributes; wherein the first set of security requirements includes a plurality of security requirements matching the functional attributes, and the functional attributes include attributes of the target software corresponding to at least two functional dimensions;

[0008] Acquire a business scenario of the target software system, and determine a second security requirement set of the target software system according to the business scenario; wherein the second security requirement set includes multiple security requirements matching the business scenario;

[0009] The security requirements of the target software system are determined according to the first security requirement set and the second security requirement set.

[0010] In one embodiment, determining a first set of security requirements of a target software system according to functional attributes includes:

[0011] Determine the functional safety requirement corresponding to each functional attribute according to the first corresponding relationship; wherein the first corresponding relationship includes the corresponding relationship between the functional attribute and the functional safety requirement;

[0012] Obtain the union of functional safety requirements corresponding to the same functional dimension to obtain a set of requirements in the same dimension;

[0013] The intersection of the same-dimensional requirement sets corresponding to different functional dimensions is obtained to obtain a first security requirement set.

[0014] In one embodiment, determining a second security requirement set of a target software system according to a business scenario includes:

[0015] Determining the business security requirements corresponding to each business scenario according to the second corresponding relationship; wherein the second corresponding relationship includes a corresponding relationship between the business scenario and the business security requirements;

[0016] The union of the business security requirements is obtained to obtain a second security requirement set.

[0017] In one embodiment, determining the security requirements of the target software system according to the first security requirement set and the second security requirement set includes:

[0018] The intersection of the first security requirement set and the second security requirement set is obtained to obtain the security requirements of the target software system.

[0019] In one embodiment, the method further comprises:

[0020] Determine the design plan of the target software system based on the security requirements of the target software system and the modification risk level of the target software system.

[0021] In one embodiment, determining the transformation risk level of the target software system includes:

[0022] Determine the system risk level of the target software system based on functional attributes;

[0023] Obtain the system transformation content of the target software system, and determine the system transformation type according to the system transformation content;

[0024] Determine the transformation risk level of the target software system based on the system risk level and system transformation type.

[0025] In one embodiment, determining the system risk level of the target software system according to the functional attributes includes:

[0026] Determine the security risk value of the target software system based on functional attributes;

[0027] The system risk level of the target software system is determined by the risk safety value.

[0028] In one embodiment, determining the security risk value of the target software system according to the functional attribute includes:

[0029] Determine the maximum safety risk value of the functional attribute corresponding to each functional dimension according to the risk correspondence relationship; wherein the risk correspondence relationship includes the correspondence between the functional attribute and the safety risk value;

[0030] Calculate the product of the maximum security risk value and the weight of the corresponding functional dimension, and calculate the sum of the products to obtain the security risk value of the target software system.

[0031] In one embodiment, determining the system transformation type according to the system transformation content includes:

[0032] The system transformation type corresponding to the system transformation content is determined according to the transformation correspondence relationship; wherein the transformation correspondence relationship includes the correspondence relationship between the system transformation content and the system transformation type.

[0033] In one embodiment, determining the transformation risk level of the target software system according to the system risk level and the system transformation type includes:

[0034] If the system transformation type is a new system, when the system risk level is low risk, the transformation risk level of the target software system is level 2; when the system risk level is not low risk, the transformation risk level of the target software system is level 3;

[0035] If the system transformation type is a high-risk transformation system, when the system risk level is high risk, the transformation risk level of the target software system is level three; when the system risk level is not high risk, the transformation risk level of the target software system is level two;

[0036] If the system transformation type is a medium-risk transformation system, when the system risk level is low risk, the transformation risk level of the target software system is level one; when the system risk level is not low risk, the transformation risk level of the target software system is level two;

[0037] If the system transformation type is a low-risk transformation system, the transformation risk level of the target software system is level one; among them, the higher the transformation risk level, the greater the system transformation risk.

[0038] In a second aspect, the present application also provides a security requirements analysis device. The device comprises:

[0039] A first requirement determination module is used to obtain functional attributes of the target software system and determine a first security requirement set of the target software system according to the functional attributes; wherein the first security requirement set includes a plurality of security requirements matching the functional attributes, and the functional attributes include attributes of the target software corresponding to at least two functional dimensions;

[0040] A second requirement determination module, used to obtain a business scenario of the target software system, and determine a second security requirement set of the target software system according to the business scenario; wherein the second security requirement set includes multiple security requirements matching the business scenario;

[0041] The system requirement determination module is used to determine the security requirements of the target software system according to the first security requirement set and the second security requirement set.

[0042] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0043] Acquire functional attributes of the target software system, and determine a first set of security requirements of the target software system according to the functional attributes; wherein the first set of security requirements includes a plurality of security requirements matching the functional attributes, and the functional attributes include attributes of the target software corresponding to at least two functional dimensions;

[0044] Acquire a business scenario of the target software system, and determine a second security requirement set of the target software system according to the business scenario; wherein the second security requirement set includes multiple security requirements matching the business scenario;

[0045] The security requirements of the target software system are determined according to the first security requirement set and the second security requirement set.

[0046] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0047] Acquire functional attributes of the target software system, and determine a first set of security requirements of the target software system according to the functional attributes; wherein the first set of security requirements includes a plurality of security requirements matching the functional attributes, and the functional attributes include attributes of the target software corresponding to at least two functional dimensions;

[0048] Acquire a business scenario of the target software system, and determine a second security requirement set of the target software system according to the business scenario; wherein the second security requirement set includes multiple security requirements matching the business scenario;

[0049] The security requirements of the target software system are determined according to the first security requirement set and the second security requirement set.

[0050] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0051] Acquire functional attributes of the target software system, and determine a first set of security requirements of the target software system according to the functional attributes; wherein the first set of security requirements includes a plurality of security requirements matching the functional attributes, and the functional attributes include attributes of the target software corresponding to at least two functional dimensions;

[0052] Acquire a business scenario of the target software system, and determine a second security requirement set of the target software system according to the business scenario; wherein the second security requirement set includes multiple security requirements matching the business scenario;

[0053] The security requirements of the target software system are determined according to the first security requirement set and the second security requirement set.

[0054] The above-mentioned security requirements analysis method, apparatus, computer equipment, storage medium and computer program product obtain the functional attributes of the target software system corresponding to at least two functional dimensions, determine the first security requirements set of the target software system according to the functional attributes, and obtain the business scenario of the target software system, determine the second security requirements set of the target software system according to the business scenario, and then determine the security requirements of the target software system according to the first security requirements set and the second security requirements set. The security requirements jointly determined based on the functional attributes of the target software system and the business scenario are not only strongly related to the business scenario, but also strongly related to the attributes of the target software system itself, thereby improving the adaptability of the determined security requirements to the target software system itself, and correspondingly improving the security performance of the designed target software system. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 A schematic diagram of a process of a security requirement analysis method in one embodiment;

[0056] Figure 2 A schematic diagram of a process for determining a first security requirement set in an embodiment;

[0057] Figure 3 A schematic diagram of a process for determining a second set of security requirements in one embodiment;

[0058] Figure 4 A schematic diagram of a process for determining a transformation risk level in one embodiment;

[0059] Figure 5 A schematic diagram of a process for determining a security risk value of a target software system in one embodiment;

[0060] Figure 6 is a structural block diagram of a security requirement analysis device in one embodiment;

[0061] Figure 7 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0062] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0063] In one embodiment, Figure 1 As shown, a security requirements analysis method is provided. This embodiment uses the method applied to a terminal as an example. It can be understood that the method can also be applied to a server, and can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server. Among them, the terminal can be but is not limited to various personal computers, laptops, smart phones, tablets, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The server can be implemented as an independent server or a server cluster composed of multiple servers. The above-mentioned security requirements analysis method includes the following steps:

[0064] S110. Acquire functional attributes of the target software system, and determine a first security requirement set of the target software system according to the functional attributes.

[0065] Among them, the first security requirement set includes multiple security requirements that match the functional attributes, and the functional attributes include the attributes of the target software corresponding to at least two functional dimensions. The target software system is the software system to be designed by the software developer. For example, it can be a software system for implementing business management, a software system for implementing personnel management, or a software system for implementing operation assistance. Functional attributes are the attribute information of the software system itself in different functional dimensions. For example, the functional dimensions include system categories, user types, or client architectures. Accordingly, the attribute information in the functional dimension of system categories may include business management systems, personnel management systems, performance management systems, etc.; the attribute information in the functional dimension of user types may include internal employees of the enterprise or all users, etc.; the attribute information in the functional dimension of client architecture may include Web application systems, mobile application systems, WeChat applets, dedicated self-service terminals, etc.

[0066] Optionally, the computer device may obtain the functional attributes input by the user as the functional attributes of the target software system. Optionally, the computer device may display an attribute input area on the display interface in response to the user's security requirements analysis request, and obtain the functional attributes input by the user in the attribute input area as the functional attributes of the target software system. Candidate functional attributes may also be displayed in the attribute input area, and the candidate functional attributes selected by the user may be obtained as the functional attributes of the target software system.

[0067] Optionally, the computer device can also obtain the functional attributes of the target software system based on the functional keywords input by the user. Among them, the functional keywords can be used to characterize the functional characteristics of the software system. Optionally, the computer device can recommend candidate functional attributes to the user based on the correspondence between the functional keywords and the functional attributes, and determine the functional attributes of the target software system based on the user's selection of the candidate functional attributes. For example, the user enters the functional keywords "attendance" and "personnel" in the attribute input area. According to the correspondence between the relational words and the functional attributes, the candidate functional attributes that the computer device can recommend to the user include: personnel management system, performance management system, and internal employees of the enterprise. If the user selects the personnel management system and internal employees of the enterprise, the computer device can determine that the functional attributes of the target software system include the personnel management system and internal employees of the enterprise.

[0068] Optionally, after determining the functional attributes of the target software system, the computer device further determines the security requirements corresponding to the functional attributes, and then obtains the first security requirements set of the target software system. Optionally, a security requirements library including multiple security requirements is preset in the computer device, and each security requirement corresponds to a functional attribute that needs to meet the security requirement. The computer device obtains security requirements corresponding to the functional attributes including the functional attributes of the above-mentioned target software system from the security requirements library to form the first security requirements set of the target software system. For example, in the case where the functional attributes of the target software system include a personnel management system and internal employees of an enterprise, the computer device can obtain security requirements corresponding to the functional attributes including the above-mentioned personnel management system and internal employees of the enterprise from the security requirements library as the first security requirements set of the target software system.

[0069] S120: Obtain a business scenario of the target software system, and determine a second security requirement set of the target software system according to the business scenario.

[0070] The second security requirement set includes multiple security requirements that match business scenarios. Business scenarios are specific businesses that can be performed by the software system, such as user registration, user login, password reset, personal information maintenance, order payment, transfer, SMS notification, face recognition, etc.

[0071] Optionally, the computer device may obtain a business scenario input by the user as the business scenario of the target software system. Optionally, in response to the user's security requirements analysis request, the computer device displays a display attribute input area and a scenario input area on the display interface, thereby obtaining the business scenario input by the user in the scenario input area as the business scenario of the target software system. Candidate business scenarios may also be displayed in the scenario input area, and the candidate business scenario selected by the user may be obtained as the business scenario of the target software system.

[0072] Optionally, the computer device can also obtain the business scenario of the target software system based on the business keywords input by the user. Among them, the business keywords can be used to characterize the business characteristics of the software system. Optionally, the computer device can recommend candidate business scenarios including business keywords to the user based on the name of the business scenario, and determine the business scenario of the target software system based on the user's selection of the candidate business scenario. For example, the user enters the business keyword "user" in the business input area, and the candidate business scenarios that the computer device can recommend to the user include: user login and user registration. If the user selects user login and user registration at the same time, the computer device can determine that the business scenarios of the target software system include user login and user registration.

[0073] Optionally, after determining the business scenario of the target software system, the computer device further determines the security requirements corresponding to the business scenario, and then obtains a second set of security requirements for the target software system. Optionally, each security requirement in the above security requirements library also corresponds to a business scenario that needs to meet the security requirement, and the computer device obtains the security requirements corresponding to the business scenario including the business scenario of the above target software system from the security requirements library to form the second set of security requirements for the target software system. For example, when the business scenario of the target software system includes user registration and user login, the computer device can obtain the security requirements corresponding to the business scenario including the above user registration and user login from the security requirements library as the second set of security requirements for the target software system.

[0074] S130 . Determine security requirements of the target software system according to the first security requirement set and the second security requirement set.

[0075] Optionally, the computer device may determine the security requirements of the target software system according to the requirements range covered by the first security requirements set and the requirements range covered by the second security requirements set. The security requirements set with the largest requirements range covered in the first security requirements set and the second security requirements set is determined as the security requirements of the target software system. The requirements range may be determined according to the number of security requirements. The larger the number of security requirements, the larger the requirements range.

[0076] Optionally, in order to more comprehensively determine the security requirements of the target software system, the computer device may also directly obtain the union of the first security requirement set and the second security requirement as the security requirements of the target software system.

[0077] In this embodiment, the computer device obtains functional attributes of the target software system corresponding to at least two functional dimensions, determines a first security requirement set based on the functional attributes, and obtains a business scenario of the target software system, determines a second security requirement set based on the business scenario, and then determines the security requirements of the target software system based on the first security requirement set and the second security requirement set. The security requirements determined based on the functional attributes of the target software system and the business scenario are not only strongly related to the business scenario, but also to the attributes of the target software system itself, thereby improving the adaptability of the determined security requirements to the target software system itself and correspondingly improving the security performance of the designed target software system.

[0078] In one embodiment, there may be multiple functional attributes corresponding to the same functional dimension, such as Figure 2 As shown, the above S110 includes:

[0079] S210. Determine the functional safety requirement corresponding to each functional attribute according to the first corresponding relationship.

[0080] The first corresponding relationship includes the corresponding relationship between the functional attributes and the functional safety requirements. Optionally, the first corresponding relationship includes the corresponding relationship between each functional attribute and the safety requirements (i.e., functional safety requirements) to be met by the corresponding functional attribute, and each functional attribute may correspond to multiple functional safety requirements. Optionally, the functional safety requirements to be met corresponding to different functional attributes may be the same or different.

[0081] For example, when the functional attributes of the target software system determined by the computer device include a personnel management system, internal employees of the enterprise, a Web application system, a mobile application system, and a WeChat applet, based on the above-mentioned first corresponding relationship, the computer device can determine the functional safety requirements corresponding to each of the above-mentioned functional attributes.

[0082] S220. Obtain a union of functional safety requirements corresponding to the same functional dimension to obtain a set of requirements of the same dimension.

[0083] Specifically, the computer device obtains the union of functional safety requirements corresponding to the same functional dimension to obtain a set of requirements of the same dimension. For example, functional safety requirement 1 corresponding to the personnel management system corresponds to the functional dimension of system category, and after taking the union, the same-dimensional requirement set 1 is obtained, which is still functional safety requirement 1; functional safety requirement 2 corresponding to internal employees of the enterprise corresponds to the functional dimension of user type, and after taking the union, the same-dimensional requirement set 2 is obtained, which is still functional safety requirement 2; functional safety requirements 3 to 5 corresponding to the Web application system, mobile application system and WeChat applet respectively correspond to the functional dimension of client architecture, and after taking the union, the same-dimensional requirement set 3 is obtained.

[0084] S230. Obtain the intersection of the same-dimensional requirement sets corresponding to different functional dimensions to obtain a first security requirement set.

[0085] Specifically, the computer device obtains the intersection of all the same-dimensional requirement sets corresponding to different functional dimensions to obtain the first security requirement set of the target software system. Continuing with the above example, the computer device obtains the intersection of the same-dimensional requirement set 1, the same-dimensional requirement set 2, and the same-dimensional requirement set 3, and the obtained requirement set is the first security requirement set.

[0086] It should be noted that the same-dimensional requirement sets corresponding to different functional dimensions must include the security requirements necessary for designing software requirements. Therefore, there must be an intersection between the same-dimensional requirement sets corresponding to different functional dimensions, that is, the intersection of the same-dimensional requirement sets corresponding to different functional dimensions is not empty, and the above-mentioned first security requirement set can definitely be obtained.

[0087] In this embodiment, the computer device determines the functional safety requirements corresponding to each functional attribute according to the first corresponding relationship, obtains the union of the functional safety requirements corresponding to the same functional dimension, obtains the same-dimensional requirement set, and then obtains the intersection of the same-dimensional requirement sets corresponding to different functional dimensions to obtain the first safety requirement set. The first corresponding relationship is the corresponding relationship between the functional attribute and the functional safety requirement. The functional safety requirement corresponding to each functional attribute can be accurately determined by using the above first corresponding relationship, thereby improving the accuracy of the first safety requirement set.

[0088] In one embodiment, in order to improve the accuracy of the determined second security requirement set, Figure 3 As shown, the above S120 includes:

[0089] S310. Determine the business security requirements corresponding to each business scenario according to the second corresponding relationship.

[0090] The second corresponding relationship includes a corresponding relationship between a business scenario and a business security requirement. Optionally, the second corresponding relationship includes a corresponding relationship between each business scenario and a security requirement (i.e., business security requirement) to be met by the business scenario. Optionally, the business security requirements to be met by different business scenarios may be the same or different.

[0091] For example, when the business scenarios of the target software system determined by the computer device include user registration, user login, password reset, and personal information maintenance, based on the above second corresponding relationship, the computer device can determine the business security requirements of each of the above business scenarios.

[0092] S320: Obtain a union of the business security requirements to obtain a second security requirement set.

[0093] Specifically, the computer device obtains the union of the obtained business security requirements to obtain the second security requirement set of the target software system. Continuing with the above example, the computer device obtains the union of business security requirement 1, business security requirement 2, business security requirement 3 and business security requirement 4, and the obtained requirement set is the second security requirement set.

[0094] In this embodiment, the computer device determines the business security requirements corresponding to each business scenario according to the second corresponding relationship, and obtains the union of the obtained business security requirements to obtain a second security requirement set. The second corresponding relationship is the corresponding relationship between the business scenario and the business security requirement. The business security requirement corresponding to each business scenario can be accurately determined by using the above second corresponding relationship, thereby improving the accuracy of the second security requirement set.

[0095] In one embodiment, to reduce the design difficulty of the target software system, the above S130 includes:

[0096] The intersection of the first security requirement set and the second security requirement set is obtained to obtain the security requirements of the target software system.

[0097] Specifically, the computer device obtains the intersection of the first security requirement set and the second security requirement set to obtain the security requirements of the target software system.

[0098] It should be noted that the first security requirement set determined by the functional attributes of the target software system and the second security requirement set determined by the business scenario of the target software system definitely include the security requirements necessary for designing software requirements. Therefore, there must be an intersection between the first security requirement set and the second security requirement set, that is, the intersection of the first security requirement set and the second security requirement set is not empty, and the security requirements of the target software system can definitely be obtained.

[0099] In this embodiment, the computer device directly obtains the intersection of the first security requirement set and the second security requirement set, that is, obtains the functional attributes of the target software system and the security requirements that need to be met by the business scenarios as the security requirements of the target software system, so as to simplify the security requirements of the target software system and reduce the design difficulty.

[0100] In one embodiment, in order to improve the practical significance of the security requirements of the target software system, the method further includes:

[0101] Determine the design plan of the target software system based on the security requirements of the target software system and the modification risk level of the target software system.

[0102] Among them, the transformation risk level is used to characterize the complexity of the design corresponding to the software system, which can be determined comprehensively based on the specific content to be transformed and the functional attributes of the software system itself. Optionally, the higher the transformation risk level, the more complex the corresponding software system is; conversely, the lower the transformation risk level, the simpler the corresponding software system is.

[0103] Optionally, a design solution library is pre-stored in the computer device, and the design solution library includes design solutions for various software systems. Each design solution corresponds to a set of security requirements and corresponding modification risk levels. The computer device can determine the corresponding design solution in the design solution library according to the determined security requirements and modification risk levels of the target software system, as the design solution for the target software system.

[0104] In this embodiment, the computer device can further determine the design plan of the target software system based on the security requirements of the target software system and the modification risk level of the target software system, providing a specific design plan for the designers of the target software system, thereby improving the practical utilization significance of the security requirements of the target software system while improving the design efficiency.

[0105] In one embodiment, the method further includes a process of determining the modification risk level of the target software system. To improve the accuracy of the modification risk level, Figure 4 As shown in Figure 1, the process of determining the renovation risk level specifically includes:

[0106] S410. Determine the system risk level of the target software system according to the functional attributes.

[0107] The system risk level is used to characterize the complexity of the software system's own functions, and can be determined based on the functional attributes of the software system itself. Optionally, the higher the system risk level, the more complex the functional attributes of the corresponding software system; conversely, the lower the system risk level, the simpler the functional attributes of the corresponding software system.

[0108] Optionally, the method may specifically include the following steps:

[0109] Determine the security risk value of the target software system based on functional attributes;

[0110] The system risk level of the target software system is determined by the risk safety value.

[0111] Specifically, the computer device can determine the security risk value corresponding to the target software system according to all functional attributes of the target software system, and then determine the system risk level according to the security risk value.

[0112] Optionally, the computer device may determine the security risk value corresponding to each functional attribute according to the risk correspondence relationship, and then obtain the sum of the security risk values corresponding to all functional attributes as the security risk value of the target software system, and determine that the system risk level to which the security risk value of the target software system belongs is the system risk level of the target software system. Among them, the risk correspondence relationship includes the correspondence relationship between the functional attribute and the security risk value, and each functional attribute corresponds to a specific security risk value.

[0113] Optionally, the system risk level may be determined as multiple levels according to different value ranges of the security risk value R corresponding to the target software system. For example, if R2 ≤ R ≤ R1, it is a high risk; if R3 ≤ R < R2, it is a medium risk; if R4 ≤ R < R3, it is a low risk.

[0114] S420. Obtain the system transformation content of the target software system, and determine the system transformation type according to the system transformation content.

[0115] Among them, the system transformation content includes the functional modules that software developers need to design. For example, architecture new module, identity authentication module, architecture change module, user information update module, interface adjustment module, etc.

[0116] Specifically, the computer device may obtain the system transformation content of the target software system based on the input or selection operation of the software developer on the function display interface, and compare it with the transformation type comparison table to determine the system transformation type corresponding to the system transformation content. Among them, multiple system transformation contents may correspond to multiple system transformation types, and the computer device selects the system transformation type with the highest risk level as the system transformation type of the target software system.

[0117] Optionally, the transformation type comparison table may be as shown in Table 1 below:

[0118] Table 1 System Transformation Type Comparison Table

[0119]

[0120] Among them, the risk level: new system > high-risk transformation system > medium-risk transformation system > low-risk transformation system.

[0121] S430. Determine the transformation risk level of the target software system according to the system risk level and the system transformation type.

[0122] Optionally, when the system transformation type includes new system, high-risk transformation system, medium-risk transformation system, and low-risk transformation system, and the system risk level includes high risk, medium risk, and low risk, the computer device may determine the transformation risk level of the target software system according to Table 2 below.

[0123] Table 2 Renovation risk level table

[0124]

[0125] Among them, the higher the transformation risk level, the greater the risk of system transformation, that is, level three > level two > level one.

[0126] Specifically, if the system transformation type is a new system, when the system risk level is low risk, the transformation risk level of the target software system is level two; when the system risk level is not low risk, the transformation risk level of the target software system is level three.

[0127] If the system transformation type is a high-risk transformation system, when the system risk level is high risk, the transformation risk level of the target software system is level three; when the system risk level is non-high risk, the transformation risk level of the target software system is level two.

[0128] If the system transformation type is a medium-risk transformation system, when the system risk level is low risk, the transformation risk level of the target software system is level one; when the system risk level is not low risk, the transformation risk level of the target software system is level two.

[0129] If the system transformation type is a low-risk transformation system, the transformation risk level of the target software system is level one.

[0130] In an optional embodiment, if Figure 5 As shown, the above-mentioned determination of the security risk value of the target software system based on the functional attributes includes:

[0131] S510. Determine the maximum security risk value of the functional attribute corresponding to each functional dimension according to the risk correspondence relationship.

[0132] Among them, the risk correspondence includes the correspondence between functional attributes and safety risk values.

[0133] Specifically, the computer device can determine the security risk value corresponding to each functional attribute according to the risk correspondence relationship, and determine the maximum security risk value of each functional dimension therefrom.

[0134] S520: Calculate the product of the maximum security risk value and the weight of the corresponding functional dimension, and calculate the sum of the products to obtain the security risk value of the target software system.

[0135] The weights of the corresponding functional dimensions may be determined according to the design requirements. For example, if the design requirements focus on meeting the security requirements of the system type, the weight corresponding to the system type may be greater than the weights corresponding to other functional dimensions.

[0136] Specifically, the computer device performs a weighted summation of the maximum security risk values ​​corresponding to each functional dimension to obtain the security risk value of the target software system. The security risk value R of the target software system satisfies the following formula:

[0137]

[0138] in, SI i The maximum security risk value = MAX(|OP1|,|OP2|,…,|OP m |)

[0139] SI i represents a functional dimension, each functional dimension may include at least one functional attribute, and each functional attribute corresponds to a security risk value OP. n is the number of functional dimensions, and m is the number of functional attributes under the corresponding functional dimension.

[0140] Optionally, the security risk value is divided into three levels: high, medium, and low. Among them, high = 1, medium = 0.5, and low = 0.2. Optionally, the system risk level R can also be divided into three levels. For example, 0.7≤R≤1.0 is a high risk; 0.5≤R<0.7 is a medium risk; 0.2≤R<0.5 is a low risk.

[0141] In this embodiment, the computer device determines the system risk level of the target software system based on the functional attributes. Specifically, the system risk level is determined through the security risk value of each functional attribute. At the same time, the system transformation content of the target software system is obtained, and the system transformation type is determined based on the system transformation content. The transformation risk level of the target software system is then determined by comprehensively considering the influence of both the system risk level and the system transformation type, thereby improving the accuracy of the determined transformation risk level.

[0142] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0143] Based on the same inventive concept, the embodiment of the present application also provides a security requirement analysis device for implementing the security requirement analysis method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more security requirement analysis device embodiments provided below can refer to the limitations of the security requirement analysis method above, and will not be repeated here.

[0144] In one embodiment, Figure 6 As shown, a security requirement analysis device is provided, including: a first requirement determination module 601, a second requirement determination module 602 and a system requirement determination module 603, wherein:

[0145] The first requirement determination module 601 is used to obtain the functional attributes of the target software system, and determine the first security requirement set of the target software system according to the functional attributes; wherein the first security requirement set includes multiple security requirements matching the functional attributes, and the functional attributes include attributes of the target software corresponding to at least two functional dimensions;

[0146] The second requirement determination module 602 is used to obtain the business scenario of the target software system and determine the second security requirement set of the target software system according to the business scenario; wherein the second security requirement set includes multiple security requirements matching the business scenario;

[0147] The system requirement determination module 603 is used to determine the security requirements of the target software system according to the first security requirement set and the second security requirement set.

[0148] In one embodiment, the first demand determination module 601 is specifically used to:

[0149] Determine the functional safety requirements corresponding to each functional attribute according to the first corresponding relationship; wherein the first corresponding relationship includes the corresponding relationship between the functional attributes and the functional safety requirements; obtain the union of the functional safety requirements corresponding to the same functional dimension to obtain a set of requirements of the same dimension; obtain the intersection of the sets of requirements of the same dimension corresponding to different functional dimensions to obtain a first set of safety requirements.

[0150] In one embodiment, the second demand determination module 602 is specifically configured to:

[0151] Determine the business security requirements corresponding to each business scenario according to the second corresponding relationship; wherein the second corresponding relationship includes the corresponding relationship between the business scenario and the business security requirements; obtain the union of the business security requirements to obtain a second security requirement set.

[0152] In one embodiment, the system requirement determination module 603 is specifically used to:

[0153] The intersection of the first security requirement set and the second security requirement set is obtained to obtain the security requirements of the target software system.

[0154] In one embodiment, the above device further includes a scheme design module:

[0155] The scheme design module is used to determine the design scheme of the target software system according to the security requirements of the target software system and the modification risk level of the target software system.

[0156] In one embodiment, the solution design module is specifically used to:

[0157] Determine the system risk level of the target software system based on functional attributes; obtain the system transformation content of the target software system, and determine the system transformation type based on the system transformation content; determine the transformation risk level of the target software system based on the system risk level and the system transformation type.

[0158] In one embodiment, the solution design module is specifically used to:

[0159] The security risk value of the target software system is determined based on the functional attributes; the system risk level of the target software system is determined by the risk security value.

[0160] In one embodiment, the solution design module is specifically used to:

[0161] Determine the maximum security risk value of the functional attribute corresponding to each functional dimension according to the risk correspondence relationship; wherein the risk correspondence relationship includes the correspondence between the functional attributes and the security risk values; calculate the product of the maximum security risk value and the weight of the corresponding functional dimension, and calculate the sum of the products to obtain the security risk value of the target software system.

[0162] In one embodiment, the solution design module is specifically used to:

[0163] The system transformation type corresponding to the system transformation content is determined according to the transformation correspondence relationship; wherein the transformation correspondence relationship includes the correspondence relationship between the system transformation content and the system transformation type.

[0164] In one embodiment, the solution design module is specifically used to:

[0165] If the system transformation type is a new system, when the system risk level is low risk, the transformation risk level of the target software system is level two; when the system risk level is not low risk, the transformation risk level of the target software system is level three; if the system transformation type is a high-risk transformation system, when the system risk level is high risk, the transformation risk level of the target software system is level three; when the system risk level is not high risk, the transformation risk level of the target software system is level two; if the system transformation type is a medium-risk transformation system, when the system risk level is low risk, the transformation risk level of the target software system is level one; when the system risk level is not low risk, the transformation risk level of the target software system is level two; if the system transformation type is a low-risk transformation system, the transformation risk level of the target software system is level one; among them, the higher the transformation risk level, the greater the system transformation risk.

[0166] Each module in the above security requirement analysis device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0167] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 7 As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a security requirements analysis method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a key, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0168] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0169] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0170] Acquire functional attributes of the target software system, and determine a first set of security requirements for the target software system based on the functional attributes; wherein the first set of security requirements includes multiple security requirements that match the functional attributes, and the functional attributes include attributes of the target software corresponding to at least two functional dimensions; acquire a business scenario of the target software system, and determine a second set of security requirements for the target software system based on the business scenario; wherein the second set of security requirements includes multiple security requirements that match the business scenario; determine the security requirements of the target software system based on the first set of security requirements and the second set of security requirements.

[0171] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0172] Determine the functional safety requirements corresponding to each functional attribute according to the first corresponding relationship; wherein the first corresponding relationship includes the corresponding relationship between the functional attributes and the functional safety requirements; obtain the union of the functional safety requirements corresponding to the same functional dimension to obtain a set of requirements of the same dimension; obtain the intersection of the sets of requirements of the same dimension corresponding to different functional dimensions to obtain a first set of safety requirements.

[0173] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0174] Determine the business security requirements corresponding to each business scenario according to the second corresponding relationship; wherein the second corresponding relationship includes the corresponding relationship between the business scenario and the business security requirements; obtain the union of the business security requirements to obtain a second security requirement set.

[0175] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0176] The intersection of the first security requirement set and the second security requirement set is obtained to obtain the security requirements of the target software system.

[0177] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0178] Determine the design plan of the target software system based on the security requirements of the target software system and the modification risk level of the target software system.

[0179] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0180] Determine the system risk level of the target software system based on functional attributes; obtain the system transformation content of the target software system, and determine the system transformation type based on the system transformation content; determine the transformation risk level of the target software system based on the system risk level and the system transformation type.

[0181] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0182] The security risk value of the target software system is determined based on the functional attributes; the system risk level of the target software system is determined by the risk security value.

[0183] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0184] Determine the maximum security risk value of the functional attribute corresponding to each functional dimension according to the risk correspondence relationship; wherein the risk correspondence relationship includes the correspondence between the functional attributes and the security risk values; calculate the product of the maximum security risk value and the weight of the corresponding functional dimension, and calculate the sum of the products to obtain the security risk value of the target software system.

[0185] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0186] The system transformation type corresponding to the system transformation content is determined according to the transformation correspondence relationship; wherein the transformation correspondence relationship includes the correspondence relationship between the system transformation content and the system transformation type.

[0187] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0188] If the system transformation type is a new system, when the system risk level is low risk, the transformation risk level of the target software system is level two; when the system risk level is not low risk, the transformation risk level of the target software system is level three; if the system transformation type is a high-risk transformation system, when the system risk level is high risk, the transformation risk level of the target software system is level three; when the system risk level is not high risk, the transformation risk level of the target software system is level two; if the system transformation type is a medium-risk transformation system, when the system risk level is low risk, the transformation risk level of the target software system is level one; when the system risk level is not low risk, the transformation risk level of the target software system is level two; if the system transformation type is a low-risk transformation system, the transformation risk level of the target software system is level one; among them, the higher the transformation risk level, the greater the system transformation risk.

[0189] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0190] Acquire functional attributes of the target software system, and determine a first set of security requirements for the target software system based on the functional attributes; wherein the first set of security requirements includes multiple security requirements that match the functional attributes, and the functional attributes include attributes of the target software corresponding to at least two functional dimensions; acquire a business scenario of the target software system, and determine a second set of security requirements for the target software system based on the business scenario; wherein the second set of security requirements includes multiple security requirements that match the business scenario; determine the security requirements of the target software system based on the first set of security requirements and the second set of security requirements.

[0191] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0192] Determine the functional safety requirements corresponding to each functional attribute according to the first corresponding relationship; wherein the first corresponding relationship includes the corresponding relationship between the functional attributes and the functional safety requirements; obtain the union of the functional safety requirements corresponding to the same functional dimension to obtain a set of requirements of the same dimension; obtain the intersection of the sets of requirements of the same dimension corresponding to different functional dimensions to obtain a first set of safety requirements.

[0193] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0194] Determine the business security requirements corresponding to each business scenario according to the second corresponding relationship; wherein the second corresponding relationship includes the corresponding relationship between the business scenario and the business security requirements; obtain the union of the business security requirements to obtain a second security requirement set.

[0195] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0196] The intersection of the first security requirement set and the second security requirement set is obtained to obtain the security requirements of the target software system.

[0197] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0198] Determine the design plan of the target software system based on the security requirements of the target software system and the modification risk level of the target software system.

[0199] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0200] Determine the system risk level of the target software system based on functional attributes; obtain the system transformation content of the target software system, and determine the system transformation type based on the system transformation content; determine the transformation risk level of the target software system based on the system risk level and the system transformation type.

[0201] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0202] The security risk value of the target software system is determined based on the functional attributes; the system risk level of the target software system is determined by the risk security value.

[0203] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0204] Determine the maximum security risk value of the functional attribute corresponding to each functional dimension according to the risk correspondence relationship; wherein the risk correspondence relationship includes the correspondence between the functional attributes and the security risk values; calculate the product of the maximum security risk value and the weight of the corresponding functional dimension, and calculate the sum of the products to obtain the security risk value of the target software system.

[0205] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0206] The system transformation type corresponding to the system transformation content is determined according to the transformation correspondence relationship; wherein the transformation correspondence relationship includes the correspondence relationship between the system transformation content and the system transformation type.

[0207] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0208] If the system transformation type is a new system, when the system risk level is low risk, the transformation risk level of the target software system is level two; when the system risk level is not low risk, the transformation risk level of the target software system is level three; if the system transformation type is a high-risk transformation system, when the system risk level is high risk, the transformation risk level of the target software system is level three; when the system risk level is not high risk, the transformation risk level of the target software system is level two; if the system transformation type is a medium-risk transformation system, when the system risk level is low risk, the transformation risk level of the target software system is level one; when the system risk level is not low risk, the transformation risk level of the target software system is level two; if the system transformation type is a low-risk transformation system, the transformation risk level of the target software system is level one; among them, the higher the transformation risk level, the greater the system transformation risk.

[0209] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0210] Acquire functional attributes of the target software system, and determine a first set of security requirements for the target software system based on the functional attributes; wherein the first set of security requirements includes multiple security requirements that match the functional attributes, and the functional attributes include attributes of the target software corresponding to at least two functional dimensions; acquire a business scenario of the target software system, and determine a second set of security requirements for the target software system based on the business scenario; wherein the second set of security requirements includes multiple security requirements that match the business scenario; determine the security requirements of the target software system based on the first set of security requirements and the second set of security requirements.

[0211] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0212] Determine the functional safety requirements corresponding to each functional attribute according to the first corresponding relationship; wherein the first corresponding relationship includes the corresponding relationship between the functional attributes and the functional safety requirements; obtain the union of the functional safety requirements corresponding to the same functional dimension to obtain a set of requirements of the same dimension; obtain the intersection of the sets of requirements of the same dimension corresponding to different functional dimensions to obtain a first set of safety requirements.

[0213] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0214] Determine the business security requirements corresponding to each business scenario according to the second corresponding relationship; wherein the second corresponding relationship includes the corresponding relationship between the business scenario and the business security requirements; obtain the union of the business security requirements to obtain a second security requirement set.

[0215] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0216] The intersection of the first security requirement set and the second security requirement set is obtained to obtain the security requirements of the target software system.

[0217] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0218] Determine the design plan of the target software system based on the security requirements of the target software system and the modification risk level of the target software system.

[0219] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0220] Determine the system risk level of the target software system based on functional attributes; obtain the system transformation content of the target software system, and determine the system transformation type based on the system transformation content; determine the transformation risk level of the target software system based on the system risk level and the system transformation type.

[0221] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0222] The security risk value of the target software system is determined based on the functional attributes; the system risk level of the target software system is determined by the risk security value.

[0223] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0224] Determine the maximum security risk value of the functional attribute corresponding to each functional dimension according to the risk correspondence relationship; wherein the risk correspondence relationship includes the correspondence between the functional attributes and the security risk values; calculate the product of the maximum security risk value and the weight of the corresponding functional dimension, and calculate the sum of the products to obtain the security risk value of the target software system.

[0225] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0226] The system transformation type corresponding to the system transformation content is determined according to the transformation correspondence relationship; wherein the transformation correspondence relationship includes the correspondence relationship between the system transformation content and the system transformation type.

[0227] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0228] If the system transformation type is a new system, when the system risk level is low risk, the transformation risk level of the target software system is level two; when the system risk level is not low risk, the transformation risk level of the target software system is level three; if the system transformation type is a high-risk transformation system, when the system risk level is high risk, the transformation risk level of the target software system is level three; when the system risk level is not high risk, the transformation risk level of the target software system is level two; if the system transformation type is a medium-risk transformation system, when the system risk level is low risk, the transformation risk level of the target software system is level one; when the system risk level is not low risk, the transformation risk level of the target software system is level two; if the system transformation type is a low-risk transformation system, the transformation risk level of the target software system is level one; among them, the higher the transformation risk level, the greater the system transformation risk.

[0229] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0230] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0231] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0232] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A security requirements analysis method, characterized in that: The method comprises: Acquire functional attributes of a target software system, and determine a first set of security requirements for the target software system according to the functional attributes; wherein the first set of security requirements includes a plurality of security requirements matching the functional attributes, and the functional attributes include attributes of the target software corresponding to at least two functional dimensions; Acquire a business scenario of the target software system, and determine a second security requirement set of the target software system according to the business scenario; wherein the second security requirement set includes a plurality of security requirements matching the business scenario; Determining the security requirements of the target software system according to the first security requirement set and the second security requirement set; The determining, according to the functional attributes, a first set of security requirements of the target software system includes: Determine the functional safety requirement corresponding to each functional attribute according to a first corresponding relationship; wherein the first corresponding relationship includes a corresponding relationship between the functional attribute and the functional safety requirement; Obtain the union of functional safety requirements corresponding to the same functional dimension to obtain a set of requirements in the same dimension; Obtaining the intersection of the same-dimensional requirement sets corresponding to different functional dimensions to obtain the first security requirement set; The determining, according to the business scenario, a second set of security requirements for the target software system includes: Determine the business security requirements corresponding to each business scenario according to the second corresponding relationship; wherein the second corresponding relationship includes the corresponding relationship between the business scenario and the business security requirements; Obtaining a union of the business security requirements to obtain the second security requirement set; The determining the security requirements of the target software system according to the first security requirement set and the second security requirement set includes: The intersection of the first security requirement set and the second security requirement set is obtained to obtain the security requirements of the target software system.

2. The method according to claim 1, characterized in that The method further comprises: A design scheme for the target software system is determined according to the security requirements of the target software system and the modification risk level of the target software system.

3. The method according to claim 2, characterized in that Determine the transformation risk level of the target software system, including: Determining a system risk level of the target software system according to the functional attributes; Acquiring system transformation content of the target software system, and determining a system transformation type according to the system transformation content; The transformation risk level of the target software system is determined according to the system risk level and the system transformation type.

4. The method according to claim 3, characterized in that: Determining the system risk level of the target software system according to the functional attributes includes: Determining a security risk value of the target software system according to the functional attributes; The system risk level of the target software system is determined according to the security risk value.

5. The method according to claim 4, characterized in that Determining the security risk value of the target software system according to the functional attribute includes: Determine the maximum security risk value of the functional attribute corresponding to each functional dimension according to the risk correspondence relationship; wherein the risk correspondence relationship includes the correspondence relationship between the functional attribute and the security risk value; The product of the maximum security risk value and the weight of the corresponding functional dimension is calculated, and the sum of the products is calculated to obtain the security risk value of the target software system.

6. The method according to claim 3, characterized in that The determining of the system transformation type according to the system transformation content includes: The system transformation type corresponding to the system transformation content is determined according to the transformation correspondence relationship; wherein the transformation correspondence relationship includes the correspondence between the system transformation content and the system transformation type.

7. The method according to claim 3, characterized in that Determining the transformation risk level of the target software system according to the system risk level and the system transformation type includes: If the system transformation type is a new system, when the system risk level is low risk, the transformation risk level of the target software system is level 2; when the system risk level is not low risk, the transformation risk level of the target software system is level 3; If the system transformation type is a high-risk transformation system, when the system risk level is high risk, the transformation risk level of the target software system is level three; when the system risk level is not high risk, the transformation risk level of the target software system is level two; If the system transformation type is a medium-risk transformation system, when the system risk level is low risk, the transformation risk level of the target software system is level one; when the system risk level is not low risk, the transformation risk level of the target software system is level two; If the system transformation type is a low-risk transformation system, the transformation risk level of the target software system is level one; wherein, the higher the transformation risk level, the greater the system transformation risk.

8. A security requirement analysis device, characterized in that: The device comprises: A first requirement determination module, configured to obtain functional attributes of a target software system, and determine a first security requirement set of the target software system according to the functional attributes; wherein the first security requirement set includes a plurality of security requirements matching the functional attributes, and the functional attributes include attributes of the target software corresponding to at least two functional dimensions; A second requirement determination module, used to obtain a business scenario of the target software system, and determine a second security requirement set of the target software system according to the business scenario; wherein the second security requirement set includes a plurality of security requirements matching the business scenario; A system requirement determination module, configured to determine the security requirements of the target software system according to the first security requirement set and the second security requirement set; The first demand determination module is further used for: Determine the functional safety requirement corresponding to each functional attribute according to a first corresponding relationship; wherein the first corresponding relationship includes a corresponding relationship between the functional attribute and the functional safety requirement; Obtain the union of functional safety requirements corresponding to the same functional dimension to obtain a set of requirements in the same dimension; Obtaining the intersection of the same-dimensional requirement sets corresponding to different functional dimensions to obtain the first security requirement set; The second demand determination module is further used to: Determine the business security requirements corresponding to each business scenario according to the second corresponding relationship; wherein the second corresponding relationship includes the corresponding relationship between the business scenario and the business security requirements; Obtaining a union of the business security requirements to obtain the second security requirement set; The system requirement determination module is further used for: The intersection of the first security requirement set and the second security requirement set is obtained to obtain the security requirements of the target software system.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images