Cloud environment security test method, device, equipment and product

By identifying risks in the cloud environment and generating negative demand and misuse use case models, external threat testing is solved, the problem of failure to pay attention to external risks in the existing technology is improved, and the security and monitoring capabilities of the cloud environment are improved, and sensitivity is avoided. Information leakage.

CN118940265APending Publication Date: 2024-11-12CHINA MOBILE (SUZHOU) SOFTWARE TECH CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410987337.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-23
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

Existing cloud environment security testing technology is mainly carried out from the inside, and fails to effectively pay attention to external risks, resulting in a lack of comprehensiveness and insufficient monitoring capabilities, which may cause sensitive information leakage.

Method used

By identifying risks in the cloud environment to be tested, generating risk models, and converting them into negative demand models and misuse use case models, testing the direction of external threats, describing the attack activities of malicious users, and enhancing the comprehensiveness and sustainability of testing Monitoring capability.

Benefits of technology

Improves the security and monitoring capabilities of cloud environments, avoids the leakage of sensitive information, and enhances the defense capabilities of external threats.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118940265A_ABST
    Figure CN118940265A_ABST
Patent Text Reader

Abstract

The invention provides a cloud environment security test method, device, equipment and product, and relates to the technical field of cloud computing, and the method comprises the steps: recognizing a risk in a to-be-tested cloud environment model, and generating a risk model; converting the risk model into a negative demand model according to the negative demand; the negative requirements are unexpected function or performance requirements in the to-be-tested cloud environment model and are obtained according to risk derivation in the risk model; converting the negative demand model into a misuse case model according to the misuse case, wherein the misuse case model is used for describing an attack activity of a malicious user on the to-be-tested cloud environment model; and testing the to-be-tested cloud environment model according to the misuse case model. According to the method for testing the cloud environment model through the misuse case model used for describing the attack activity of malicious users on the to-be-tested cloud environment model, the cloud environment is tested from the direction of external threats, the test comprehensiveness is enhanced, the continuous monitoring capacity is improved, and leakage of sensitive information is avoided.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of cloud computing technology, and in particular to a method, device, equipment and product for cloud environment security testing. Background Art

[0002] Cloud constitutes an advancement of service-oriented systems. For enterprises, consuming services provided by the cloud can save time and money in developing and adapting applications. In order to ensure the security of cloud applications, in addition to functional and non-functional correctness testing, dedicated security testing is also required. Security testing is to discover potential security vulnerabilities and defects and evaluate the system's defense capabilities against various security threats.

[0003] At present, the security testing technology solutions for cloud applications mainly include penetration testing, security code review, data protection testing, security log scanning and other means. Most software security testing is carried out based on the principle of reverse design of defect space, that is, to check in advance where there may be security risks, and then test these possible risks. Therefore, the reverse testing process starts from the defect space, establishes a defect threat model, finds intrusion points through the threat model, and performs scanning tests on the intrusion points for known vulnerabilities. However, this method tests from within the cloud environment, without paying attention to the review of external risks, which may lead to ignoring external threats, lack of comprehensiveness, insufficient continuous monitoring capabilities, and leakage of sensitive information. Summary of the invention

[0004] The purpose of the present invention is to provide a method, device, equipment and product for cloud environment security testing, which is used to solve the problem in the prior art that testing is performed from within the cloud environment without paying attention to the review of external risks, which may lead to ignoring external threats, lack of comprehensiveness, insufficient continuous monitoring capabilities, and leakage of sensitive information.

[0005] To achieve the above object, an embodiment of the present invention provides a method for cloud environment security testing, which includes:

[0006] Identify risks in the cloud environment model to be tested and generate a risk model;

[0007] Converting the risk model into a negative demand model according to negative demands; wherein the negative demands are functions or performance requirements that are not expected to appear in the cloud environment model to be tested; and the negative demands are derived according to the risks in the risk model;

[0008] The negative demand model is converted into a misuse use case model according to the misuse use case; wherein the misuse use case model is used to describe the attack activities of malicious users on the cloud environment model to be tested; the misuse use case is generated based on the negative demand;

[0009] The cloud environment model to be tested is tested according to the misuse use case model.

[0010] Optionally, in the method, the step of identifying risks in the cloud environment model to be tested and generating a risk model comprises:

[0011] Identifying the risk in the cloud environment model to be tested through a vulnerability library;

[0012] The risk is described using a domain specific language (DSL) to generate the risk model.

[0013] Optionally, the method, wherein converting the risk model into a negative demand model according to the negative demand comprises:

[0014] Creating a negative demand model to be changed according to the negative demand;

[0015] If the negative demand model to be changed needs to be manually modified, the modification state is entered;

[0016] If an external event occurs and the risk model is modified, it enters the integrated change state;

[0017] The negative demand model to be changed is integrated and changed into the risk model to obtain the negative demand model.

[0018] Optionally, the method, wherein converting the negative requirement model into a misuse use case model according to the misuse use case comprises:

[0019] Creating a misuse use case model to be changed according to the misuse use case;

[0020] If the misused use case model to be changed needs to be manually modified, the modification state is entered;

[0021] If an external event occurs, the negative demand model is modified and the integration change state is entered;

[0022] The misuse use case model to be changed is integrated and changed into the negative demand model to obtain the misuse use case model.

[0023] Optionally, in the method, the step of testing the cloud environment model to be tested according to the misuse use case model comprises:

[0024] Obtaining a unified modeling language diagram according to the misuse use case model;

[0025] Generate test code according to the unified modeling language diagram;

[0026] The test code is used to test the cloud environment model to be tested.

[0027] Optionally, the method further comprises:

[0028] When the misuse case fails the test, the cloud environment model to be tested is updated to obtain the updated cloud environment model.

[0029] In order to achieve the above object, an embodiment of the present invention further provides a cloud environment security testing device, which includes:

[0030] The first generation module is used to identify risks in the cloud environment model to be tested and generate a risk model;

[0031] A first processing module is used to convert the risk model into a negative demand model according to negative demands; wherein the negative demands are functions or performance requirements that are not expected to appear in the cloud environment model to be tested; and the negative demands are derived according to the risks in the risk model;

[0032] A second processing module is used to convert the negative demand model into a misuse use case model according to the misuse use case; wherein the misuse use case model is used to describe the attack activities of malicious users on the cloud environment model to be tested; and the misuse use case is generated based on the negative demand;

[0033] The third processing module is used to test the cloud environment model to be tested according to the misuse use case model.

[0034] In order to achieve the above-mentioned purpose, an embodiment of the present invention also provides a network device, including: a processor, a memory, and a program or instruction stored in the memory and executable on the processor; wherein, when the processor executes the program or instruction, the method of cloud environment security testing as described above is implemented.

[0035] In order to achieve the above-mentioned purpose, an embodiment of the present invention further provides a readable storage medium on which a program or instruction is stored, wherein when the program or instruction is executed by a processor, the steps in the method for cloud environment security testing as described above are implemented.

[0036] In order to achieve the above-mentioned purpose, an embodiment of the present invention further provides a computer program product, which includes computer instructions, and when the computer instructions are executed by a processor, the steps of the method for cloud environment security testing as described above are implemented.

[0037] The beneficial effects of the above technical solution of the present invention are as follows:

[0038] The embodiment of the present invention converts the risk model generated by identifying the risks in the cloud environment model to be tested into a negative demand model, and further converts it into a misuse use case model to test the cloud environment model to be tested. The method of testing the cloud environment model by using the misuse use case model for describing the attack activities of malicious users on the cloud environment model to be tested tests the cloud environment from the direction of external threats. Compared with the existing technology that only tests from within the cloud environment, the comprehensiveness is enhanced, the continuous monitoring capability is improved, and the leakage of sensitive information is avoided. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A schematic diagram of a cloud environment security testing method according to an embodiment of the present invention;

[0040] Figure 2 A flowchart of a method for cloud environment security testing according to an embodiment of the present invention;

[0041] Figure 3 A negative requirement derivation flow chart of the cloud environment security testing method according to an embodiment of the present invention;

[0042] Figure 4 A flowchart of the model evolution of the cloud environment security testing method according to an embodiment of the present invention;

[0043] Figure 5 A schematic diagram of a cloud environment security test device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0044] In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0045] It should be understood that the references to "one embodiment" or "an embodiment" throughout the specification mean that the specific features, structures, or characteristics associated with the embodiment are included in at least one embodiment of the present invention. Therefore, the references to "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0046] In various embodiments of the present invention, it should be understood that the size of the serial numbers of the following processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0047] Additionally, the terms "system" and "network" are often used interchangeably herein.

[0048] In the embodiments provided in the present application, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0049] For ease of understanding, some contents involved in the embodiments of the present invention are described below:

[0050] like Figure 1 As shown, a cloud environment security testing method according to an embodiment of the present invention includes:

[0051] S10, identifying risks in the cloud environment model to be tested and generating a risk model;

[0052] It should be noted that the embodiment of the present invention separates the test-related information from the cloud environment model to be tested and establishes a Figure 2 The independent test model shown first performs risk analysis on the cloud environment model to be tested (CUT), identifies the risks therein, and generates the risk model (RM).

[0053] S20, converting the risk model into a negative demand model according to negative demands; wherein the negative demands are functions or performance requirements that are not expected to appear in the cloud environment model to be tested; and the negative demands are derived according to the risks in the risk model;

[0054] It should be noted that, based on the risk model, a series of negative requirements are obtained, and the negative requirements describe the functional or performance requirements that should not appear in the cloud environment model to be tested; Figure 3 As shown, an example is now provided. During the risk analysis and identification phase, a security risk was discovered: unauthorized users can access sensitive data. Based on this security risk, a negative requirement can be derived and summarized: access to sensitive data can be restricted to authorized users only. Therefore, the requirement is defined: only authorized users can access sensitive data, and unauthorized users should be blocked from access or have their access rights restricted. Through this negative requirement, it can be clearly required that the system verify and authorize user identities when accessing sensitive data, and implement appropriate access control measures to ensure that only authorized users can obtain access rights. Further, as Figure 2 As shown, the risk model (RM) is converted into the negative demand model (NRM) according to the negative demand.

[0055] S30, converting the negative demand model into a misuse use case model according to the misuse use case; wherein the misuse use case model is used to describe the attack activities of malicious users on the cloud environment model to be tested; and the misuse use case is generated based on the negative demand;

[0056] It should be noted that, through model conversion, an effective misuse use case model is obtained from the negative demand model, and a model that can describe possible and executable attacks on the cloud environment model to be tested is obtained. The misuse use case model describes the attack activities carried out by the user on the cloud environment model to be tested and tests them in sequence, for example, injecting the attack cloud through SOAP (Simple Object Access Protocol). Since the risk model has been manually edited, the misuse use case model can accurately describe the possible attacks on the cloud environment model to be tested. This method can improve the ability to test the security and reliability of the cloud environment model to be tested.

[0057] S40: Testing the cloud environment model to be tested according to the misuse use case model.

[0058] In this embodiment, the risk model generated by identifying the risks in the cloud environment model to be tested is converted into the negative demand model, and further converted into the misuse use case model, and the cloud environment model to be tested is tested. The method of testing the cloud environment model by using the misuse use case model for describing the attack activities of malicious users on the cloud environment model to be tested is used to test the cloud environment from the direction of external threats. Compared with the existing technology that only tests from within the cloud environment, the comprehensiveness is enhanced, the continuous monitoring capability is improved, and the leakage of sensitive information is avoided.

[0059] Optionally, in the method, step S10 includes:

[0060] Identifying the risk in the cloud environment model to be tested through a vulnerability library;

[0061] The risk is described using a domain specific language (DSL) to generate the risk model.

[0062] In this embodiment, if Figure 2As shown, the defects in the cloud environment model to be tested are identified through the vulnerability library. Since the update of the vulnerability library may not be timely or there are errors in identifying risks, the manual editing function is still retained when establishing the risk, so that the risk can be modified or a new risk description can be added as needed. The risk descriptions identified in the risk model include the threat level of assets and specific risks, such as the possibility of SOAP injection that may affect specific services. Therefore, it is also necessary to introduce a domain-specific language DSL (domain-specific language) to describe the risks, such as defining a security assessment rule. The format of each rule is rule "rule name", and then the triggering condition of the rule is described in the when block, and finally the operation after the rule is triggered is defined in the then block.

[0063] The specific code is as follows:

[0064] rule "Security Assessment Rule 1"

[0065] when

[0066] averageTemperature>30

[0067] and(humidity>80or precipitation>50)

[0068] then

[0069] riskLevel = "High Risk"

[0070] end.

[0071] Optionally, in the method, step S20 includes:

[0072] Creating a negative demand model to be changed according to the negative demand;

[0073] If the negative demand model to be changed needs to be manually modified, the modification state is entered;

[0074] If an external event occurs and the risk model is modified, it enters the integrated change state;

[0075] The negative demand model to be changed is integrated and changed into the risk model to obtain the negative demand model.

[0076] In this embodiment, the external event can be regarded as a malicious attack event or a third-party service failure event, wherein a malicious attack event is a denial of service (DDoS) attack, which attempts to make the cloud service unavailable, or attempts to conduct a remote code execution attack through a vulnerability to obtain unauthorized access rights; a third-party service failure event is an event in which the cloud service provider may face hardware failure, network interruption and other problems that may lead to degradation of model performance.

[0077] Optionally, in the method, step S30 includes:

[0078] Creating a misuse use case model to be changed according to the misuse use case;

[0079] If the misused use case model to be changed needs to be manually modified, the modification state is entered;

[0080] If an external event occurs, the negative demand model is modified and the integration change state is entered;

[0081] The misuse use case model to be changed is integrated and changed into the negative demand model to obtain the misuse use case model.

[0082] In this embodiment, Figure 2 The transformation process of the test model shown is evolved in a change-driven manner, using Figure 4The state machine in the embodiment of the present invention is used to convert, wherein the state machine is used to describe the state of the system in different time periods and a mathematical model of conversion operations that may be performed when receiving a specific event. The state machine used in the embodiment of the present invention has four states, namely, creation (new), modification (modified), integration of changes (incorporateChanges) and completion (clean), wherein the modified state is the state of inputting or propagating changes, and the incorporateChanges state is the state of inputting or integrating changes. A newly created model is in the new state, including creating the negative demand model to be changed according to the negative demand and creating the misuse use case model to be changed according to the misuse use case; it can be converted to two states, namely modified and incorporateChanges. If the model is manually modified, it will trigger the conversion to the modified state; and if an external event occurs, triggering the modification of the previous model (wherein, in the case where the newly created model is the negative demand model to be changed, the previous model is the risk model, and in the case where the newly created model is the misuse use case model to be changed, the previous model is the negative demand model), it will trigger the conversion to the incorporateChanges state. If the current state of the model is incorporateChanges, it can only switch to the modified state after applying all changes. After all changes are delivered, the model switches to the clean state, indicating that all changes to the model have been completed, that is, the negative demand model or the misuse use case model has been obtained. When the model enters the modified state, an external event is triggered, which is triggered by the previous model. The purpose of this event is to trigger the model to enter the incorporateChanges state. In the modified state, some changes or modifications may have been applied to the model, and the incorporateChanges state represents the process of applying these changes. In this process, changes are adapted to the model through model-to-model conversion (Model-to-Model, M2M for short) and merging existing models with newly generated models, so that the risk model is converted to the negative demand model, and then from the negative demand model to the misuse use case model. After a change that requires manual modification or is triggered by an external event is completed, the model reaches the clean state. At this time, the clean state sends a message to the modified and incorporateChanges states in the model to inform that the model has been modified or the model change has been accepted.

[0083] Model-driven security testing can help improve the security of cloud environments through fine-grained testing, efficient test execution, and the ability to discover security vulnerabilities in advance. It can also help discover and prevent security vulnerabilities in advance, and reduce the losses to enterprises caused by security incidents, including potential economic and reputation losses caused by data leakage, service interruption, etc.

[0084] Optionally, in the method, step S40 includes:

[0085] Obtaining a unified modeling language diagram according to the misuse use case model;

[0086] Generate test code according to the unified modeling language diagram;

[0087] The test code is used to test the cloud environment model to be tested.

[0088] In this embodiment, a template-based Model-2-Text code generator is used to generate corresponding text codes according to a Unified Modeling Language (UML) diagram to convert the misuse case model into the test code. The code generator can be adjusted to meet the requirements of mapping from the misuse case model to code and generating correct test code. For example, when access to sensitive data needs to be controlled, an authorization mechanism can be used to limit access rights.

[0089] public class SensitiveDataAccess{

[0090] public boolean isUserAuthorized(User user){

[0091] / / Check if the user is authorized

[0092] / / Assume that there is an authorization mechanism or user management system that can be used to verify user identity and permissions

[0093] if(user!=null&&user.isAuthorized()){

[0094] return true;

[0095] }

[0096] return false;

[0097] }

[0098] public String getSensitiveData(User user){

[0099] if (isUserAuthorized (user)) {

[0100] / / Logic for obtaining sensitive data

[0101] / / Assume there is sensitive data in the database or other storage system

[0102] return "sensitive data content";

[0103] }else{

[0104] throw new UnauthorizedAccessException("Unauthorized users cannot access sensitive data");

[0105] }

[0106] }

[0107] / / Other business logic and methods...

[0108] }.

[0109] In the above code, the SensitiveDataAccess class encapsulates the access operation to sensitive data. Among them, the isUserAuthorized method is used to check whether the user is authorized.

[0110] In the getSensitiveData method, the isUserAuthorized method is first called to verify whether the user is authorized. If the user is authorized, the logic of obtaining sensitive data is executed and the corresponding data is returned. On the contrary, if the user is not authorized, an UnauthorizedAccessException exception is thrown, indicating that unauthorized users cannot access sensitive data.

[0111] The mapping from the misuse use case model to code in the above process can simplify the code generation process. By using the existing misuse use case model to realize code generation, redundancy and complexity can be reduced in the code generation process.

[0112] Optionally, the method further comprises:

[0113] When the misuse case fails the test, the cloud environment model to be tested is updated to obtain the updated cloud environment model.

[0114] In this embodiment, if the misuse case fails the test, it will affect the positive requirements and risk avoidance measures in the risk model, and will be updated and improved, thereby updating the cloud environment model to be tested.

[0115] It should be noted that the embodiment of the present invention first separates the test-related information from the cloud environment model to be tested and establishes an independent test model. In this way, on the one hand, the cloud environment model can be developed independently, and on the other hand, the close association between the cloud environment model and the test model makes it possible to customize detailed tests according to the specific system. The cloud environment model describes the interfaces, classes and operations of the cloud environment to be tested. In the cloud computing environment, SaaS, IaaS, and PaaS will be abstracted as services, providing various interfaces and functions, which can be called and accessed from the outside. However, it is not enough to consider only the interface definition, so it is necessary to further study the implementation classes and operations, because they may have design defects that lead to security risks. Using the cloud abstraction level in the cloud environment model can easily adapt to various types of cloud systems.

[0116] The embodiment of the present invention proposes a new model-driven security testing method for cloud environments, which uses negative requirements derived from risk analysis to define misuse cases. First, risk analysis is performed to determine the security risks and potential threats in the cloud environment. According to the results of the risk analysis, negative requirements are defined as key indicators for security testing. Misuse cases are defined using information derived from negative requirements, and the misuse cases are compared with the model of the cloud environment to find potential security weaknesses or loopholes, and corresponding security tests are performed. Model-driven testing can be performed automatically to improve the repeatability and efficiency of testing. Through this model-driven security testing method, the security requirements of the cloud environment can be more comprehensively covered, and possible security loopholes and potential attack risks can be found. This helps to improve the security of the cloud environment and reduce potential security threats. In addition, fine-grained security testing of the cloud environment can be provided, and this precision and accuracy helps to find more security loopholes and potential threats; and it can be integrated with other model-driven security testing technologies and tools, and supports further expansion and customization, which makes it flexible and adaptable to different cloud environments and security requirements.

[0117] like Figure 5 As shown, in order to achieve the above-mentioned purpose, an embodiment of the present invention further provides a cloud environment security testing device, which includes:

[0118] The first generating module 501 is used to identify risks in the cloud environment model to be tested and generate a risk model;

[0119] A first processing module 502 is used to convert the risk model into a negative demand model according to negative demands; wherein the negative demands are functions or performance requirements that are not expected to appear in the cloud environment model to be tested; and the negative demands are derived according to the risks in the risk model;

[0120] The second processing module 503 is used to convert the negative demand model into a misuse use case model according to the misuse use case; wherein the misuse use case model is used to describe the attack activities of malicious users on the cloud environment model to be tested; and the misuse use case is generated based on the negative demand;

[0121] The third processing module 504 is used to test the cloud environment model to be tested according to the misuse use case model.

[0122] Optionally, in the device, the first generating module 501 includes:

[0123] A first identification unit, configured to identify the risk in the cloud environment model to be tested through a vulnerability library;

[0124] The first generating unit is used to describe the risk by using a domain specific language DSL to generate the risk model.

[0125] Optionally, in the device, the first processing module 502 includes:

[0126] A first creating unit, configured to create a negative demand model to be changed according to the negative demand;

[0127] A first processing unit, configured to enter a modification state if the negative demand model to be modified needs to be manually modified;

[0128] A second processing unit is used to modify the risk model if an external event occurs, and then enter an integrated change state;

[0129] The first acquisition unit is used to integrate the negative demand model to be changed into the risk model to acquire the negative demand model.

[0130] Optionally, in the device, the second processing module 503 includes:

[0131] A second creation unit, configured to create a misuse use case model to be changed according to the misuse use case;

[0132] A third processing unit, configured to enter a modification state if the misused use case model to be modified needs to be manually modified;

[0133] a fourth processing unit, for modifying the negative demand model if an external event occurs, and then entering an integration change state;

[0134] The second acquisition unit is used to integrate the misuse use case model to be changed into the negative demand model to acquire the misuse use case model.

[0135] Optionally, in the device, the third processing module 504 includes:

[0136] A third acquisition unit is used to acquire a unified modeling language diagram according to the misuse use case model;

[0137] A second generating unit, configured to generate test code according to the unified modeling language diagram;

[0138] The fifth processing unit is used to test the cloud environment model to be tested by using the test code.

[0139] Optionally, the device further comprises:

[0140] The first acquisition module is used to update the cloud environment model to be tested and acquire the updated cloud environment model when the misuse case fails the test.

[0141] It should be noted here that the above-mentioned device provided in the embodiment of the present invention can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0142] In order to achieve the above-mentioned purpose, an embodiment of the present invention also provides a network device, including: a processor, a memory, and a program or instruction stored in the memory and executable on the processor; wherein, when the processor executes the program or instruction, the method of cloud environment security testing as described above is implemented.

[0143] In order to achieve the above-mentioned purpose, an embodiment of the present invention further provides a readable storage medium on which a program or instruction is stored, wherein when the program or instruction is executed by a processor, the steps in the method for cloud environment security testing as described above are implemented.

[0144] In order to achieve the above-mentioned purpose, an embodiment of the present invention further provides a computer program product, which includes computer instructions, and when the computer instructions are executed by a processor, the steps of the method for cloud environment security testing as described above are implemented.

[0145] The above exemplary embodiments are described with reference to the accompanying drawings, and many different forms and embodiments are feasible without departing from the spirit and teachings of the present invention. Therefore, the present invention should not be constructed as a limitation of the exemplary embodiments proposed herein. More specifically, these exemplary embodiments are provided so that the present invention will be perfect and complete, and the scope of the present invention will be conveyed to those who are familiar with the technology. In these figures, the component sizes and relative sizes may be exaggerated for clarity. The terms used here are only based on the purpose of describing specific exemplary embodiments and are not intended to be limiting. As used herein, unless the text clearly indicates otherwise, the singular forms "one", "an" and "the" are intended to include these multiple forms. It will be further understood that the terms "including" and / or "comprising" when used in this specification indicate the presence of the features, integers, steps, operations, components and / or components, but do not exclude the presence or increase of one or more other features, integers, steps, operations, components, components and / or their groups. Unless otherwise indicated, when stated, a range of values ​​includes the upper and lower limits of that range and any subranges therebetween.

[0146] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for cloud environment security testing, characterized in that: include: Identify risks in the cloud environment model to be tested and generate a risk model; Converting the risk model into a negative demand model according to negative demands; wherein the negative demands are functions or performance requirements that are not expected to appear in the cloud environment model to be tested; and the negative demands are derived according to the risks in the risk model; The negative demand model is converted into a misuse use case model according to the misuse use case; wherein the misuse use case model is used to describe the attack activities of malicious users on the cloud environment model to be tested; the misuse use case is generated based on the negative demand; The cloud environment model to be tested is tested according to the misuse use case model.

2. The method according to claim 1, characterized in that The step of identifying risks in the cloud environment model to be tested and generating a risk model includes: Identifying the risk in the cloud environment model to be tested through a vulnerability library; The risk is described using a domain specific language (DSL) to generate the risk model.

3. The method according to claim 1, characterized in that The step of converting the risk model into a negative demand model according to the negative demand includes: Creating a negative demand model to be changed according to the negative demand; If the negative demand model to be changed needs to be manually modified, the modification state is entered; If an external event occurs and the risk model is modified, it enters the integrated change state; The negative demand model to be changed is integrated and changed into the risk model to obtain the negative demand model.

4. The method according to claim 1, characterized in that The converting the negative requirement model into a misuse use case model according to the misuse use case includes: Creating a misuse use case model to be changed according to the misuse use case; If the misused use case model to be changed needs to be manually modified, the modification state is entered; If an external event occurs, the negative demand model is modified and the integration change state is entered; The misuse use case model to be changed is integrated and changed into the negative demand model to obtain the misuse use case model.

5. The method according to claim 1, characterized in that The testing of the cloud environment model to be tested according to the misuse use case model includes: Obtaining a unified modeling language diagram according to the misuse use case model; Generate test code according to the unified modeling language diagram; The test code is used to test the cloud environment model to be tested.

6. The method according to claim 1 or 5, characterized in that: The method further comprises: When the misuse case fails the test, the cloud environment model to be tested is updated to obtain the updated cloud environment model.

7. A cloud environment security testing device, characterized in that: include: The first generation module is used to identify risks in the cloud environment model to be tested and generate a risk model; A first processing module is used to convert the risk model into a negative demand model according to negative demands; wherein the negative demands are functions or performance requirements that are not expected to appear in the cloud environment model to be tested; and the negative demands are derived according to the risks in the risk model; A second processing module is used to convert the negative demand model into a misuse use case model according to the misuse use case; wherein the misuse use case model is used to describe the attack activities of malicious users on the cloud environment model to be tested; and the misuse use case is generated based on the negative demand; The third processing module is used to test the cloud environment model to be tested according to the misuse use case model.

8. A network device comprising: A processor, a memory, and a program or instruction stored in the memory and executable on the processor; characterized in that when the processor executes the program or instruction, the method for cloud environment security testing as described in any one of claims 1-6 is implemented.

9. A readable storage medium having a program or instruction stored thereon, characterized in that: When the program or instruction is executed by the processor, the steps in the method for cloud environment security testing as described in any one of claims 1-6 are implemented.

10. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the steps of the method for cloud environment security testing as described in any one of claims 1 to 6.