Method, system and mimicry defense architecture for restoring mimicry system factory settings

Abstract

The application provides a method and system for restoring the factory settings of a mimicry system and a mimicry defense architecture. The method comprises a heterogeneous executor initialization step and a mimicry component initialization step. The heterogeneous executor initialization step: determines whether an input agent has captured a factory settings restoration instruction, if yes, isolates external user input traffic, generates an executor initialization instruction, and transmits the instruction to N online heterogeneous executors; after receiving the executor initialization instruction, the N online heterogeneous executors perform a factory settings restoration operation, and after the operation is completed, an executor initialization OK signal is generated and transmitted to a decider; the decider generates an online executor initialization completion signal and transmits the signal to a dispatcher. The application quickly and safely and reliably realizes the factory settings restoration operation of the mimicry system under the premise that the components and modules in the mimicry system do not change the original system network architecture.

Description

Technical Field

[0001] This invention relates to the field of mimicry defense technology, specifically to a method, system, and mimicry defense architecture for restoring a mimicry system to its factory settings. Background Technology

[0002] Mimicry defense technology has revolutionized cyberspace defense, providing a novel solution for network system security. To ensure the security of each module and component within a mimicry system, internal communication must be conducted via a single-line mechanism. While this method prevents attacks from spreading, it often makes subsequent maintenance of each component and module inconvenient.

[0003] Factory reset is a fundamental feature of commercial products. When a system malfunctions due to unexpected damage or misconfiguration, a factory reset is often necessary to quickly resolve the problem. Therefore, understanding how to quickly restore the factory settings of various modules and components of a mimicry system without altering its internal network communication architecture is crucial for improving the commercial viability of mimicry systems.

[0004] In order to solve the above problems, people have been seeking an ideal technological solution. Summary of the Invention

[0005] The purpose of this invention is to address the shortcomings of existing technologies by providing a method, system, and mimicry defense architecture for restoring a mimicry system to its factory settings.

[0006] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0007] The first aspect of the present invention provides a method for restoring a mimicry system to its factory settings, which includes a heterogeneous execution unit initialization step and a mimicry component initialization step;

[0008] Heterogeneous Executor Initialization Steps:

[0009] Determine whether the input agent has captured the factory reset command. If so, isolate external user input traffic, generate execution body initialization commands, and transmit them to N online heterogeneous execution bodies respectively.

[0010] Upon receiving the execution unit initialization command, N online heterogeneous execution units respectively perform factory reset operations. After completion, an execution unit initialization OK signal is generated and transmitted to the arbitrator.

[0011] Determine whether the adjudicator receives an executor initialization OK signal from N online heterogeneous executors within a preset time period T1. If so, generate an online executor initialization completion signal and transmit it to the scheduler; otherwise, notify the scheduler to take the heterogeneous executor with initialization error offline for cleaning.

[0012] Mimicry component initialization steps:

[0013] Upon receiving the online executor initialization completion signal, the scheduler generates a mimicry component initialization start notification and transmits it to the input agent;

[0014] In response to the received mimicry component initialization start notification, the input agent generates mimicry component initialization instructions and transmits them to N online heterogeneous executors respectively;

[0015] After confirming that the initialization command for the mimicry component was successfully sent, the input agent begins to perform a factory reset operation;

[0016] Upon receiving the initialization command of the mimicry component, the N online heterogeneous executors forward the command to the adjudicator.

[0017] The arbitrator determines whether it receives a mimic component initialization instruction from N online heterogeneous executors within a preset time period T2. If so, the arbitrator starts to perform a factory reset operation; otherwise, it generates a component initialization instruction to receive an abnormal signal and transmits it to the scheduler.

[0018] After confirming that the arbiter has completed the factory reset operation, the arbiter generates an arbiter initialization OK signal and transmits it to the scheduler;

[0019] In response to the received arbitrator initialization OK signal, the scheduler begins to perform a factory reset operation.

[0020] A second aspect of the present invention provides a system for restoring the factory settings of a mimicry system, comprising a factory initialization module I disposed on an input agent, a factory initialization module II disposed on a heterogeneous executor, a factory initialization module III disposed on a arbiter, and a factory initialization module IV disposed on a scheduler.

[0021] The factory initialization module I is used to determine whether the input agent has captured the factory reset command. If so, it isolates external user input traffic, generates an execution body initialization command, and transmits it to the factory initialization modules II of the N online heterogeneous execution bodies respectively. It is also used to respond to the received mimicry component initialization start notification, generate mimicry component initialization commands, and transmit them to the factory initialization modules II of the N online heterogeneous execution bodies respectively. It is also used to start executing the input agent factory reset operation after confirming that the mimicry component initialization command has been successfully sent.

[0022] The factory initialization module II is used to perform a factory reset operation after receiving the execution body initialization instruction, and after the operation is completed, generate an execution body initialization OK signal and transmit it to the factory initialization module III of the arbiter; it is also used to forward the mimicry component initialization instruction to the factory initialization module III of the arbiter after receiving the mimicry component initialization instruction.

[0023] The factory initialization module III is used to determine whether the arbiter receives an execution unit initialization OK signal from N online heterogeneous execution units within a preset time period T1. If so, it generates an online execution unit initialization completion signal and transmits it to the factory initialization module IV of the scheduler; otherwise, it notifies the scheduler to take the heterogeneous execution units with initialization errors offline for cleaning. It is also used to determine whether the arbiter receives a mimic component initialization instruction from N online heterogeneous execution units within a preset time period T2. If so, it starts executing the arbiter factory reset operation; otherwise, it generates a component initialization instruction reception error signal and transmits it to the factory initialization module IV of the scheduler. It is also used to generate an arbiter initialization OK signal and transmit it to the factory initialization module IV of the scheduler after confirming that the arbiter factory reset operation is completed.

[0024] The factory initialization module IV is used to generate a mimic component initialization start notification and transmit it to the factory initialization module I of the input agent after receiving the online execution body initialization completion signal; it is also used to start executing the scheduler factory reset operation in response to the received arbitrator initialization OK signal.

[0025] A third aspect of the present invention provides a mimicry defense architecture, including an input agent, heterogeneous executors, an adjudicator, and a scheduler. The input agent is communicatively connected to each of the heterogeneous executors, the heterogeneous executors are also communicatively connected to the adjudicator, the adjudicator is also communicatively connected to the scheduler, and the scheduler is also communicatively connected to an online heterogeneous executor, a backup executor pool, and the input agent.

[0026] The input agent is used to perform the factory reset function of the input agent in the above-described method for restoring the factory settings of the mimicry system;

[0027] The heterogeneous actuator is used to perform the factory reset function of the heterogeneous actuator in the above-described method for restoring the factory settings of the mimicry system;

[0028] The arbiter is used to perform the factory reset function of the arbiter in the above-described method for restoring the factory settings of the mimicry system;

[0029] The scheduler is used to perform the factory reset function of the scheduler in the above-described method for restoring the factory settings of the mimicry system.

[0030] This invention has outstanding substantive features and significant progress compared to the prior art, specifically:

[0031] This invention leverages the unidirectional nature of mimicry system communication and adopts the concept of "initialization commands being passed step by step and initialization operations being performed step by step." First, the executor is initialized, and then the mimicry components are initialized. By utilizing the functions of the input agent, scheduler, and arbitrator, the factory initialization work of all modules in the mimicry system is completed in an orderly manner. This allows each component and module in the mimicry system to quickly, safely, and reliably restore the mimicry system to factory settings without changing the original system network architecture. Attached Figure Description

[0032] Figure 1 This is a flowchart of the method for restoring the mimicry system to its factory settings according to the present invention;

[0033] Figure 2 This is a schematic diagram of the structure of the system for restoring the factory settings of the mimicry system of the present invention. Detailed Implementation

[0034] The technical solution of the present invention will be further described in detail below through specific embodiments.

[0035] Example 1

[0036] As attached Figure 1 As shown, a method for restoring a mimicry system to its factory settings includes a heterogeneous execution unit initialization step and a mimicry component initialization step;

[0037] Heterogeneous Executor Initialization Steps:

[0038] Determine whether the input agent has captured the factory reset command. If so, isolate external user input traffic, generate execution body initialization commands, and transmit them to N online heterogeneous execution bodies respectively.

[0039] Upon receiving the execution unit initialization command, N online heterogeneous execution units respectively perform factory reset operations. After completion, an execution unit initialization OK signal is generated and transmitted to the arbitrator.

[0040] Determine whether the adjudicator receives an executor initialization OK signal from N online heterogeneous executors within a preset time period T1. If so, generate an online executor initialization completion signal and transmit it to the scheduler; otherwise, notify the scheduler to take the heterogeneous executor with initialization error offline for cleaning.

[0041] Mimicry component initialization steps:

[0042] Upon receiving the online executor initialization completion signal, the scheduler generates a mimicry component initialization start notification and transmits it to the input agent;

[0043] In response to the received mimicry component initialization start notification, the input agent generates mimicry component initialization instructions and transmits them to N online heterogeneous executors respectively;

[0044] After confirming that the initialization command for the mimicry component was successfully sent, the input agent begins to perform a factory reset operation;

[0045] Upon receiving the initialization command of the mimicry component, the N online heterogeneous executors forward the command to the adjudicator.

[0046] The arbitrator determines whether it receives a mimic component initialization instruction from N online heterogeneous executors within a preset time period T2. If so, the arbitrator starts to perform a factory reset operation; otherwise, it generates a component initialization instruction to receive an abnormal signal and transmits it to the scheduler.

[0047] After confirming that the arbiter has completed the factory reset operation, the arbiter generates an arbiter initialization OK signal and transmits it to the scheduler;

[0048] In response to the received arbitrator initialization OK signal, the scheduler begins to perform a factory reset operation.

[0049] It is understandable that in the heterogeneous executor initialization step, the above operations are performed to restore the factory settings of all executors in the online executor pool; in the mimicry component initialization step, the above operations are performed to restore the factory settings of the input agent, arbitrator, and scheduler respectively; by leveraging the original communication network architecture within the mimicry system and the functions of the mimicry components themselves, the hierarchical transmission of initial instructions is achieved, and the initialization of mimicry components and modules is performed hierarchically, ensuring that the mimicry system can restore the factory settings without changing the original internal network architecture.

[0050] It should be noted that, theoretically, the initialization of the executor and mimicry components does not need to be in any particular order, and the factory reset order of the input agent, heterogeneous executor, arbitrator, and scheduler is not strictly limited. However, in engineering implementation, updating the program on the executor will not affect the normal operation of the entire mimicry system; from a security perspective, since the executor is directly exposed to attackers, attacks often occur on the executor. Therefore, this invention initializes the executor first, which helps to quickly cut off and eliminate attacks, while also preventing the spread of attacks; ensuring the security of the executor first, and then initializing the components, further ensures the security of the components.

[0051] It is understandable that when the executor performs a factory reset, the initialization process includes: at the hardware level, mainly resetting system memory data and chip registers, resetting the system through a hardware reset; at the operating system level, mainly restoring the initial file system and clearing historical usage traces; and at the application software level, mainly clearing application data and cache, and setting software settings.

[0052] When the input agent, arbitrator, and scheduler perform a factory reset, the initialization process includes: clearing cached data, restoring default configuration (mainly restoring the configuration file to its default state), and clearing user-configured data.

[0053] Furthermore, if the arbiter does not receive an executor initialization OK signal from N online heterogeneous executors within a preset time period T1, it notifies the scheduler to take the heterogeneous executor with initialization error offline and clean it into the backup heterogeneous executor pool.

[0054] It should be noted that after the scheduler receives the online execution entity initialization completion signal ("initialization OK" ruling) sent by the arbiter, the scheduler considers that the execution entities in the online execution entity pool have completed initialization, and then takes the execution entities in the online execution entity pool offline. At the same time, it schedules uninitialized execution entities from the backup execution entity pool into the online execution entity pool.

[0055] Specifically, the heterogeneous execution unit initialization step further includes the following steps:

[0056] After the scheduler receives the signal that the online execution entity has been initialized, it schedules the uninitialized heterogeneous execution entities from the backup heterogeneous execution entity pool to come online, and takes the initialized online heterogeneous execution entities offline and puts them into the backup heterogeneous execution entity pool.

[0057] After confirming that an uninitialized heterogeneous execution unit has been scheduled to come online, the scheduler generates a backup heterogeneous execution unit online notification and transmits it to the input agent;

[0058] In response to the received notification that the backup heterogeneous execution unit is online, the input agent generates backup execution unit initialization instructions and transmits them to N online backup heterogeneous execution units respectively;

[0059] Upon receiving the online backup heterogeneous executor, each of the N online backup heterogeneous executors performs a factory reset operation. After completion, a backup executor initialization OK signal is generated and transmitted to the arbiter.

[0060] Determine whether the arbiter receives a backup execution initialization OK signal from N online backup heterogeneous execution entities within a preset time period T1. If so, generate a backup execution initialization completion signal and transmit it to the scheduler.

[0061] Repeat the above steps to restore all execution entities in the online execution entity pool and the backup execution entity pool to factory settings, until all uninitialized heterogeneous execution entities in the backup heterogeneous execution entity pool are restored to factory settings.

[0062] Furthermore, the heterogeneous execution unit initialization step also includes the following steps:

[0063] Each time, N uninitialized heterogeneous executions are scheduled to come online for initialization from the backup heterogeneous execution pool. If the number of uninitialized heterogeneous executions is less than N, then all uninitialized heterogeneous executions are brought online.

[0064] Specifically, N = 2n + 1, where n is a natural number greater than or equal to 1. The preset time period T1 is 1 hour, 30 minutes, 10 minutes, or 5 minutes, which can be adjusted according to actual needs. The preset time period T2 is 1 hour, 30 minutes, 10 minutes, or 5 minutes, which can be adjusted according to actual needs.

[0065] Example 2

[0066] Based on Example 1, this example provides a specific implementation method for restoring the factory settings of a mimicry system, as shown in the attached figure. Figure 2 As shown;

[0067] The system for restoring the factory settings of the mimicry system includes a factory initialization module I set on the input agent, a factory initialization module II set on the heterogeneous executor, a factory initialization module III set on the arbiter, and a factory initialization module IV set on the scheduler.

[0068] The factory initialization module I is used to determine whether the input agent has captured the factory reset command. If so, it isolates external user input traffic, generates an execution body initialization command, and transmits it to the factory initialization modules II of the N online heterogeneous execution bodies respectively. It is also used to respond to the received mimicry component initialization start notification, generate mimicry component initialization commands, and transmit them to the factory initialization modules II of the N online heterogeneous execution bodies respectively. It is also used to start executing the input agent factory reset operation after confirming that the mimicry component initialization command has been successfully sent.

[0069] The factory initialization module II is used to perform a factory reset operation after receiving the execution body initialization instruction, and after the operation is completed, generate an execution body initialization OK signal and transmit it to the factory initialization module III of the arbiter; it is also used to forward the mimicry component initialization instruction to the factory initialization module III of the arbiter after receiving the mimicry component initialization instruction.

[0070] The factory initialization module III is used to determine whether the arbiter receives an execution unit initialization OK signal from N online heterogeneous execution units within a preset time period T1. If so, it generates an online execution unit initialization completion signal and transmits it to the factory initialization module IV of the scheduler; otherwise, it notifies the scheduler to take the heterogeneous execution units with initialization errors offline for cleaning. It is also used to determine whether the arbiter receives a mimic component initialization instruction from N online heterogeneous execution units within a preset time period T2. If so, it starts executing the arbiter factory reset operation; otherwise, it generates a component initialization instruction reception error signal and transmits it to the factory initialization module IV of the scheduler. It is also used to generate an arbiter initialization OK signal and transmit it to the factory initialization module IV of the scheduler after confirming that the arbiter factory reset operation is completed.

[0071] The factory initialization module IV is used to generate a mimic component initialization start notification and transmit it to the factory initialization module I of the input agent after receiving the online execution body initialization completion signal; it is also used to start executing the scheduler factory reset operation in response to the received arbitrator initialization OK signal.

[0072] It should be noted that the factory initialization module I is used to capture the factory reset command (or signal). When the factory reset command is obtained, the input agent first isolates the external user input traffic to prevent external traffic from affecting the internal factory initialization work of the mimicry system.

[0073] Once the online execution unit initialization is complete, a factory reset operation will be performed on all execution units in the backup execution unit pool.

[0074] The factory initialization module IV is further configured to: after receiving the online execution entity initialization completion signal, schedule uninitialized heterogeneous execution entities to come online from the backup heterogeneous execution entity pool, and take the initialized online heterogeneous execution entities offline and put them into the backup heterogeneous execution entity pool; it is also configured to generate a backup heterogeneous execution entity online notification after confirming that the uninitialized heterogeneous execution entity has been scheduled to come online, and transmit it to the factory initialization module I.

[0075] The factory initialization module I is further configured to: in response to the received notification of the backup heterogeneous execution unit going online, generate backup execution unit initialization instructions and transmit them to the N online backup heterogeneous execution units respectively;

[0076] The factory initialization module II is also used to perform factory reset operations upon receiving the online backup heterogeneous execution entities, and after the operations are completed, generate a backup execution entity initialization OK signal and transmit it to the factory initialization module III.

[0077] The factory initialization module III is further configured to: determine whether a backup execution unit initialization OK signal is received from N online backup heterogeneous execution units within a preset time period T1; if so, generate a backup execution unit initialization completion signal and transmit it to the factory initialization module IV.

[0078] Furthermore, the factory initialization module IV is also used for:

[0079] Each time, N uninitialized heterogeneous executions are scheduled to come online for initialization from the backup heterogeneous execution pool. If the number of uninitialized heterogeneous executions is less than N, then all uninitialized heterogeneous executions are brought online.

[0080] Example 3

[0081] Based on the above embodiments, this embodiment provides a specific implementation of a mimicry defense architecture, including an input agent, heterogeneous executors, an adjudicator, and a scheduler. The input agent is communicatively connected to the heterogeneous executors, the heterogeneous executors are also communicatively connected to the adjudicator, the adjudicator is also communicatively connected to the scheduler, and the scheduler is also communicatively connected to the online heterogeneous executors, the backup executor pool, and the input agent.

[0082] The input agent is used to perform the factory reset function of the input agent in the method for restoring the factory settings of the mimicry system in Embodiment 1;

[0083] The heterogeneous actuator is used to perform the factory reset function of the heterogeneous actuator in the method for restoring the factory settings of the mimicry system in Embodiment 1;

[0084] The arbitrator is used to perform the factory reset function of the arbitrator in the method for restoring the factory settings of the mimicry system in Embodiment 1;

[0085] The scheduler is used to execute the factory reset function of the scheduler in the method for restoring the factory settings of the mimicry system in Embodiment 1.

[0086] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them; although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications can still be made to the specific implementation of the present invention or equivalent substitutions can be made to some technical features without departing from the spirit of the technical solutions of the present invention, and all such modifications and substitutions should be covered within the scope of the technical solutions claimed in the present invention.

Claims

1. A method for restoring a mimicry system to factory settings, characterized in that: This includes the heterogeneous execution entity initialization step and the mimicry component initialization step; Heterogeneous Executor Initialization Steps: Determine whether the input agent has captured the factory reset command. If so, isolate external user input traffic, generate execution body initialization commands, and transmit them to N online heterogeneous execution bodies respectively. Upon receiving the execution unit initialization command, N online heterogeneous execution units respectively perform factory reset operations. After completion, an execution unit initialization OK signal is generated and transmitted to the arbitrator. Determine whether the adjudicator receives an executor initialization OK signal from N online heterogeneous executors within a preset time period T1. If so, generate an online executor initialization completion signal and transmit it to the scheduler; otherwise, notify the scheduler to take the heterogeneous executor with initialization error offline for cleaning. Mimicry component initialization steps: Upon receiving the online executor initialization completion signal, the scheduler generates a mimicry component initialization start notification and transmits it to the input agent; In response to the received mimicry component initialization start notification, the input agent generates mimicry component initialization instructions and transmits them to N online heterogeneous executors respectively; After confirming that the initialization command for the mimicry component was successfully sent, the input agent begins to perform a factory reset operation; Upon receiving the initialization command of the mimicry component, the N online heterogeneous executors forward the command to the adjudicator. Determine whether the arbiter receives a mimic component initialization command from N online heterogeneous executors within a preset time period T2. If so, the arbiter starts to perform a factory reset operation. Otherwise, the component initialization instruction receives an exception signal and transmits it to the scheduler; After confirming that the arbiter has completed the factory reset operation, the arbiter generates an arbiter initialization OK signal and transmits it to the scheduler; In response to the received arbitrator initialization OK signal, the scheduler begins to perform a factory reset operation; When the executor performs a factory reset, the initialization process includes: at the hardware level, resetting system memory data and chip registers, and resetting the system through a hardware reset; at the operating system level, restoring the initial file system and clearing historical usage traces; and at the application software level, clearing application data and cache, and setting software settings. When the input agent, arbitrator, and scheduler perform a factory reset, the initialization process includes: clearing cached data, restoring default configurations, and clearing user-configured data.

2. The method for restoring a mimicry system to factory settings according to claim 1, characterized in that, The heterogeneous execution unit initialization step further includes the following steps: After the scheduler receives the signal that the online execution entity has been initialized, it schedules the uninitialized heterogeneous execution entities from the backup heterogeneous execution entity pool to come online, and takes the initialized online heterogeneous execution entities offline and puts them into the backup heterogeneous execution entity pool. After confirming that an uninitialized heterogeneous execution unit has been scheduled to come online, the scheduler generates a backup heterogeneous execution unit online notification and transmits it to the input agent; In response to the received notification that the backup heterogeneous execution unit is online, the input agent generates backup execution unit initialization instructions and transmits them to N online backup heterogeneous execution units respectively; Upon receiving the online backup heterogeneous executor, each of the N online backup heterogeneous executors performs a factory reset operation. After completion, a backup executor initialization OK signal is generated and transmitted to the arbiter. Determine whether the arbiter receives a backup execution initialization OK signal from N online backup heterogeneous execution entities within a preset time period T1. If so, generate a backup execution initialization completion signal and transmit it to the scheduler. Repeat the process until all uninitialized heterogeneous executions in the backup heterogeneous execution pool are restored to factory settings.

3. The method for restoring a mimicry system to factory settings according to claim 2, characterized in that, The heterogeneous execution unit initialization step further includes the following steps: Each time, N uninitialized heterogeneous executions are scheduled to come online for initialization from the backup heterogeneous execution pool. If the number of uninitialized heterogeneous executions is less than N, then all uninitialized heterogeneous executions are brought online.

4. A system for restoring a mimicry system to its factory settings, characterized in that: It includes a factory initialization module I set on the input agent, a factory initialization module II set on the heterogeneous executor, a factory initialization module III set on the arbiter, and a factory initialization module IV set on the scheduler; The factory initialization module I is used to determine whether the input agent has captured the factory reset command. If so, it isolates external user input traffic, generates an execution body initialization command, and transmits it to the factory initialization modules II of the N online heterogeneous execution bodies respectively. It is also used to respond to the received mimicry component initialization start notification, generate mimicry component initialization commands, and transmit them to the factory initialization modules II of the N online heterogeneous execution bodies respectively. It is also used to start executing the input agent factory reset operation after confirming that the mimicry component initialization command has been successfully sent. The factory initialization module II is used to perform a factory reset operation after receiving the execution body initialization instruction, and after the operation is completed, generate an execution body initialization OK signal and transmit it to the factory initialization module III of the arbiter; it is also used to forward the mimicry component initialization instruction to the factory initialization module III of the arbiter after receiving the mimicry component initialization instruction. The factory initialization module III is used to determine whether the arbiter receives an execution unit initialization OK signal from N online heterogeneous execution units within a preset time period T1. If so, it generates an online execution unit initialization completion signal and transmits it to the factory initialization module IV of the scheduler; otherwise, it notifies the scheduler to take the heterogeneous execution units with initialization errors offline for cleaning. It is also used to determine whether the arbiter receives a mimic component initialization instruction from N online heterogeneous execution units within a preset time period T2. If so, it starts executing the arbiter's factory reset operation. Otherwise, the component initialization instruction receives an abnormal signal and transmits it to the factory initialization module IV of the scheduler; it is also used to generate an arbiter initialization OK signal and transmit it to the factory initialization module IV of the scheduler after confirming that the arbiter has completed the factory reset operation. The factory initialization module IV is used to generate a mimic component initialization start notification and transmit it to the factory initialization module I of the input agent after receiving the online execution body initialization completion signal; it is also used to start executing the scheduler factory restore operation in response to the received arbitrator initialization OK signal. When the executor performs a factory reset, the initialization process includes: at the hardware level, resetting system memory data and chip registers, and resetting the system through a hardware reset; at the operating system level, restoring the initial file system and clearing historical usage traces; and at the application software level, clearing application data and cache, and setting software settings. When the input agent, arbitrator, and scheduler perform a factory reset, the initialization process includes: clearing cached data, restoring default configurations, and clearing user-configured data.

5. The system for restoring the factory settings of a mimicry system according to claim 4, characterized in that, The factory initialization module IV is also used to: after receiving the online execution entity initialization completion signal, schedule uninitialized heterogeneous execution entities to come online from the backup heterogeneous execution entity pool, and take the initialized online heterogeneous execution entities offline and put them into the backup heterogeneous execution entity pool; It is also used to generate a backup heterogeneous execution unit online notification and transmit it to the factory initialization module I after confirming that an uninitialized heterogeneous execution unit has been scheduled to go online; The factory initialization module I is further configured to: in response to the received notification of the backup heterogeneous execution unit going online, generate backup execution unit initialization instructions and transmit them to the N online backup heterogeneous execution units respectively; The factory initialization module II is also used to perform factory reset operations upon receiving the online backup heterogeneous execution entities, and after the operations are completed, generate a backup execution entity initialization OK signal and transmit it to the factory initialization module III. The factory initialization module III is further configured to: determine whether a backup execution unit initialization OK signal is received from N online backup heterogeneous execution units within a preset time period T1; if so, generate a backup execution unit initialization completion signal and transmit it to the factory initialization module IV.

6. The system for restoring the factory settings of a mimicry system according to claim 5, characterized in that, The factory initialization module IV is also used for: Each time, N uninitialized heterogeneous executions are scheduled to come online for initialization from the backup heterogeneous execution pool. If the number of uninitialized heterogeneous executions is less than N, then all uninitialized heterogeneous executions are brought online.

7. A mimicry defense architecture, comprising an input agent, a heterogeneous executor, an adjudicator, and a scheduler, characterized in that: The input agent is communicatively connected to the heterogeneous executor, the heterogeneous executor is also communicatively connected to the arbiter, the arbiter is also communicatively connected to the scheduler, and the scheduler is also communicatively connected to the online heterogeneous executor, the backup executor pool, and the input agent. The input agent is used to perform the factory reset function of the input agent in the method for restoring the factory settings of the mimicry system according to any one of claims 1 to 3; The heterogeneous actuator is used to perform the factory reset function of the heterogeneous actuator in the method for restoring the factory settings of the mimicry system according to any one of claims 1 to 3; The arbitrator is used to perform the factory reset function of the arbitrator in the method for restoring the factory settings of the mimicry system according to any one of claims 1 to 3; The scheduler is used to execute the factory reset function of the scheduler in the method for restoring the factory settings of the mimicry system according to any one of claims 1 to 3.

Images