An interactive penetration testing system based on documents

Abstract

This application provides a document-based interactive penetration testing system to implement an automated penetration testing mechanism that can significantly reduce packet loss. This allows for more convenient and efficient penetration testing, and has high application value. The document-based interactive penetration testing system provided in this application includes: a tool configuration module, used by advanced penetration engineers to configure the tools involved in automated penetration testing; a process configuration module, used by advanced penetration engineers to configure the processes involved in automated penetration testing; a document structure generation module, which processes the data generated by different penetration testing tools in the tool configuration module and different penetration testing processes in the process configuration module to obtain a document structure; a document parsing module, which converts the document structure into a data structure for execution; and a task execution module, used by junior penetration engineers to select and execute the data structure for automated penetration testing of the target.

Description

Technical Field

[0001] This application relates to the field of penetration testing, specifically to a document-based interactive penetration testing system. Background Technology

[0002] Penetration testing simulates the attack techniques and vulnerability discovery techniques that hackers might use to conduct in-depth exploration of the security of target systems, servers, or databases, discovering complex and interconnected security issues or deeper weaknesses, and generating reports on the intrusion process and details to the user.

[0003] Existing penetration testing is mainly divided into two categories: manual testing and automated testing. Manual testing relies on human experience and uses network security scanners and dedicated security testing tools to conduct non-destructive simulated attacks on operating systems, network devices, and application systems in the network. Automated testing uses penetration testing tools such as the Metasploit Framework (MSF) to automatically collect network target information, select matching attack components based on the target fingerprint to execute attacks on the target, and then output a penetration test report based on the test results.

[0004] In the process of researching existing related technologies, the inventors found that manual testing relies on the personal operational experience of penetration engineers, which not only results in unstable penetration testing effects but also has high operational costs. Automated testing, on the other hand, has poor automation effects, can only effectively test relatively fixed or limited targets, and may also be accompanied by a large number of invalid packets during test execution, which may lead to server blocking of IPs and affect the penetration testing effect. Obviously, both types of existing penetration testing solutions have the problem of inconvenience in application, resulting in low application value. Summary of the Invention

[0005] This application provides a document-based interactive penetration testing system to implement an automated penetration testing mechanism that can significantly reduce packet sending, thus enabling more convenient and efficient penetration testing and possessing high application value.

[0006] This application provides a document-based interactive penetration testing system, the system comprising: The tool configuration module allows highly skilled penetration engineers to configure the tools involved in automated penetration testing. The process configuration module allows highly skilled penetration engineers to configure the processes involved in automated penetration testing. The document structure generation module processes the data generated by the different penetration testing tools involved in the tool configuration module and the different penetration testing processes involved in the process configuration module to obtain the document structure. The document parsing module transforms the document structure into a data structure that can be used for execution. The task execution module allows junior penetration engineers to select and execute data structures to perform automated penetration testing on the target.

[0007] In the first possible implementation of this application, the document structure generation module extracts, analyzes, and summarizes the key content of the data generated by the tool and its related processes through the parsing script adapted for each penetration testing tool, and organizes it into a document structure.

[0008] In the second possible implementation of this application, the document structure specifically includes five aspects: target information collection, expanding the attack surface, single-point breakthrough, lateral movement within the internal network, and determining the target machine control authority.

[0009] In a third possible implementation of this application, the document parsing module also provides collaborative editing services for the document structure to different penetration engineers.

[0010] In conjunction with the third possible implementation of this application, in the fourth possible implementation of this application, the document parsing module also presents the content of the document structure through a visual interface.

[0011] In conjunction with the fourth possible implementation of this application, in the fifth possible implementation of this application, the visual interface is generated based on the selected document structure template.

[0012] In conjunction with the fourth possible implementation of this application, in the sixth possible implementation of this application, the collaborative editing service is specifically implemented through a unified visual interface.

[0013] In the seventh possible implementation of this application, the system also includes a document filling module, in which a junior penetration engineer fills the penetration test results into a specified location in the penetration test report document.

[0014] In conjunction with the seventh possible implementation of this application, in the eighth possible implementation of this application, the document filling module also provides collaborative editing services for penetration test reports to different penetration engineers in a filling manner.

[0015] In the ninth possible implementation of this application, the different penetration testing tools involved in the tool configuration module are specifically divided into online tools, GUI tools, and platform invocation tools.

[0016] From the above, it can be concluded that this application has the following beneficial effects: Document-based interactive penetration testing systems allow highly skilled penetration engineers to freely combine penetration testing tools and processes adapted to different penetration testing targets, and provide junior penetration engineers with access to the combined results. This materializes penetration experience for junior engineers, and enhances collaboration through specific document and data structures. The system balances the needs of both high-level human penetration testing and automated penetration testing, avoiding the limitations of existing automated penetration tools in terms of test targets. It also significantly reduces packet transmission and eliminates the problem of numerous invalid packets during test execution, preventing server IP blocking and impacting penetration testing effectiveness. This results in a penetration testing platform that integrates human and automated testing, enabling more convenient and efficient penetration testing with high application value. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a schematic diagram of a system architecture for the document-based interactive penetration testing system of this application; Figure 2 This is a schematic diagram illustrating a scenario where the platform calls the tool in this application; Figure 3 A schematic diagram of the interface configured for the tools of this application; Figure 4 This is a schematic diagram illustrating one of the usage processes of nmap for host discovery in this application; Figure 5 This is a schematic diagram illustrating a standard, comprehensive vulnerability scan coverage of a target in this application. Figure 6 This is a structural diagram of the document structure of this application; Figure 7 This is a schematic diagram of the interface of the document parsing module of this application; Figure 8 This is another schematic diagram of the document parsing module of this application; Figure 9 This is a schematic diagram of one of the chapters in the document structure of this application; Figure 10 This is a schematic diagram of an interface for performing automated penetration testing in this application. Figure 11This is another schematic diagram of an interface for performing automated penetration testing in this application; Figure 12 This is a schematic diagram of an interface in the penetration test report of this application; Figure 13 This is another schematic diagram of the interface of the penetration test report of this application; Figure 14 This is another schematic diagram of the interface of the penetration test report of this application; Figure 15 This is a schematic diagram of another system architecture for the document-based interactive penetration testing system of this application. Detailed Implementation

[0019] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that includes a series of steps or modules is not necessarily limited to those explicitly listed, but may include other steps or modules not explicitly listed or inherent to such processes, methods, products, or devices. The naming or numbering of steps appearing in this application does not imply that the steps in the method flow must be performed in the chronological / logical order indicated by the naming or numbering. The execution order of named or numbered process steps can be changed according to the desired technical purpose, as long as the same or similar technical effect is achieved.

[0021] The module division described in this application is a logical division. In practical applications, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the coupling or direct coupling or communication connection between modules shown or discussed may be through some interfaces, and the indirect coupling or communication connection between modules may be electrical or other similar forms, none of which are limited in this application. Furthermore, the modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed in multiple circuit modules. Some or all of the modules may be selected to achieve the purpose of the solution in this application according to actual needs.

[0022] First, before introducing the document-based interactive penetration testing system provided in this application, let's introduce the relevant background information involved in this application.

[0023] As mentioned earlier, existing penetration testing is mainly divided into two categories: manual testing and automated testing. Specifically: Manual testing, also known as manual service, has been the primary method used by penetration engineers to complete their tasks. They combine their professional knowledge with various independently operating and low-cooperation testing tools. From information gathering to project completion, penetration engineers have to repeat a lot of unnecessary work. At the same time, the penetration engineer's personal professional knowledge, practical skills, and the tools they use directly affect the penetration test results and efficiency.

[0024] Therefore, penetration engineers urgently need a simple, easy-to-use, and highly automated penetration testing system to help testers perform a large amount of repetitive work, allowing them more time to focus on learning the latest penetration testing theories and improving practical skills. Obviously, manual testing not only has unstable penetration testing results but also has high operating costs. In practical applications, it requires a large investment of human resources and places high demands on the professional skills of penetration engineers. The value of penetration test reports directly depends on the professional level of penetration engineers, and it cannot provide standardized penetration testing services. At the same time, this situation is accompanied by the long-standing problem of a shortage of penetration engineers.

[0025] Automated testing, also known as vulnerability exploitation frameworks, has limitations in its target audience. Various automated penetration testing systems often operate independently, making efficient collaboration difficult. Furthermore, each system typically performs well in only one or a few areas. Penetration engineers still need to subjectively select specific systems based on their professional knowledge, experience, and testing task requirements to ensure the penetration test is as comprehensive and efficient as possible. While various automated penetration testing systems are available for engineers to choose from, the most effective system varies depending on the specific testing task. Moreover, the system sets collected by ordinary penetration engineers are often incomplete, and their proficiency with relevant tools varies. Therefore, the results and efficiency of different testing tasks still depend on the penetration engineer's knowledge and proficiency in using the system sets.

[0026] Furthermore, commonly used penetration testing systems still have low levels of automation, and most systems have relatively fixed functions. For example, they may have built-in Nmap for port scanning, and if Nmap fails, the port scanning capability is lost, thus having significant limitations. At the same time, ordinary penetration testing systems have low levels of automation and incomplete function integration; while heavy-duty scanning tools like AWVS and IBM Appscan perform a large number of fuzzy FUZZ tests, resulting in a lack of targeting, which seriously affects testing efficiency and portability.

[0027] Clearly, existing automated testing methods are not very effective, and the objects that can be effectively tested are relatively fixed or limited. They may also be accompanied by a large number of invalid packets during test execution, which may lead to server blocking of IPs and affect the effectiveness of penetration testing.

[0028] The document-based interactive penetration testing system provided in this application will now be introduced.

[0029] See Figure 1 , Figure 1 This diagram illustrates a system architecture of the document-based interactive penetration testing system of this application. The document-based interactive penetration testing system provided in this application mainly includes a tool configuration module, a process configuration module, a document structure generation module, a document parsing module, and a task execution module (other modules are described in subsequent exemplary embodiments). Its specific working content can be found in the following: Tool Configuration Module It is understandable that the tool configuration module is set up so that highly skilled penetration engineers can configure the tools involved in automated penetration testing.

[0030] The tool configuration module targets the different basic testing tools that can be called in automated penetration testing. These small-scale basic testing tools need to be combined to achieve a complete set of penetration test content for a specific penetration target.

[0031] Among them, the high-level penetration engineer, also known as the first penetration engineer or first user, possesses a high level of penetration testing skills and can be understood as having high system privileges. They are used to provide junior penetration engineers with readily available, automated penetration testing solutions that can be invoked through this application, corresponding to the document structure generation module and its subsequent modules below. The junior penetration engineer, in contrast to the pre-defined high-level penetration engineer, can also be referred to as the second penetration engineer or second user.

[0032] In one specific implementation, the different penetration testing tools involved in the tool configuration module can be divided into three types: online tools, GUI tools, and platform invocation tools.

[0033] Online tools are mainly tools that offer functions on web pages; GUI (Graphical User Interface) tools are tools that can open a GUI page, that is, tools with a screen. If such tools cannot be executed from the command line, it is difficult to form a process. Platform invocation tools, also known as platform invocation class tools, are the focus of the test tools in this application. They can be used to form processes and are generally tools with different parameters that run in cmd.

[0034] For example, you can refer to Figure 2 The diagram illustrates a scenario where the platform invokes a tool according to this application. Such command-line tools can be invoked by the scheduling module after combining parameters to achieve different capabilities, such as... Figure 3 The diagram shown illustrates an interface configuration of the tool in this application, which demonstrates the configuration content of the Nmap tool. Each parameter can have a new configuration parameter added. The first column is the name, the second column is the actual parameters and inputs, the third column is an example, and the fourth column is the parsing script used to obtain key information from the nmap tool.

[0035] In practical applications, when configuring penetration testing tools, the tool configuration module can also select which basic data is valid, such as IP / URL / Domain / IP range / port, etc. For some tools, if the input is an IP, the tool can be configured to be valid for IP. The document parsing module can refer to this configuration later.

[0036] Process configuration module It is understandable that the process configuration module is set up so that highly skilled penetration engineers can configure the process configurations involved in automated penetration testing.

[0037] The process configuration module mainly enables the arrangement and combination of different penetration testing tools, including platform calling tools, based on experience. This allows penetration experience to be materialized into penetration paths and penetration actions to be standardized. This standardization capability also enables novice penetration testers to perform penetration tests.

[0038] like Figure 4 The diagram shown illustrates a usage flow of nmap for host discovery in this application. Figure 4 The process shown allows penetration engineers to comprehensively discover live hosts.

[0039] For example Figure 5 The diagram shown illustrates a standard, comprehensive vulnerability scanning coverage of a target using the present application. First, all subdomains of the target are discovered using the oneforall tool. Then, fingerprints are detected using Ehole. Finally, a Proof-of-Concept (PoC) test with fingerprint filtering is performed using nuclei.

[0040] Document structure generation module It is understandable that the document structure generation module is configured to process the data generated by the different penetration testing tools involved in the tool configuration module and the different penetration testing processes involved in the process configuration module to obtain the document structure.

[0041] The document structure generated by the document structure generation module can also be the core of the solution involved in this application. The document structure generated by the module enables the implementation of the document interactive feature of the penetration testing system of this application.

[0042] Specifically, the document structure generation module is based on the tool configuration module and the process configuration module mentioned above. It is a document structure obtained through fusion processing, thus materializing the experience of high-level penetration engineers in the form of document structure.

[0043] Therefore, before the document structure is generated here, the data generated by each tool / process involved in the previous two aspects needs to be processed in order to achieve the purpose of integration.

[0044] Among them, as a practical implementation method, the document structure generation module can extract, analyze and summarize the key content (important content) of the data generated by the tool and its related processes through the parsing script adapted for each penetration testing tool, and organize it into a document structure.

[0045] Through meticulous data processing including extraction, analysis, and summarization, a corresponding document structure is generated based on the obtained data and pre-defined document structure specifications. This document structure contains standard penetration testing content derived from the penetration testing experience of highly skilled penetration engineers.

[0046] In one instance, a complex process, including all penetration testing procedures such as information gathering, vulnerability exploitation, privilege escalation, and C2 control, can form a complex document structure. This document structure has five aspects: target information gathering, expanding the attack surface, single-point breakthrough, lateral movement within the internal network, and determining the target machine's control privileges.

[0047] refer to Figure 6 The schematic diagram of the document structure shown may specifically include the following sections and contents: Chapter 1, Target Information Gathering Get IP Get Domain Name Get website screenshots Obtain fingerprint information ... Chapter Two: Expanding the Attack Surface Subdomain detection C-segment IP scanning C-class IP port scanning Subdomain fingerprint discovery Subdomain vulnerability scanning ... Chapter Three, Targeted Utilization SQL injection exploit File upload utilization Known container vulnerabilities exploitation ... Chapter Four, Single-Point Breakthrough Launch CS Vipper launched ... Chapter 5, Internal Network Lateral Layout Internal network reachable segment detection Internal network fingerprint detection Internal network vulnerability scanning Internal network weak password scanning ... Chapter Six: Determining Target Control Authority Search Web System Target drone located ... It is important to note that after the document structure generation module creates the document structure, it does not execute any specific tasks within it. Instead, it merely forms the document structure. The method for producing this document structure is mainly based on the specific data generated in the process involving the combination of tools.

[0048] For example, in port scanning tools like nmap, a section titled "Port Scanning" can be created; OnForall can discover subdomains and create a section on subdomain discovery in expanding the attack surface; Nuclei can scan for known vulnerabilities and create a section on vulnerability scanning. Therefore, different tools can create different sections, ultimately forming a complete structured document, which is what we call the document structure here.

[0049] Once the document structure is generated, it will help penetration engineers to control the execution of tasks based on their experience, thereby completing the penetration test and realizing the interactive document feature of the penetration test system in this application. Through the guidance of high-level penetration testing, the total number of tasks is reduced, some unnecessary penetration tests are reduced, and the system can execute penetration test tasks more efficiently and uniformly based on the experience of penetration test engineers, sending fewer packets, only publishing useful packets, and selectively executing penetration paths.

[0050] Document parsing module It is understandable that the document parsing module is configured to transform the document structure into a data structure for use in execution.

[0051] The document structure generated by the previous document structure generation module is generally easy for manual editing and viewing, thus reducing the learning cost and allowing penetration testing novices to understand and complete the entire penetration testing task. However, the document structure itself is not a data structure that a machine can directly understand and execute, which is not conducive to the program understanding / obtaining important parameters. Therefore, a dedicated document parsing module can be used here to parse the document content and convert it into a data structure, which helps to call and execute it as a parameter in the program.

[0052] Specifically, you can define variables as follows: The structure "variable:numeric" represents the basic data parameters. The appearance of this structure in the document indicates variable assignment and configuration. For example, to set the target as "a certain penetration testing academy," you can configure it as `target: penetration testing academy`. Figure 7 The diagram shown illustrates one interface of the document parsing module of this application. It retrieves the target's URI, IP address, etc. This method can also be used for subsequent processes, such as... Figure 8 The diagram shown is another interface of the document parsing module of this application. According to this method, some basic data is generated. For each type of basic data, different penetration testing tools can be called. This is also selected and configured when configuring the penetration testing tools.

[0053] Continue to refer to Figure 9 The diagram shown illustrates an interface for one section of the document structure of this application. During the document structure generation process, tools can be selected and invoked from the template of that section, such as... Figure 9 It is the target, which can call tools such as getting domain name, getting IP, and getting screenshots of the main site. The target can also select the basic data content such as IP, domain name, and URL obtained. Of course, different basic data can call different plugins.

[0054] By selecting options based on the template, a document with a predefined structure can be generated. This generated document structure does not lead to direct task execution, but is presented visually for penetration engineers to view and select.

[0055] Furthermore, based on the interactive features and effects of the penetration testing system described above, the collaborative work effect can be further enhanced, specifically through collaborative editing.

[0056] As another specific implementation method, the document parsing module can also provide collaborative editing services for document structure to different penetration engineers (including high-level penetration engineers and junior penetration engineers).

[0057] As is easily understood, collaborative editing allows different penetration testing engineers to work together on the same document structure. When a skilled penetration engineer translates their penetration testing experience into a document structure, other collaborators can access it, complete their own penetration testing tasks, and aggregate the target's penetration testing process data into a single document. For example, in port scanning penetration testing, other collaborators complete the port scan, and the penetration engineer can directly view and use it without having to scan again. This collaborative editing capability enables collaboration among penetration testing engineers, thereby improving penetration testing efficiency, reducing manpower consumption, and significantly alleviating the shortage of human resources.

[0058] Specifically, as another practical implementation method, to facilitate collaborative editing by penetration engineers, the document parsing module can also present the document structure through a visual interface. This allows for a more intuitive presentation of the previously generated document structure, enabling penetration engineers to more accurately view the document structure and perform specific editing as needed.

[0059] In addition, combined Figure 9 The exemplary embodiment shown here can also be generated based on a selected document structure template. In other words, in actual operation, this application can also provide a range of document structures without substantial content (selectable document structure templates) to allow penetration engineers to generate document structures that are more in line with the actual situation.

[0060] Furthermore, to further enhance the collaborative effect, it can also be configured to perform interactive and collaborative editing in a unified interface. That is, the collaborative editing service involved in this embodiment can be implemented through a unified visual interface. In this way, both visualization function and convenient collaborative editing function can be realized in a highly integrated unified interface.

[0061] Task execution module It is understandable that the task execution module is set up so that junior penetration engineers can select and call execution data structures to perform automated penetration testing of the target.

[0062] After the document parsing module generates the data structure for execution, it can be called to perform specific automated penetration testing tasks.

[0063] It should be understood that, in the execution phase here, test engineers can also choose the specific content of the data structure (the cross-bracing of the previous document parsing module).

[0064] In one instance, see [reference] Figure 10 , Figure 11 The following are schematic diagrams of the interface for performing automated penetration testing in this application. The automated penetration testing task will only start executing after clicking the execute button (small triangle shown in the figure) in front of each task. The advantage of this is that it summarizes the execution of different penetration testing tools on one page, improving efficiency. In addition, not executing all tasks at the beginning can effectively reduce the number of packets sent and tasks.

[0065] Once the system has performed automated penetration testing as required, it can generate specific test results.

[0066] At this point, the test results can be output directly, such as in the form of a penetration test report, or further data processing can be performed.

[0067] As yet another example, see [link / reference] Figure 12 The diagram shown is an example of an interface for the penetration test report of this application. Penetration engineers can click to obtain domain names, IP addresses, or website screenshots, and can execute tasks and fill in the task results.

[0068] As yet another example, see [link / reference] Figure 13 The diagram shown is another interface illustration of the penetration test report of this application. For tasks that have not been executed, the corresponding content is empty.

[0069] In another specific implementation, the system may also include a document population module, in which junior penetration engineers populate the penetration test results into a specified location in the penetration test report document.

[0070] Clearly, this application introduces a manual operation step by the penetration engineer between the penetration test results obtained from the automated penetration test performed by the system and the final output penetration test report. This allows for convenient and selective filling of the results of various tools into designated locations, stringing them together into an easy-to-understand and readable penetration test report, which can then be submitted to the client to fix vulnerabilities and improve security. This operation further enhances the visualization of the penetration test report.

[0071] As yet another example, see [link / reference] Figure 14 The diagram shown is another interface illustration of the penetration test report of this application. Specifically, it uses a tool to obtain the C-segment. The execution result obtains the target C-segment, that is, it fills other IPs into the C_range list to obtain the side stations. Alternatively, it can fill the side station list into the corresponding positions.

[0072] Furthermore, the collaborative effect involved in this application can be further enhanced in the penetration test report stage. Specifically, in another exemplary implementation, the document filling module can also provide collaborative editing services for penetration test reports to different penetration engineers in a filling manner. It can be seen that the content of the final output penetration test report can also be processed collaboratively.

[0073] In this way, different penetration testing engineers can collaboratively access the same penetration testing report, fill in and supplement local data, improve collaboration efficiency, and when other penetration testing engineers see important vulnerabilities, they can directly perform actions such as vulnerability repair / vulnerability reporting.

[0074] To further facilitate understanding of the above content, you can also refer to... Figure 15 The diagram shown is another system architecture diagram of the document-based interactive penetration testing system of this application for understanding.

[0075] As can be seen from the above, a document-based interactive penetration testing system allows high-level penetration engineers to freely combine penetration testing tools and processes adapted to different penetration testing targets, and provides junior penetration engineers with a service to call the combined results. This materializes penetration experience for junior engineers. Furthermore, the specific document and data structures enhance collaboration. Therefore, the system balances the needs of high-level human penetration testing with those of automated penetration testing, avoiding the limitations of existing automated penetration tools in terms of testing targets. It also significantly reduces packet sending and avoids the problem of numerous invalid packets during test execution, preventing server IP blocking and impacting penetration testing results. Thus, it constructs a penetration testing platform that integrates human and automated testing, enabling more convenient and efficient penetration testing and possessing high application value.

[0076] The document-based interactive penetration testing system provided in this application has been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A document-based interactive penetration testing system, characterized in that, The system includes: The tool configuration module allows highly skilled penetration engineers to configure the tools involved in automated penetration testing. The process configuration module allows the highly skilled penetration engineer to configure the processes involved in the automated penetration testing. The document structure generation module processes the data generated by the different penetration testing tools involved in the tool configuration module and the different penetration testing processes involved in the process configuration module to obtain the document structure. The document parsing module converts the document structure into a data structure for execution. The task execution module allows junior penetration engineers to select and execute the data structure to perform automated penetration testing on the target. The document parsing module also provides collaborative editing services for the document structure to different penetration engineers; The document parsing module also presents the document structure through a visual interface; The visualization interface is generated based on the selected document structure template; The collaborative editing service is specifically implemented through a unified visual interface; The document structure generation module extracts, analyzes, and summarizes the key content of the data generated by the tool and its related processes through the parsing script adapted for each penetration testing tool, and organizes it into the document structure.

2. The document-based interactive penetration testing system according to claim 1, characterized in that, The document structure specifically includes five aspects: target information collection, expanding the attack surface, single-point breakthrough, lateral movement within the internal network, and determining target machine control permissions.

3. The document-based interactive penetration testing system according to claim 1, characterized in that, The system also includes a document population module, which allows the junior penetration engineer to populate the penetration test results into a specified location in the penetration test report document.

4. The document-based interactive penetration testing system according to claim 3, characterized in that, The document filling module also provides collaborative editing services for the penetration test report to different penetration engineers in a filling manner.

5. The document-based interactive penetration testing system according to claim 1, characterized in that, The tool configuration module involves different penetration testing tools, specifically online tools, GUI tools, and platform calling tools.

Images