Operation method of target object, electronic equipment and storage medium

Abstract

The invention discloses an operation method of a target object, electronic equipment and a storage medium, and belongs to the technical field of network security, the method comprises the following steps: receiving an operation command, the operation command being used for instructing to perform a target operation on a target object corresponding to a target service node in a target cluster; in response to the operation command, determining a business level to which the target object belongs according to a corresponding relationship between a preset object and a preset level; and performing target operation on a target object corresponding to the target service node according to a predefined rule corresponding to the service level.

Description

Technical Field

[0001] This application belongs to the field of network security technology, and in particular, relates to an operation method for a target object, an electronic device, a storage medium, and a computer program product. Background Art

[0002] In the contemporary information technology environment, ensuring the security of network systems has become an important part of enterprises and organizations, and network security maintenance is an important means to ensure network security. Network security maintenance includes, but is not limited to, penetration testing, upgrading and strengthening, and obtaining the resource usage of each node in the network. As a security assessment technology that simulates the behavior of attackers, penetration testing evaluates the defense capabilities of network systems against various attacks by simulating the behavior of attackers. Testers will use various attack means to try to break through the security defenses of the network system. Through penetration testing, the vulnerabilities of the network system can be understood, and the security protection level of the network system can be improved.

[0003] In some scenarios, with the popularization of cloud computing, distributed systems, and microservices architectures, the complexity of the modern information technology environment has increased significantly. Especially the wide application of the distributed multi-node cluster autonomous deployment mode has made network topology and security protection extremely complex, which undoubtedly increases the difficulty of network security maintenance. Maintenance personnel need to have profound professional knowledge and practical experience and need to invest a large amount of time and human resources to effectively complete the task of network system security maintenance. Thus, the efficiency of network security maintenance is low and the human resource cost is high. Summary of the Invention

[0004] The purpose of the embodiments of this application is to provide an operation method for a target object, an electronic device, a storage medium, and a computer program product, which can solve the problems of low efficiency of network security maintenance and high human resource cost.

[0005] In a first aspect, an operation method for a target object is provided, which is executed by an electronic device. The method includes: receiving an operation command, where the operation command is used to indicate a target operation on a target object corresponding to a target service node in a target cluster; in response to the operation command, determining the service level to which the target object belongs according to the corresponding relationship between the preset object and the preset level; and performing a target operation on the target object corresponding to the target service node according to the predefined rule corresponding to the service level.

[0006] Second aspect, an operating device for a target object is provided, including: a receiving module, configured to receive an operation command for indicating to perform a target operation on a target object corresponding to a target service node in a target cluster; a determining module, configured to, in response to the operation command, determine a service level to which the target object belongs according to a preset correspondence between objects and preset levels; and an operating module, configured to perform the target operation on the target object corresponding to the target service node according to a predefined rule corresponding to the service level.

[0007] Third aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor, and computer-executable instructions stored on the memory and executable on the processor, where the computer-executable instructions, when executed by the processor, implement the steps of the method according to the first aspect.

[0008] Fourth aspect, an embodiment of the present application provides a computer-readable storage medium for storing computer-executable instructions, where the computer-executable instructions, when executed by a processor, implement the steps of the method according to the first aspect.

[0009] Fifth aspect, an embodiment of the present application provides a computer program product, where the computer program product includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions that, when executed by a computer, cause the computer to execute the steps of the method according to the first aspect.

[0010] In the embodiment of the present application, first, an operation command is received, and the operation command is used to indicate to perform a target operation on a target object corresponding to a target service node in a target cluster. Then, in response to the operation command, according to the preset correspondence between objects and preset levels, the service level to which the target object belongs is determined. Finally, the target operation is performed on the target object corresponding to the target service node according to the predefined rule corresponding to the service level. In this way, the technical solution provided by the embodiment of the present application shields the complexity of the network architecture of the distributed multi-node cluster autonomous deployment, and only needs to execute the actually required operation command at the corresponding service level, so as to operate on the target object on the service node in the cluster according to the rule corresponding to the service level, realizing automatic security maintenance of the network. There is no need for maintenance personnel to invest a large amount of manpower and material resources to learn and master the complex network architecture, improving the efficiency of network security maintenance and reducing the human resource cost. Description of the Drawings

[0011] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0012] Figure 1 It is a schematic structural diagram of the operating system of the target object provided by an exemplary embodiment of the present application.

[0013] Figure 2 It is a schematic diagram of the hierarchical relationship of the service layer provided by an exemplary embodiment of the present application.

[0014] Figure 3 It is a schematic structural diagram of the operating system of the target object provided by another exemplary embodiment of the present application.

[0015] Figure 4 It is a schematic flowchart of the operation method of the target object provided by an exemplary embodiment of the present application.

[0016] Figure 5 It is a schematic diagram of the application scenario for penetration testing of containers provided by an exemplary embodiment of the present application;

[0017] Figure 6 It is a schematic diagram of the application scenario for penetration testing of microservice applications provided by an exemplary embodiment of the present application;

[0018] Figure 7 It is a schematic diagram of the application scenario for penetration testing of the host system provided by an exemplary embodiment of the present application;

[0019] Figure 8 It is a schematic structural diagram of the operating device of the target object provided by an exemplary embodiment of the present application.

[0020] Figure 9 It is a schematic structural diagram of an electronic device provided by an exemplary embodiment of the present application. Detailed implementation manners

[0021] In order to enable those skilled in the art to better understand the technical solutions in the present application, the following will clearly and completely describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0022] The technical solutions provided by the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings, through some embodiments and their application scenarios.

[0023] First, please refer to Figure 1 , Figure 1 which is a schematic structural diagram of an operating system of a target object provided by an embodiment of the present application. The devices involved in the embodiments of the present application include an operator and a target host cluster environment. Among them, the operator is mainly used to send operation commands to the target host cluster environment. The operation commands may be execution commands for host nodes or containers in the target host cluster environment, or a set of execution commands included in a script. The operation commands or operation command sets issued by the operator need to be executed on the hosts or containers of all or part of the service nodes in the target host cluster environment.

[0024] Among them, the target host cluster is a host cluster in a distributed multi-node cluster autonomous deployment scenario, which includes a cluster control node, business containers, and cluster service nodes. The business function is a networking method implemented through the interaction of containerized microservice business components. Among them, the communication between cluster service nodes is carried out through the internal management network, and the containerized microservice business components provide corresponding functional services through the external business network. The communication between business containers is carried out through the internal business network. Among them, the internal management network, internal business network, and external business network can support being configured as multiple. Generally, to ensure communication security, the internal management network, internal business network, and external business network are network-isolated from each other and do not communicate directly. There are applications or microservices that provide services internally / externally in this target host cluster. The above application environment requirements, whether existing alone or simultaneously, can apply the operation method of the target object provided by the embodiments of the present application for test operations.

[0025] Next, please refer to Figure 2 , for the distributed multi-node cluster autonomous deployment scenario, the embodiments of the present application divide the target objects that need to be security-maintained into three business levels. It includes the multi-node host system layer, the Docker container layer, and the microservice application layer. The multi-node host system layer can perform penetration testing, upgrade and strengthening, or obtain the resource usage of multiple host nodes in the distributed multi-node cluster autonomous deployment. The Docker container layer can perform penetration testing, upgrade and strengthening, or obtain the resource usage of the main container for multiple containers on multiple host nodes in the distributed multi-node cluster autonomous deployment. The microservice application layer can provide service capabilities internally / externally. In addition to testing the security of its containerized deployment, it is also necessary to detect the deployment security of the microservice, such as performing penetration testing, upgrade and strengthening, or obtaining the resource usage of the main container for the microservice.

[0026] Among them, the penetration testing of the host node includes operating system vulnerability detection and application environment vulnerability detection, etc. The operating system vulnerability detection and application environment vulnerability detection include but are not limited to system password security, system privilege management, system log auditing, sudo privilege configuration, system account security, SSH access security, and sensitive information detection, etc. The upgrade and reinforcement of the host node is to upgrade and reinforce the mapping file of the host node. Obtaining the resource usage of the host node can be obtaining the memory resource usage of the host node, the Central Processing Unit (CPU) resource usage, etc.

[0027] Furthermore, the penetration testing of multiple containers on multiple host nodes includes but is not limited to high-risk capability detection, privileged mode detection, host mode detection, non-root operation, container security auditing, mounting sensitive directories, and read-only root file system, etc. The upgrade and reinforcement of the container is to upgrade and reinforce the container image file mapped from the host node to the host directory. Obtaining the resource usage of the container can be obtaining the memory resource and CPU resource used by the container in the host node for the target business node, etc.

[0028] Furthermore, the penetration testing of microservices includes but is not limited to PG database security, Oracle security, mysql security, Redis security, logstash security, Elasticsearch security, and logstash security, etc. The upgrade and reinforcement of microservices is to upgrade and reinforce the microservice application files mapped from the host node to the host directory. Obtaining the resource usage of microservices can be obtaining the memory resource and CPU resource used by the microservice application in the host node for the target business node, etc.

[0029] Furthermore, please refer to Figure 3 , Figure 3 , a multi-layer penetration testing framework (MLPTF) provided by an embodiment of the present application. An embodiment of the present application can use this multi-layer penetration testing framework to maintain the security of the network in a distributed multi-node cluster autonomous deployment scenario. As Figure 3As shown, the MLPTF in the embodiment of the present application is mainly divided into two parts: a control center and an execution unit. Among them, the control center can be deployed on the control nodes of a distributed multi-node cluster, and the execution unit is distributed to multiple service nodes. The control center mainly includes an initialization management module, an execution management module, and a log management module. The control center is the distribution point of operation commands or operation command sets. Through the control center, the hierarchical operation commands that actually need to be executed are sent to the processing modules of the corresponding execution units, ensuring that the operation commands and operation command sets can be executed at the correct service level and obtaining the expected execution results. At the same time, the control center can integrate and process the execution results after each execution unit has completed execution.

[0030] The execution unit is mainly divided into a host command processing module / script processing module, a container operation processing module, and a microservice operation processing module. Among them, the host command processing module / script processing module is mainly used for security detection at the host system layer of the node. The host command is equivalent to the operation command issued by the operation machine, and the host script is equivalent to the operation command set issued by the operation machine. The difference between the two is that the host command processing module is a separate processing module, while the host script processing module is embedded in the instruction set of the host script. The container operation processing module corresponds to various operation detections at the above-mentioned Docker container layer and is mainly used to ensure that the operation commands or operation command sets are executed on the target container. The microservice operation processing module corresponds to various operation detections at the above-mentioned microservice application layer and is mainly used to ensure that the operation commands or operation command sets are executed on specific microservice containers.

[0031] Furthermore, for the initialization management module in the control center, initialization management mainly completes the cleaning work of the result directory of the control center, the execution directories and result directories of each execution unit, avoiding the legacy data and programs caused by abnormal situations from affecting normal testing. Or after execution, clean up the test traces of the measured node cluster to avoid the retention of operation data and programs.

[0032] Further, for the execution management module in the control center, the execution management module mainly completes the unified processing of operation commands and operation scripts, ensures that the execution content necessary for the MLPTF framework is uploaded to the execution directory, and is responsible for sending execution instructions to the execution unit. First, it determines whether the operation content carried in the operation command sent by the operation machine is an operation instruction or an operation script. If it is an operation instruction, the operation instruction is written into the default script of the framework; thus ensuring that all files passed to the execution unit are files. Then, based on the obtained set of business node IPs of the target cluster, it determines whether the execution directory of the execution unit exists. If it does not exist, the execution directory of the execution unit is created; the framework files, default execution scripts, or operation machine-specified execution scripts that need to be executed on the execution unit are uploaded to the execution directories of each business node. Secondly, it determines whether the result directory of the execution unit of each business node exists. If it does not exist, the result directory of the execution unit is created. Among them, the result directory of the execution unit is generally used to store the execution results and execution record information of the execution unit.

[0033] Further, it determines whether the operation instruction needs to be escalated to root for execution. If so, a privilege escalation instruction is added to the execution instruction.

[0034] Further, an execution instruction is sent to the execution unit, and the execution instruction carries execution information such as an operation command or an operation script, and an operation execution type.

[0035] Further, for the log management module in the control center, the logs in the log management module include three parts. One part is the execution result of the execution unit, one part is the debug record information during the execution process of the execution unit, and another part is the special record information generated by the framework, such as an operation keyword indicating whether the target operation on the target object is completed. In addition, the log management module also needs to ensure that the process status on the execution unit is normal, so as to ensure the normal logs, and rely on the logs to obtain necessary judgment information normally. If the process status is abnormal, then exception handling is performed.

[0036] Further, the host command processing module in the execution unit writes the host command into the default script, then calls the default script to run, and stores the execution result in the result file, or the host command processing module directly executes the host command through the system and stores the execution result in the result file. If the operation command is a script, the script processing module directly calls the script to run and writes the output value during the script call into the result file.

[0037] Further, the container operation processing module in the execution unit mainly includes two execution logics. One is to perform a security check on the metadata of the container using the docker inspect command in the container command line, and the other is to enter the container for a security check using the docker exec command in the container command line. The security check on the metadata of the container includes methods such as high-risk capability detection, privileged mode detection, host mode detection, and running as non-root. Entering the container for a security check includes container timeout detection, container address randomization protection check, container file and folder permission check, sensitive information check, special file permission check, etc.

[0038] Further, the microservice operation processing module in the execution unit mainly includes two execution logics. One is to perform a security check on the metadata of the microservice, and the other is to perform a security check using the query command provided by the microservice itself. The security check on the metadata of the microservice includes detections such as log record type, log file access permission, debug log output configuration, etc. The check on the microservice itself includes detections such as data directory access permission, administrator account permission, host verification configuration, etc.

[0039] Next, in conjunction with Figure 4 a method for operating a target object provided in an embodiment of the present application will be described. Figure 4 FIG. shows a schematic flowchart of a method 400 for operating a target object provided in an embodiment of the present application. This method can be executed by an electronic device, such as a terminal device or a server device. In other words, the method can be executed by software or hardware installed on the terminal device or the server device. As Figure 4 shown, the method may include the following steps.

[0040] Step S401, receive an operation command.

[0041] Among them, the operation command is used to indicate a target operation on a target object corresponding to a target service node in a target cluster.

[0042] Specifically, the operation command is sent by the operation machine to the target cluster. The operation command can be an instruction or a set of instructions recorded in a script. The target cluster can be a distributed multi-node cluster, and the target service node can be a host node in the distributed multi-node cluster. The target object includes but is not limited to host nodes, containers, and microservice applications in the distributed multi-node cluster. The target operation includes but is not limited to penetration testing, upgrade and reinforcement, and obtaining resource information used by the target object, etc. The operation command includes but is not limited to penetration testing commands, upgrade and reinforcement commands, and acquisition commands for obtaining resource usage conditions, etc.

[0043] Step S402, in response to the operation command, determine the business level to which the target object belongs according to the corresponding relationship between the preset object and the preset level.

[0044] Specifically, the preset levels include, but are not limited to Figure 2 the host system layer, the container layer, and the microservice application layer shown. The corresponding relationship between the preset object and the preset level refers to the corresponding relationship between the container and the container layer, the corresponding relationship between the host node and the host system layer, and the corresponding relationship between the microservice application and the microservice application layer, etc.

[0045] As an optional embodiment of the present application, in response to an operation command, according to the corresponding relationship between the preset object and the preset level, determining the business level to which the target object belongs includes: when the target object is a container, according to the corresponding relationship between the preset container and the preset level, determining that the business level to which the container belongs is the container layer; or, when the target object is a host node, according to the corresponding relationship between the preset host node and the preset level, determining that the business level to which the host node belongs is the host system layer; or, when the target object is a microservice application, according to the corresponding relationship between the preset microservice application and the preset level, determining that the business level to which the microservice application belongs is the microservice application layer.

[0046] Step S403, perform a target operation on the target object corresponding to the target business node according to the predefined rule corresponding to the business level.

[0047] Specifically, for different business levels, different rules are used to perform target operations on the target object. If the business level is the host system layer and the operation command is a penetration test command, the predefined rule is to perform an operating system vulnerability test and an application environment vulnerability test on the target business node, etc. If the business level is the host system layer and the operation command is an upgrade and reinforcement command, the predefined rule is to upgrade and reinforce the host of the target business node. If the business level is the host system layer and the operation command is a resource acquisition command, the predefined rule is to obtain the resource usage of the host node of the target business node.

[0048] If the business level is the container layer and the operation command is a penetration test command, the predefined rule is to perform a penetration test on the container in the target business node. If the business level is the container layer and the operation command is an upgrade and reinforcement command, the predefined rule is to upgrade and reinforce the container of the target business node. If the business level is the container layer and the operation command is a resource acquisition command, the predefined rule is to obtain the resource usage of the container using the resources on the target business node.

[0049] If the service level is the microservice application layer and the operation command is a penetration test command, the predefined rule is to perform a penetration test on the microservice applications in the target service nodes. If the service level is the microservice application layer and the operation command is an upgrade and reinforcement command, the predefined rule is to perform an upgrade and reinforcement on the microservice applications in the target service nodes. If the service level is the microservice application layer and the operation command is a resource acquisition command, the predefined rule is to obtain the resource usage of the microservice applications on the target service nodes.

[0050] In the embodiment of the present application, first, an operation command is received, and this operation command is used to indicate to perform a target operation on a target object corresponding to a target service node in a target cluster. Then, in response to this operation command, according to the corresponding relationship between the preset object and the preset level, the service level to which the target object belongs is determined. Finally, the target operation is performed on the target object corresponding to the target service node according to the predefined rule corresponding to the service level. In this way, the technical solution provided by the embodiment of the present application shields the complexity of the network architecture of the distributed multi-node cluster autonomous deployment. It only needs to execute the actually required operation command at the corresponding service level, so as to operate on the target object on the service node in the cluster according to the rule corresponding to this service level, realizing the automated security maintenance of the network. There is no need for maintenance personnel to invest a large amount of manpower and material resources to learn and master the complex network architecture, improving the efficiency of network security maintenance and reducing the human resource cost.

[0051] As an optional embodiment of the present application, after receiving the operation command, the method further includes: initializing the execution directory and the result directory when the target object has corresponding execution directory and result directory; creating the execution directory and the result directory when the target object does not have corresponding execution directory and result directory; the execution directory is used to record the operation scripts or operation commands for performing the target operation on the target object, and the result directory is used to record the debugging information, operation results, and operation keywords during the execution process of performing the target operation on the target object according to the execution file, and the operation keywords indicate whether the target operation is completed.

[0052] Specifically, after the control center receives the operation instruction sent by the operation machine, an initialization operation is performed on the result directory and the execution directory of the target object in the control center to determine that there is no historical data remaining in the result directory and the execution directory, so as to avoid affecting the result of this operation. If the result directory and the execution directory do not exist, the result directory and the execution directory are created, and the user to which the control center belongs is given read and write permissions to avoid abnormal operation results due to permission issues. Further, the execution unit in the service node indicated by the operation instruction performs an initialization operation on the result directory and the execution directory in this service node. If the result directory and the execution directory do not exist in the service node indicated by the operation instruction, they are re-created.

[0053] Furthermore, the execution directory is used to record the operation script or operation command of the execution unit to perform the target operation on the target object. The recording process in the result directory is as follows: obtain the IP set of each business node in the target cluster, mark the acquisition result of each business node as the execution unit that has not been acquired, and issue an instruction to determine whether the log record contains the operation keyword of "operation completed". If the log record contains the operation keyword of "operation completed", the function of the execution unit has been completed, and it is necessary to issue an acquisition instruction of the operation result to the execution unit, and mark the acquisition result of the execution unit as acquired. The acquisition result identification is mainly used for the judgment and process control of subsequent processes. Determine whether the operation results of all execution units have been acquired. If so, integrate the operation results and record the integrated operation results in the result directory. When integrating, the IP of the business node to which it belongs can be added to the operation result of each operation command to identify different business nodes. And add the operation keyword of "all operations completed" to the result directory of the control center, as well as the debugging information of each execution node in the execution process of performing the target operation on the target object according to the execution file. At this point, all operations required by the operation instruction are completed, and the program calls the initialization management module of the control center to perform file cleanup on the result directory and execution directory of each execution unit.

[0054] Furthermore, if there are still execution units whose operation results have not been obtained, it is continued to determine whether the log record of the execution unit contains the operation keyword "operation completed" until the operation results of all execution units have been obtained. If the log record does not contain the operation keyword "operation completed of the execution unit", an instruction to obtain the execution process status is issued to the execution unit; the instruction here is related to the execution module of the execution unit, and the instruction to obtain the execution process status is combined and generated according to the operation execution type of the operation command. If the returned execution process status is normal, after waiting for a certain time interval, it is continued to determine whether the log record of the execution unit contains the operation keyword "operation completed". If the returned execution process status is abnormal, the log file and result file that the execution unit has been tested are obtained, and the acquisition result of the execution unit is marked as obtained. Adding a log record indicates that the node result acquisition of the execution unit is abnormal. The operation machine checks whether the log of the result directory of the control center contains the operation keyword "all operations completed" by polling. If it does, the operation result of the execution unit is obtained.

[0055] As an optional embodiment of the present application, the operation command includes a penetration test command, and the penetration test command is used to indicate to perform a penetration test on a target object corresponding to a target service node in a target cluster. Performing a target operation on the target object corresponding to the target service node according to a predefined rule corresponding to the service level includes: when the service level is the container layer, determining the test type indicated by the operation command; when the test type is metadata test, calling a first command in the container command line interface to perform a penetration test on the metadata of the container, and the first command is a command in the container command line tool for checking metadata; when the test type is entering the container for testing, calling a second command in the container command line interface to perform a penetration test inside the container, and the second command is a command in the container command line tool for executing a penetration test command in a running container.

[0056] Specifically, when the service level is the container layer, the target object is a container, and the operation command is a penetration operation command, the container operation processing module of the execution unit can use docker inspect in the container command line tool as the first command to perform a penetration test on the metadata of the container, or use docker exec in the container command line tool as the second command to enter the container for inspection. Among them, the container can be a docker container, and the container command line tool can be a docker container command line tool.

[0057] Exemplarily, the specific process of performing a penetration test on a container is as follows: As Figure 5As shown, the operating machine sends an operation command or a set of operation commands to the control center. The operation command or the set of operation commands is a penetration test command. According to the penetration test instructions of the container, the service node obtains the ID set of all containers in the service node where the execution unit is located. The initialization management of the control center clears the historical information in the result directory and the execution directory in the log management module, and clears the historical files in the execution directory and the result directory in the file system of each execution unit of the service node. Then, the execution management module of the control center starts to execute the following operations for each container in the ID set: First, obtain the container name according to the container ID and record it in the container name variable. Then, determine the penetration test type indicated by the operation command. If it is to perform a penetration test on the container's metadata, use docker inspect in the container command line tool as the first command to perform a penetration test on the container's metadata, and write the container ID, container name, and operation result into the result directory of the execution unit's file system; if it is to enter the container for inspection, use docker exec in the container command line tool to enter the container to execute the penetration test command, and write the container ID, container name, and operation result into the result directory of the execution unit's file system. After the execution unit completes the operations on all containers, write the operation keyword of "execution unit operation completed" into the log record of the control center, and the log management module of the control center records this log record into the result directory of the control center's file system.

[0058] Furthermore, the container metadata check includes methods such as high-risk capability detection, privileged mode detection, host mode detection, and running as non-root, etc. The detection inside the container includes container timeout detection, container address randomization protection check, container file and folder permission check, sensitive information check, special file permission check, etc.

[0059] As an optional embodiment of the present application, the operation command includes a penetration test command. The penetration test command is used to indicate a penetration test on the target object corresponding to the target service node in the target cluster. Performing target operations on the target object corresponding to the target service node according to the predefined rules corresponding to the business level includes: in the case where the business level is the microservice application layer, determining the test type indicated by the operation command; in the case where the test type is a test of microservice metadata, calling the third command in the cluster command line interface to enter the container to perform a penetration test on the microservice metadata. The third command is a command in the cluster command line tool for executing a penetration test command in a running container; in the case where the test type is a test of the microservice itself, calling the fourth command in the cluster command line interface to perform a penetration test on the microservice. The fourth command is a query command provided by the microservice itself.

[0060] Specifically, when performing penetration testing and scanning on the microservices application layer, since some built-in microservices applications provide service capabilities to the inside / outside, in addition to testing the security of their containerized deployment, it is also necessary to test the deployment security of the microservices application. Therefore, the microservices operation processing module of the execution unit mainly includes two execution logics. One is the security check of microservices metadata, and the other is the security check of the microservices themselves using the query commands provided by the microservices themselves. Among them, microservices metadata includes log record types, log file access permissions, debug log output configurations, etc.; the security check of the microservices themselves includes data directory access permissions, administrator account permissions, host verification configurations, etc. Among them, the container command-line tool can be the Kubernetes command-line tool.

[0061] Exemplarily, the specific process of performing penetration testing on a microservices application is as follows: As Figure 6 shown, the operator sends an operation command or a set of operation commands to the control center. The operation command or the set of operation commands is a penetration testing command. According to the penetration testing instructions of the container, the business node obtains the set of container IDs of all microservices related to the execution unit in the business node where it is located. The initialization management of the control center clears the historical information in the result directory and the execution directory in the log management module, and clears the historical files in the execution directory and the result directory in the file system of each execution unit of the business node. Then, the execution management module of the control center starts to perform the following operations on each microservice in the set of container IDs related to the microservices: First, obtain the container name according to the container ID related to the microservice and record it in the container name variable. Then, determine the penetration testing type indicated by the operation command. If it is a penetration test on microservices metadata, use the kubectl exec command in the cluster command-line tool as the third command to perform a penetration test on the microservices metadata, and write the container ID, container name, and operation result related to the microservice into the result directory of the file system of the execution unit; if it is a security check of the microservices themselves, use the kubectl exec command in the cluster command-line tool to enter the microservice and execute the penetration testing command through the query command of the microservice itself, and write the container ID, container name, and operation result related to the microservice into the result directory of the file system of the execution unit. After the execution unit has completed operations on all microservices, write the operation keyword of "execution unit operation completed" to the log record of the control center, and the log management module of the control center records this log record in the result directory of the file system of the control center.

[0062] As an optional embodiment of the present application, the operation command includes a penetration test command, and the penetration test command is used to instruct to perform a penetration test on the target object corresponding to the target business node in the target cluster. The target operation on the target object corresponding to the target business node according to the predefined rules corresponding to the business level includes: when the business level is the host system layer, determining the test type indicated by the operation command; when the test type is an operating system vulnerability test, performing a scanning penetration test on the operating system of the target business node; or, when the test type is an application environment vulnerability test, performing a scanning penetration test on the application environment of the target business node.

[0063] Specifically, if the business level is the host system level, penetration testing operations will be performed on multiple business nodes in the target cluster, including operating system vulnerability detection and application environment vulnerability detection, etc. Therefore, the execution management module of the control center starts the host command processing module and script processing module of each execution unit to perform penetration testing operations on multiple business nodes.

[0064] For example, Figure 7 As shown, the operation machine sends an operation command or an operation command set to the control center. The operation command or the operation command set is a penetration test command. The execution management module of the control center is responsible for starting the execution of the host command module and the script processing module of each execution unit. The operation result of the execution unit is placed in the result directory of the file system by the processing module of the execution unit. The operation result includes the penetration test result of the operating system of the target business node and the penetration test result of the application environment of the target business node. The log management module of the control center is responsible for monitoring the execution of the execution unit process, and obtaining the operation results of each execution unit for merging and processing. After the operation results of all execution units are obtained and the merging and processing are completed, the operation keyword "all operations are completed" and the debugging information of the execution node performing the target operation on the target object according to the execution file are added to the log of the control center, and stored in the result directory of the file system of the control center. At this point, the work required by the operation command is completed, and the program calls the initialization management module to clean up the files in the result directory and execution directory of each execution unit. After the cleaning is completed, the program exits.

[0065] As an alternative embodiment of the present application, the operation command includes an acquisition command, and the acquisition command is used to indicate acquiring resource information of a target object using a target service node. Performing a target operation on the target object corresponding to the target service node according to a predefined rule corresponding to the service level includes: in the case where the service level is the container layer, acquiring resource information of the container using the target service node in the target service node; in the case where the service level is the host system layer, acquiring resource information of the host node using the target service node in the target service node; in the case where the service level is the microservice application layer, acquiring resource information of the microservice application using the target service node in the target service node.

[0066] Specifically, the resource information includes memory resources and CPU resources, etc. The memory resources include but are not limited to the total memory, the proportion of used memory, the proportion of cache, and the proportion of free memory, etc. The CPU resources include but are not limited to the number of CPU cores used by the user, the number of CPU cores used by the system, and the number of free CPU cores, etc. In the embodiment of the present application, an acquisition command can be sent to the control center in the target cluster through an operation machine, and the control center then distributes the acquisition command to the execution units of each service node, and the execution units of each service node acquire the resource information. Among them, for the type of the target object indicated by the operation command, the resource information of the container using the target service node, the resource information of the host node using the target service node, and the resource information of the microservice application using the target service node can be acquired correspondingly. Through the hierarchical test framework provided by the embodiment of the present application, the resource information used by each target object can be quickly acquired, saving a large amount of manpower and material resources and improving the resource acquisition efficiency.

[0067] As an alternative embodiment of the present application, after performing a target operation on the target object corresponding to the target service node according to a predefined rule corresponding to the service level, the method further includes: displaying the resource information of the target object using the target service node through a dashboard.

[0068] Specifically, the acquired resource information of the target object using the target service node is all placed in a variable, combined into a JSON format description, and then reported to the specified dashboard through the curl instruction, and the resource information of the target object using the target service node is displayed through the dashboard. The user can intuitively see the resource information of the target object using the target service node, improving the user experience.

[0069] As an optional embodiment of the present application, the operation command includes an upgrade and reinforcement command, and the upgrade and reinforcement command is used to indicate to perform upgrade and reinforcement on a target object. Performing a target operation on a target object corresponding to a target service node according to a predefined rule corresponding to a service level includes: when the service level is the container layer, performing upgrade and reinforcement on the container image file mapped into the host directory in the target service node; when the service level is the host system layer, performing upgrade and reinforcement on the files of the host in the target service node; when the service level is the microservice application layer, performing upgrade and reinforcement on the microservice application files mapped into the host directory in the target service node.

[0070] Specifically, for the upgrade and reinforcement of a container, it is mainly to perform upgrade and reinforcement on the container image file. For the upgrade and reinforcement of a microservice application, the deployed microservice application is generally mapped to the container through the host directory. When performing upgrade and reinforcement on the microservice application, it is only necessary to upgrade and reinforce the microservice application files in the directory mapped by the corresponding host. In this way, when performing upgrade and reinforcement on the host, container, and microservice application, for the hierarchical test framework, it is all converted into an operation instruction set for the host to process. The entity reflected by the upgrade and reinforcement instruction set is a series of script files and file resources. The operator sends the upgrade and reinforcement instruction set to the control center of the target cluster through an operation machine, and then the control center sends the upgrade and reinforcement instruction set to the execution unit, finally realizing the upgrade and reinforcement operations of the host node, container, and microservice. This improves the efficiency of upgrade and reinforcement and saves a large amount of manpower and material resources.

[0071] As an optional embodiment of the present application, performing a target operation on a target object corresponding to a target service node according to a predefined rule corresponding to a service level includes: determining an operation execution type corresponding to the operation command; when the operation execution type is an instruction, executing the operation command through the target service node to perform a target operation on the target object according to a predefined rule corresponding to the service level; or, when the operation execution type is a script, invoking the system call script of the target service node to perform a target operation on the target object according to a predefined rule corresponding to the service level.

[0072] As an optional embodiment of the present application, when the operation execution type is an instruction, the method further includes: writing the operation command into a predefined script; invoking the predefined script through the target service node to perform a target operation on the target object according to a predefined rule corresponding to the service level.

[0073] Specifically, after receiving an operation command, it is determined whether the operation content carried in the operation command is an operation instruction or an operation script. If it is an operation instruction, the operation instruction is written into the default script of the hierarchical test framework, so as to ensure that the files passed to the execution unit are all script files, improving the operation efficiency. After the predetermined script written with the operation command is transferred to the execution directory of the service node, the target service node calls the predetermined script to perform a target operation on the target object according to the predefined rules corresponding to the service level.

[0074] Figure 8 FIG. shows a schematic structural diagram of an operation device for a target object provided by an embodiment of the present application. The device 800 includes: a receiving module 801, configured to receive an operation command for instructing a target operation on a target object corresponding to a target service node in a target cluster; a determining module 802, configured to, in response to the operation command, determine the service level to which the target object belongs according to a corresponding relationship between a preset object and a preset level; and an operation module 803, configured to perform a target operation on the target object corresponding to the target service node according to predefined rules corresponding to the service level.

[0075] In an embodiment of the present application, first, an operation command is received, and the operation command is used to instruct a target operation on a target object corresponding to a target service node in a target cluster. Then, in response to the operation command, according to the corresponding relationship between the preset object and the preset level, the service level to which the target object belongs is determined. Finally, a target operation is performed on the target object corresponding to the target service node according to the predefined rules corresponding to the service level. In this way, the technical solution provided by the embodiment of the present application shields the complexity of the network architecture of the distributed multi-node cluster autonomous deployment, and only needs to execute the actually required operation command at the corresponding service level, so as to operate on the target object on the service node in the cluster according to the rules corresponding to the service level, realizing automatic security maintenance of the network. There is no need for maintenance personnel to invest a large amount of manpower and material resources to learn and master the complex network architecture, improving the efficiency of network security maintenance and reducing the human resource cost.

[0076] Optionally, the determining module 802 is further configured to, when the target object is a container, determine that the service level to which the container belongs is the container layer according to the corresponding relationship between the preset container and the preset level; or, when the target object is a host node, determine that the service level to which the host node belongs is the host system layer according to the corresponding relationship between the preset host node and the preset level; or, when the target object is a microservice application, determine that the service level to which the microservice application belongs is the microservice application layer according to the corresponding relationship between the preset microservice application and the preset level.

[0077] Optionally, the operation module 803 is further configured to determine the test type indicated by the operation command when the service level is the container layer; when the test type is metadata test, call the first command in the container command line interface to perform penetration testing on the metadata of the container, where the first command is the command in the container command line tool for checking metadata; when the test type is in-container testing, call the second command in the container command line interface to perform penetration testing on the inside of the container, where the second command is the command in the container command line tool for executing a penetration testing command in a running container.

[0078] Optionally, the operation module 803 is further configured to determine the test type indicated by the operation command when the service level is the microservice application layer; when the test type is microservice metadata test, call the third command in the cluster command line interface to enter the container to perform penetration testing on the microservice metadata, where the third command is the command in the cluster command line tool for executing a penetration testing command in a running container; when the test type is testing the microservice itself, call the fourth command in the cluster command line interface to perform penetration testing on the microservice, where the fourth command is the query command provided by the microservice itself.

[0079] Optionally, the operation module 803 is further configured to determine the test type indicated by the operation command when the service level is the host system layer; when the test type is operating system vulnerability test, perform scanning and penetration testing on the operating system of the target service node; or, when the test type is application environment vulnerability test, perform scanning and penetration testing on the application environment of the target service node.

[0080] Optionally, the operation module 803 is further configured to obtain the resource information used by the container in the target service node for the target service node when the service level is the container layer; obtain the resource information used by the host node in the target service node for the target service node when the service level is the host system layer; obtain the resource information used by the microservice application in the target service node for the target service node when the service level is the microservice application layer.

[0081] Optionally, it further includes a display module for displaying the resource information used by the target object in the target service node through a dashboard.

[0082] Optionally, the operation module 803 is further configured to upgrade and strengthen the container image file mapped to the host directory in the target service node when the service level is the container layer; upgrade and strengthen the files of the host in the target service node when the service level is the host system layer; upgrade and strengthen the microservice application files mapped to the host directory in the target service node when the service level is the microservice application layer.

[0083] Optionally, the operation module 803 is further configured to initialize the execution directory and the result directory when there are corresponding execution directories and result directories for the target object; create the execution directory and the result directory when there are no corresponding execution directories and result directories for the target object; the execution directory is used to record the operation scripts or operation commands for performing the target operation on the target object, and the result directory is used to record the debugging information, operation results, and operation keywords during the execution of the target operation on the target object according to the execution file, and the operation keywords indicate whether the target operation is completed.

[0084] Optionally, the operation module 803 is further configured to determine the operation execution type corresponding to the operation command; when the operation execution type is an instruction, execute the operation command through the target service node to perform the target operation on the target object according to the predefined rules corresponding to the service level; or, when the operation execution type is a script, call the system call script of the target service node to perform the target operation on the target object according to the predefined rules corresponding to the service level.

[0085] Optionally, the operation module 803 is further configured to write the operation command into a predetermined script; call the predetermined script through the target service node to perform the target operation on the target object according to the predefined rules corresponding to the service level.

[0086] The apparatus 800 provided by the embodiments of the present application can execute the various methods described in the foregoing method embodiments, and implement the functions and beneficial effects of the various methods described in the foregoing method embodiments, which will not be elaborated herein.

[0087] Figure 9 The hardware structure diagram of the electronic device provided by the embodiments of the present application is shown. Referring to this figure, at the hardware level, the electronic device includes a processor, and optionally, an internal bus, a network interface, and a memory. Among them, the memory may include internal memory, such as high-speed random access memory (Random-Access Memory, RAM), and may also include non-volatile memory, such as at least one disk memory, etc. Of course, the electronic device may also include other hardware required for other services.

[0088] The processor, network interface, and memory can be interconnected through an internal bus, which can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience in representation, only a bidirectional arrow is used in this figure, but it does not mean that there is only one bus or one type of bus.

[0089] A memory for storing programs. Specifically, the program can include program code, and the program code includes computer operation commands. The memory can include a memory and a non-volatile memory, and provide instructions and data to the processor.

[0090] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a device for locating a specified user at the logical level. The processor executes the program stored in the memory and is specifically used to execute: Figure 4 The methods disclosed in the illustrated embodiments and implement the functions and beneficial effects of the various methods described in the foregoing method embodiments, which will not be elaborated herein.

[0091] The above as in this application Figure 4The method disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, the steps of the above method can be completed by the integrated logic circuit in the hardware of the processor or instructions in software form. The above-mentioned processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0092] The electronic device can also execute the various methods described in the foregoing method embodiments and achieve the functions and beneficial effects of the various methods described in the foregoing method embodiments, which will not be elaborated herein.

[0093] Of course, in addition to the software implementation, the electronic device of the present application does not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or a logic device.

[0094] The embodiments of the present application also propose a computer-readable storage medium. The computer-readable medium stores one or more programs. When the one or more programs are executed by an electronic device including a plurality of application programs, the electronic device is caused to execute Figure 4 the method disclosed in the illustrated embodiment and achieve the functions and beneficial effects of the various methods described in the foregoing method embodiments, which will not be elaborated herein.

[0095] Among them, the computer-readable storage medium includes a read-only memory (ROM), a random access memory (RAM), a magnetic disk, an optical disc, etc.

[0096] Furthermore, an embodiment of the present application also provides a computer program product. The computer program product includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions. When the program instructions are executed by a computer, the following process is implemented: Figure 1 - Figure 3 The method disclosed in the illustrated embodiment realizes the functions and beneficial effects of each method described in the foregoing method embodiments, which will not be elaborated herein.

[0097] In summary, the above are only the preferred embodiments of the present application and are not used to limit the protection scope of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

[0098] The systems, devices, modules or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0099] Computer-readable media includes both permanent and non-permanent, removable and non-removable media and can store information by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0100] It should also be noted that the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, such that a process, method, commodity or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the presence of additional identical elements in the process, method, commodity or device comprising the said element.

[0101] Each embodiment in this specification is described in a progressive manner. For the identical and similar parts among the embodiments, reference can be made to each other, and the key point of each embodiment is to illustrate the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the relevant parts, reference can be made to the partial description of the method embodiment.

Claims

1. A method for operating a target object, characterized in that, The operation method of the target object includes: Receiving an operation command for instructing to perform a target operation on a target object corresponding to a target service node in a target cluster; Responding to the operation command and determining the service level to which the target object belongs according to the corresponding relationship between the preset object and the preset level; Performing a target operation on the target object corresponding to the target service node according to the predefined rule corresponding to the service level.

2. The operation method of the target object according to claim 1, characterized in that, The step of responding to the operation command and determining the service level to which the target object belongs according to the corresponding relationship between the preset object and the preset level includes: When the target object is a container, determining that the service level to which the container belongs is the container layer according to the corresponding relationship between the preset container and the preset level; or When the target object is a host node, determining that the service level to which the host node belongs is the host system layer according to the corresponding relationship between the preset host node and the preset level; or When the target object is a microservice application, determining that the service level to which the microservice application belongs is the microservice application layer according to the corresponding relationship between the preset microservice application and the preset level.

3. The operating method of the target object according to claim 2, characterized in that, The operation command includes a penetration test command for instructing to perform a penetration test on a target object corresponding to a target service node in a target cluster. The step of performing a target operation on the target object corresponding to the target service node according to the predefined rule corresponding to the service level includes: When the service level is the container layer, determining the test type indicated by the operation command; When the test type is metadata test, invoking a first command in the container command line interface to perform a penetration test on the metadata of the container, where the first command is a command in the container command line tool for checking metadata; When the test type is in-container test, invoking a second command in the container command line interface to perform a penetration test inside the container, where the second command is a command in the container command line tool for executing a penetration test command in a running container.

4. The operating method of the target object according to claim 2, characterized in that, The operation command includes a penetration test command for instructing to perform a penetration test on a target object corresponding to a target service node in a target cluster. The step of performing a target operation on the target object corresponding to the target service node according to the predefined rule corresponding to the service level includes: When the service level is the microservice application layer, determining the test type indicated by the operation command; When the test type is microservice metadata test, invoking a third command in the cluster command line interface to enter the container to perform a penetration test on the microservice metadata, where the third command is a command in the cluster command line tool for executing a penetration test command in a running container; When the test type is to test the microservice itself, invoking a fourth command in the cluster command line interface to perform a penetration test on the microservice, where the fourth command is a query command provided by the microservice itself.

5. The operating method of the target object according to claim 2, characterized in that, The operation command includes a penetration test command, which is used to indicate to perform a penetration test on a target object corresponding to a target service node in a target cluster. The performing a target operation on the target object corresponding to the target service node according to a predefined rule corresponding to the service level includes: When the service level is the host system layer, determining the test type indicated by the operation command; When the test type is an operating system vulnerability test, performing a scanning penetration test on the operating system of the target service node; or, When the test type is an application environment vulnerability test, performing a scanning penetration test on the application environment of the target service node.

6. The operating method of the target object according to claim 2, wherein, The operation command includes a retrieval command, which is used to indicate to retrieve resource information used by the target object in the target service node. The performing a target operation on the target object corresponding to the target service node according to a predefined rule corresponding to the service level includes: When the service level is the container layer, retrieving resource information used by a container in the target service node in the target service node; When the service level is the host system layer, retrieving resource information used by a host node in the target service node in the target service node; When the service level is the microservice application layer, retrieving resource information used by a microservice application in the target service node in the target service node.

7. The operating method of the target object according to claim 6, characterized in that, After performing the target operation on the target object corresponding to the target service node according to the predefined rule corresponding to the service level, the method further includes: Displaying, through a dashboard, the resource information used by the target object in the target service node.

8. The operating method of the target object according to claim 2, characterized in that, The operation command includes an upgrade and reinforcement command, which is used to indicate to upgrade and reinforce a target object. The performing a target operation on the target object corresponding to the target service node according to a predefined rule corresponding to the service level includes: When the service level is the container layer, upgrading and reinforcing a container image file mapped to a host directory in the target service node; When the service level is the host system layer, upgrading and reinforcing files of a host in the target service node; When the service level is the microservice application layer, upgrading and reinforcing microservice application files mapped to a host directory in the target service node.

9. The operating method of the target object according to claim 1, characterized in that, After receiving the operation command, the method further includes: When an execution directory and a result directory corresponding to the target object exist, initializing the execution directory and the result directory; When an execution directory and a result directory corresponding to the target object do not exist, creating the execution directory and the result directory; The execution directory is used to record operation scripts or operation commands for performing a target operation on the target object, and the result directory is used to record debugging information, operation results, and operation keywords during the execution process of performing the target operation on the target object according to the execution file. The operation keywords indicate whether the target operation is completed.

10. The operation method of the target object according to claim 1, characterized in that, Performing a target operation on a target object corresponding to the target service node according to a predefined rule corresponding to the service level includes: Determining an operation execution type corresponding to the operation command; When the operation execution type is an instruction, executing the operation command through the target service node to perform a target operation on the target object according to the predefined rule corresponding to the service level; or, When the operation execution type is a script, invoking the script through the system of the target service node to perform a target operation on the target object according to the predefined rule corresponding to the service level.

11. The operating method of the target object according to claim 10, characterized in that, When the operation execution type is an instruction, the method further includes: Writing the operation command into a predefined script; Invoking the predefined script through the target service node to perform a target operation on the target object according to the predefined rule corresponding to the service level.

12. An electronic device, characterized in that, Comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implements the steps of the method for operating a target object as described in any one of claims 1-11.

13. A computer-readable medium, characterized in that, A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the method for operating a target object as described in any one of claims 1-11.

14. A computer program product, the computer program product comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions that, when executed by a computer, cause the computer to execute the steps of the method for operating a target object as described in any one of claims 1-11.

Images