A method, apparatus, device and storage medium for adjusting a sending rate

Abstract

The application discloses a mail sending rate adjusting method and device, equipment and storage medium, relates to the network security technical field, and includes the following steps: calling a preset Open API interface to create a mail sending task for each phishing email; determining whether the current time has reached the scheduled sending time; if yes, the mail sending task is sent to the master management service through the Open API interface, and the mail sending task is distributed to multiple agent nodes according to the distribution strategy of the mail sending task; the task execution mode of the mail sending task is obtained through the agent node, and the phishing email is sent to the target practice object according to the task execution mode; the mail sending rate is detected through the master management service, and it is determined whether the mail sending rate is greater than the preset rate threshold; if not, a new agent node is created to send the phishing email to be sent. The application can realize dynamic mail sending efficiency adjustment and achieve good phishing email practice effect.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of network security, and particularly relates to a sending rate adjusting method and device, equipment and a storage medium. BACKGROUND

[0002] Phishing email drills are exercises that simulate phishing attacks, which can improve users' ability to identify phishing emails and network security awareness. By sending disguised emails, users can simulate the common tactics used by network attackers, such as disguising as trusted people or official institutions, to lure users to click malicious links or download malicious files, thereby stealing user credentials and data information and other sensitive information. This drill is usually organized by an information technology center or security team, through simulating high-fidelity and immersive real scenes, to let users experience the deceptive and hidden nature of phishing emails, thereby improving users' vigilance and anti-fraud ability. During the drill, if the user is affected, he / she will usually enter a prompt page and automatically jump to a security training learning module after a period of time, to open the anti-phishing security learning. In this way, users can learn how to identify and prevent phishing emails, thereby enhancing their awareness of the security of personal information and data.

[0003] Currently, when conducting phishing email drills, a phishing email drill system is usually used for drilling, and when facing enterprise, college and other unit customers, the drill system is developed into a SaaS (Software as a Service) platform, and when conducting phishing email drills through the platform, if too many customers participate in the drill at the same time, such as the number of phishing emails sent by each unit customer reaching 1000 or even 10000 or more, the sending efficiency needs to be adjusted. Since too slow sending will affect user experience and drill effect, and too fast sending will be judged as spam or even returned by the recipient's anti-spam strategy, therefore, the adjustment of sending rate is crucial.

[0004] Currently, when sending a phishing email, a method of sending time reservation + limiting the number of sending in a unit time is generally adopted, for example, 30 emails are sent in 1 minute, that is, a new email is sent every 2 seconds, and the sending time of each email is 01:00:00, 01:00:02, 01:00:04, …, 01:01:00. The above method is to reasonably control the sending rate from the perspective of a unit customer, and is more suitable for a phishing email simulation system deployed privately, and is not suitable for a SaaS multi-tenant (unit customer) scenario. For example, when multiple customers perform simulation tasks at the same time, there are multiple emails to be sent in the database and the sending time is the same, for example, there are 10 emails to be sent at 01:00:30, and the sending of the email itself needs to connect, log in to the sending party mailbox service, and transfer the email data (including the email header, the content of the body and even the attachment) and a series of operations. The process is greatly affected by the network, and usually a second-level operation, which may cause parallel task accumulation, so that the subsequent task is constantly delayed, and the target object of the simulation / the recipient may increase the vigilance of identifying the authenticity of the email, thereby affecting the simulation effect. SUMMARY

[0005] Therefore, the purpose of the present application is to provide a sending rate adjusting method, device, equipment and storage medium, which can realize dynamic sending efficiency adjustment and achieve good phishing email simulation effect. The specific scheme is as follows:

[0006] In a first aspect, the present application discloses a sending rate adjusting method, comprising:

[0007] A preset Open API interface is called through a target business system to create a sending task for each phishing email, and it is judged whether the scheduled sending time has been reached or not;

[0008] If the scheduled sending time has been reached, the Open API interface is used to send each sending task to a pre-created master management service to determine a distribution strategy of the sending task, and the sending task is distributed to a plurality of agent nodes in a preset node group according to the distribution strategy;

[0009] The agent nodes in the preset node group analyze the received sending task to obtain a task execution mode of the sending task, and send the phishing email to a target simulation object according to the task execution mode;

[0010] Detecting a sending rate of the phishing email in a current sending task execution process by the master management service, and judging whether the sending rate is greater than a preset rate threshold; if not, creating a new agent node in the preset node group, and sending the phishing email to be sent by using the new agent node.

[0011] Optionally, the preset Open API interface is called by the target business system to create a sending task for each phishing email, which includes:

[0012] The preset Open API interface is called by the phishing engine to create a sending task for each phishing email; the sending task contains the phishing email, a task ID, a task type, and a task execution mode.

[0013] Optionally, the sending task is distributed to a plurality of agent nodes in a preset node group according to the distribution strategy, which includes:

[0014] Judging whether the distribution strategy is a directional distribution strategy;

[0015] If the distribution strategy is a non-directional distribution strategy, an agent node in an idle state is determined from the preset node group, and the sending task is distributed to the agent node in the idle state.

[0016] Optionally, the sending task is distributed to a plurality of agent nodes in a preset node group according to the distribution strategy, which includes:

[0017] Judging whether the distribution strategy is a directional distribution strategy;

[0018] If the distribution strategy is a directional distribution strategy, the sending task is distributed to a plurality of agent nodes in a specific node group.

[0019] Optionally, the sending task is distributed to a plurality of agent nodes in a preset node group according to the distribution strategy, which includes:

[0020] Judging whether the distribution strategy is a directional distribution strategy;

[0021] If the distribution strategy is a non-directional distribution strategy, an agent state table is queried by the master management service to obtain all online agent nodes in the preset node group, an agent list is obtained, a consistent hash algorithm is used to calculate the agent list, and a consistent hash ring is obtained.

[0022] calculating a hash value based on a task ID of the sending task, and determining a corresponding target agent node from the consistent hash ring based on the hash value;

[0023] detecting whether the target agent node is in an idle state;

[0024] if the target agent node is in the idle state, issuing the corresponding sending task to the target agent node.

[0025] Optionally, the agent nodes in the preset node group analyze the received sending tasks to obtain task execution modes of the sending tasks, and send phishing emails to target practice objects according to the task execution modes, including:

[0026] The agent nodes in the preset node group analyze the respective received sending tasks to obtain task types and task execution modes of the sending tasks, and determine whether the task types are phishing email practice types;

[0027] If the task types are phishing email practice types, obtain a plug-in path corresponding to the phishing email practice types, and obtain a phishing email practice plug-in from a configuration file of the corresponding agent node according to the plug-in path, and call the phishing email practice plug-in to send the phishing emails to target practice objects according to the task execution modes.

[0028] Optionally, the sending rate adjusting method further includes:

[0029] If the sending rate is greater than the preset rate threshold, the number of agent nodes in the preset node group is reduced to scale down the preset node group.

[0030] In a second aspect, the application discloses a sending rate adjusting device, including:

[0031] An interface calling module is configured to call a preset Open API interface through a target business system to create a sending task for each phishing email.

[0032] A first judgment module is configured to determine whether a scheduled sending time has been reached.

[0033] A task issuing module is configured to issue each sending task to a pre-created master control management service through the Open API interface if the scheduled sending time has been reached, to determine a distribution strategy of the sending task, and distribute the sending task to multiple agent nodes in a preset node group according to the distribution strategy.

[0034] The analysis module is configured to analyze the received mail sending task by an agent node in the preset node group to obtain a task execution mode of the mail sending task.

[0035] The mail sending module is configured to send the phishing mail to a target rehearsal object according to the task execution mode.

[0036] The sending rate detection module is configured to detect a sending rate of the phishing mail in the current mail sending task execution process by the master control management service.

[0037] The second judgment module is configured to judge whether the sending rate is greater than a preset rate threshold.

[0038] The sending rate adjustment module is configured to create a new agent node in the preset node group and send the phishing mail to be sent by using the new agent node if the sending rate is not greater than the preset rate threshold.

[0039] In a third aspect, the present application discloses an electronic device, comprising a processor and a memory; wherein the processor implements the mail sending rate adjustment method when executing the computer program saved in the memory.

[0040] In a fourth aspect, the present application discloses a computer readable storage medium for storing a computer program; wherein the computer program is executed by a processor to implement the mail sending rate adjustment method.

[0041] It can be seen that the application first calls a preset Open API interface through a target business system to create a sending task for each phishing email, and determines whether the scheduled sending time has been reached. If the scheduled sending time has been reached, the Open API interface is used to send each sending task to a pre-created master management service to determine a distribution strategy of the sending task, and the sending task is distributed to multiple agent nodes in a preset node group according to the distribution strategy. Then, the agent nodes in the preset node group are used to analyze the received sending task to obtain a task execution mode of the sending task, and the phishing email is sent to a target practice object according to the task execution mode. Then, the master management service is used to detect a sending rate of the phishing email in the current sending task execution process, and determine whether the sending rate is greater than a preset rate threshold. If the sending rate is not greater than the preset rate threshold, a new agent node is created in the preset node group, and the new agent node is used to send the phishing email to be sent. The application creates a sending task for each phishing email by calling a preset Open API interface, and sends the sending task to a pre-created master management service to distribute the task to multiple agent nodes in a node group according to a distribution strategy of the sending task, and perform phishing email practice through multiple agent nodes. In the practice process, it is determined whether the current sending rate is greater than a preset rate threshold. If yes, a new agent node is created to realize expansion of the node group, that is, dynamic sending efficiency adjustment. With the increase of agent nodes, the sending efficiency can be improved, the email can be sent in time, the user (that is, the target practice object) can receive the email without delay, and a good phishing email practice effect is achieved. The application is suitable for SaaS phishing email practice scenarios. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are only embodiments of the application, and those skilled in the art can obtain other drawings according to the provided drawings without creative labor.

[0043] Figure 1 A sending rate adjustment method flowchart disclosed by the application;

[0044] Figure 2 A specific sending rate adjustment method flowchart disclosed by the application;

[0045] Figure 3 A specific sending rate adjustment method flowchart disclosed by the application;

[0046] Figure 4 A structure diagram of a sending rate adjustment device disclosed in the present application;

[0047] Figure 5 A structure diagram of an electronic device disclosed in the present application. DETAILED DESCRIPTION

[0048] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0049] The embodiments of the present application disclose a sending rate adjustment method, referring to Figure 1 The method comprises the following steps.

[0050] Step S11: calling a preset Open API interface through a target business system to create a sending task for each phishing email, and judging whether the scheduled sending time has arrived.

[0051] It should be pointed out that the sending rate adjustment scheme proposed in the present application is applicable to a SaaS multi-tenant (i.e. multi-target simulation object) phishing email simulation scenario.

[0052] In the present embodiment, first, a preset Open API interface (i.e. Open Application Programming Interface, open application programming interface) is called through a target business system, so as to create a sending task for each phishing email through the Open API interface, and then it is judged whether the scheduled sending time has arrived. The target business system is a system or software for detecting and preventing phishing attacks. The Open API interface provides a business API interface to the outside world, which is convenient for third-party calling, and establishes a long link with the master management service on the inside, and forwards tasks to the master management service for scheduling and distribution.

[0053] In a specific embodiment, the calling of the preset Open API interface through the target business system to create a sending task for each phishing email can specifically include: calling the preset Open API interface through a phishing engine to create a sending task for each phishing email. The sending task contains the phishing email, a task ID, a task type and a task execution mode. In the present embodiment, referring to Figure 2As shown, a preset OpenAPI interface can be invoked by the phishing engine to create a sending task for each phishing email, which contains the phishing email, an identity document, a task type, a task execution mode, task parameters params (json), a task status, and the like. The task type contained in the sending task specifically refers to a phishing email drill type, and the task execution mode includes but is not limited to an immediate start execution mode, a certain time period execution mode (i.e., a mode of limiting a start time and an end time), and the like.

[0054] Step S12: If the current time has reached the scheduled sending time, each sending task is sent to a pre-created manager service through the Open API interface to determine a distribution strategy of the sending task and distribute the sending task to a plurality of agent nodes in a preset node group according to the distribution strategy.

[0055] In the embodiment, if the current time reaches the scheduled sending time, each sending task is sent to a pre-created manager service (manager service) through the Open API interface, so as to determine a distribution strategy of each sending task through the manager service, and then distribute the corresponding sending task to a plurality of agent nodes in a preset node group according to the distribution strategy. The number of agent nodes in the preset node group can be selected according to actual application requirements, and the distribution strategy includes but is not limited to a polling strategy, a random strategy, a hash load strategy, a directional strategy, and the like. For example, referring to Figure 2 As shown, the manager service distributes the sending task to four nodes of agent A, agent B, agent C, and agent D. It should be noted that the agent node has a task queue to be executed locally, and after receiving the task, the task is first stored in the queue, and then the corresponding sending task is taken out from the queue when it needs to be executed. In addition, after executing the sending task, the agent node can report the execution result to the manager service through WebSocket (a protocol for full-duplex communication on a single TCP connection).

[0056] Specifically, the manager service provides a task issuing and query entry, and supports registration and authentication of multiple agent nodes in a preset node group and long link connection management. Meanwhile, in order to improve the access performance and stability of the agent nodes, the manager service also supports horizontal expansion and contraction functions, and can expand or contract the number of agent nodes in the preset node group, so as to realize dynamic adjustment of the sending rate. In addition, for the SaaS multi-tenant (i.e. multiple target simulation objects) phishing email simulation scene, multiple manager services can be created, and each manager service corresponds to a node group containing multiple agent nodes. Different manager services can communicate through RPC (Remote Procedure Call), and realize the forwarding of task issuing and task result reporting messages.

[0057] Specifically, the distribution of the sending tasks to the multiple agent nodes in the preset node group according to the distribution strategy can include: determining whether the distribution strategy is a directional distribution strategy; if the distribution strategy is a non-directional distribution strategy, determining the agent nodes in an idle state from the preset node group, and distributing the sending tasks to the agent nodes in the idle state. That is, after determining the distribution strategy of the sending tasks, it is determined whether the current distribution strategy is a directional distribution strategy. If it is a non-directional distribution strategy, the agent nodes in the idle state are selected from the preset node group, and then the sending tasks are distributed to the agent nodes in the idle state. It can be understood that when the subsequent phishing email simulation is performed by the agent nodes, the agent nodes need to be in the idle state, i.e. in the non-working state, so that the phishing email sending operation can be performed in time, and the delay caused by task accumulation of a single agent node can be avoided.

[0058] Specifically, the manager service can obtain idle node information by querying all agent state tables corresponding to the agent nodes, and selecting a corresponding number of agent node information in the idle state from the agent state table by polling or randomly, and then selecting the corresponding agent nodes from the preset node group based on the idle node information. In addition, the manager service can set the node state of the agent node corresponding to the sending task to executing during the process of issuing the task, and when the agent node completes the sending task (i.e. completes the phishing email sending), the node state of the corresponding agent node can be restored to the idle state.

[0059] In a specific implementation, the distributing the mail sending task to the plurality of agent nodes in the preset node group according to the distribution strategy can specifically include: judging whether the distribution strategy is a directional distribution strategy; and if the distribution strategy is the directional distribution strategy, distributing the mail sending task to the plurality of agent nodes in a specific node group. It should be noted that for the phishing email drill for a specific user, a specific node group can be specified in advance to send the phishing email, and the specific node group and the corresponding client are bound. Since the mail sending task of other clients cannot be dispatched to the node group, when it is determined that the distribution strategy is the directional distribution strategy, the mail sending task can be directly distributed to the agent nodes in the specific node group. In this way, the mail sending efficiency and the drill experience of some large clients can be guaranteed.

[0060] Step S13: The agent nodes in the preset node group analyze the received mail sending task to obtain a task execution mode of the mail sending task, and send the phishing email to a target drill object according to the task execution mode.

[0061] In the embodiment, after the mail sending task is distributed to the plurality of agent nodes in the preset node group according to the distribution strategy, the received mail sending task is further analyzed by the agent nodes in the preset node group to obtain a task execution mode of the mail sending task, and then the corresponding phishing email is sent to a target drill object according to the task execution mode. The target drill object includes but is not limited to employees of a company, teachers and students of a school, and the like.

[0062] Specifically, the agent nodes in the preset node group analyze the received mail sending task to obtain a task execution mode of the mail sending task, and send the phishing email to the target rehearsal object according to the task execution mode. This can include: the agent nodes in the preset node group analyze the respective received mail sending task to obtain a task type and a task execution mode of the mail sending task, and determine whether the task type is a phishing email rehearsal type. If the task type is a phishing email rehearsal type, an plugin path corresponding to the phishing email rehearsal type is obtained, a phishing email rehearsal plugin is obtained from a configuration file of the corresponding agent node according to the plugin path, and the phishing email rehearsal plugin is called to send the phishing email to the target rehearsal object according to the task execution mode. It can be understood that the agent node can process not only phishing email rehearsal business, but also other businesses such as data forwarding, parameter configuration, etc., and different plugins can process different businesses. Therefore, after the agent node receives a mail sending task, it can first analyze the mail sending task to obtain the task type and the task execution mode of the mail sending task. Then, it is determined whether the current task type is a phishing email rehearsal type. If so, the plugin (plugin) path corresponding to the phishing email rehearsal type is obtained, the phishing email rehearsal plugin is obtained from the configuration file (config.toml) of the corresponding agent node according to the plugin path, and the phishing email rehearsal plugin is called to send the phishing email to the target rehearsal object according to the task execution mode (such as an immediate execution mode, an execution mode within a certain time period, etc.).

[0063] In this embodiment, the supported plugin capabilities can be specified in the configuration file of each agent node in advance, and the plugin paths corresponding to different types of plugins and whether to enable, etc. are recorded to facilitate fast acquisition of the plugin.

[0064] Further, after the agent node sends the phishing email to the target rehearsal object according to the task execution mode, it can also report the message after task execution (such as sending success and sending failure) to the master control service (manager service), and when the master control service (manager service) receives the reported message, it can set the node state of the corresponding agent node to an idle state.

[0065] Step S14: detecting the sending rate of the phishing email in the current sending task execution process by the master management service, and judging whether the sending rate is greater than a preset rate threshold, if not greater than the preset rate threshold, creating a new agent node in the preset node group, and sending the phishing email to be sent by using the new agent node.

[0066] In the embodiment, the sending rate of the phishing email in the current sending task execution process can be detected by the master management service, and then the sending rate is compared with the preset rate threshold. If the current sending rate is not greater than the preset rate threshold, it indicates that the current sending rate is small. At this time, in order to improve the sending rate, a new agent node can be created in the preset node group, that is, the preset node group is expanded, and then the phishing email to be sent is sent by using the new agent node. For example, after a sending task is issued, the master management service queries whether there is agent node information in the agent state table in an idle state. If not, the node group is appropriately expanded to ensure the sending efficiency.

[0067] In the embodiment, if the sending rate is greater than the preset rate threshold, the number of agent nodes in the preset node group is reduced to shrink the preset node group. In the embodiment, in order to reasonably use resources, when the sending rate is greater than the preset rate threshold, it indicates that the current agent node is too much. At this time, the number of agent nodes in the preset node group can be reduced to shrink the preset node group. For example, when it is detected that the sending is too fast to generate a return prompt, the sending rate can be reduced by using the node shrinkage + increasing the time interval of the reservation sending, or the reservation sending time of the email to be sent in the database is delayed, and the reservation interval of the email to be sent is increased, so as to reduce the sending rate.

[0068] It can be seen that, in the embodiment of the application, the Open API interface preset is called through a target business system to create a sending task for each phishing email, and it is determined whether the scheduled sending time has been reached. If the scheduled sending time has been reached, the Open API interface is used to distribute each sending task to a pre-created master management service to determine a distribution strategy of the sending task, and the sending task is distributed to multiple agent nodes in a preset node group according to the distribution strategy. Then, the agent nodes in the preset node group are used to analyze the received sending task to obtain a task execution mode of the sending task, and the phishing email is sent to a target practice object according to the task execution mode. Then, the master management service is used to detect a sending rate of the phishing email in the sending task execution process, and it is determined whether the sending rate is greater than a preset rate threshold. If the sending rate is not greater than the preset rate threshold, a new agent node is created in the preset node group, and the new agent node is used to send the phishing email to be sent. In the embodiment of the application, the Open API interface preset is called to create a sending task for each phishing email, and the sending task is sent to the pre-created master management service. The task is distributed to multiple agent nodes in a node group according to a distribution strategy of the sending task, and the phishing email is practiced through the multiple agent nodes. In the practice process, it is determined whether the current sending rate is greater than a preset rate threshold. If yes, a new agent node is created, so that the capacity of the node group is expanded, that is, the dynamic sending efficiency is adjusted. With the increase of the agent nodes, the sending efficiency can be improved, the email can be sent in time, the user (that is, the target practice object) can receive the email without delay, and a good phishing email practice effect is achieved. The method is suitable for a SaaS multi-tenant phishing email practice scene.

[0069] The embodiment of the application discloses a specific sending rate adjustment method, as shown in Figure 3 The method comprises the following steps:

[0070] Step S21: An Open API interface preset is called through a target business system to create a sending task for each phishing email, and it is determined whether the scheduled sending time has been reached.

[0071] Step S22: If the scheduled sending time has been reached, the Open API interface is used to distribute each sending task to a pre-created master management service to determine a distribution strategy of the sending task, and it is determined whether the distribution strategy is a directional distribution strategy.

[0072] Step S23: If the distribution strategy is a non-directional distribution strategy, the manager service is used to query the agent state table to obtain all online agent nodes in the preset node group, to obtain an agent list, and a consistent hashing algorithm is used to calculate the agent list to obtain a consistent hashing ring.

[0073] In this embodiment, if the current distribution strategy is a non-directional distribution strategy, the manager service is used to query the agent state table to obtain all online agent nodes in the preset node group, to obtain an agent list, and a consistent hashing algorithm is used to calculate the agent list to obtain a consistent hashing ring.

[0074] Step S24: A hash value is calculated based on the task ID of the sending task, and a corresponding target agent node is determined from the consistent hashing ring based on the hash value.

[0075] In this embodiment, after the consistent hashing ring is obtained, a hash value is calculated based on the task ID of the sending task, and a corresponding target agent node is determined from the consistent hashing ring based on the hash value.

[0076] Step S25: It is detected whether the target agent node is in an idle state, and if the target agent node is in an idle state, the corresponding sending task is sent to the target agent node.

[0077] In this embodiment, for the determined target agent node, it is first detected whether it is in an idle state, and if yes, the corresponding sending task is directly sent to the target agent node, and if no, a hash value is continuously calculated, a new agent node is determined, and it is detected whether the new agent node is in an idle state, and if yes, the corresponding sending task is sent to the new agent node.

[0078] Step S26: The received sending task is parsed by the agent nodes in the preset node group to obtain a task execution mode of the sending task, and the phishing email is sent to a target exercise object according to the task execution mode.

[0079] Step S27: The sending rate of the phishing email in the current sending task execution process is detected by the manager service, and it is judged whether the sending rate is greater than a preset rate threshold, and if not greater than the preset rate threshold, a new agent node is created in the preset node group, and the phishing email to be sent is sent by using the new agent node.

[0080] The more specific processing procedures of steps S21, S22, S26, and S27 will be described in the foregoing embodiments, and will not be described here.

[0081] It can be seen that, when the distribution strategy is a non-directional distribution strategy, the embodiment of the application queries the agent state table through the master management service to obtain all online agent nodes located in the preset node group, obtains an agent list, calculates the agent list by using a consistent hashing algorithm to obtain a consistent hashing ring, then calculates a hash value based on the task ID of the sending task, determines the corresponding target agent node from the consistent hashing ring based on the hash value, then detects whether the target agent node is in an idle state, if the target agent node is in an idle state, the corresponding sending task is sent to the target agent node, the phishing email is sent to the target exercise object according to the task execution mode, the sending rate of the phishing email in the sending task execution process is detected by the master management service, and a new agent node is created in the preset node group when the sending rate is not greater than the preset rate threshold, and the new agent node is used to send the phishing email to be sent. The embodiment of the application abstracts the sending task of each phishing email as a distributed task by distributed task scheduling and arrangement, sends the phishing email through multiple idle agent nodes, and expands and shrinks the agent nodes through the preset master management service, so that the sending rate is not too fast or too slow / blocking, so that the recipient can receive the email in time, and then query, click the link or execute the attachment, thereby achieving better exercise effect.

[0082] Correspondingly, the embodiment of the application also discloses a sending rate adjusting device, as shown in Figure 4 The device comprises:

[0083] The interface calling module 11 is configured to call a preset Open API interface through a target business system to create a sending task for each phishing email.

[0084] The first judgment module 12 is configured to judge whether the scheduled sending time has arrived.

[0085] The task issuing module 13 is configured to issue each sending task to the pre-created master management service through the Open API interface if the scheduled sending time has arrived, to determine the distribution strategy of the sending task, and distribute the sending task to multiple agent nodes in the preset node group according to the distribution strategy.

[0086] The analysis module 14 is configured to analyze the received sending task by an agent node in the preset node group to obtain a task execution mode of the sending task.

[0087] The mail sending module 15 is configured to send the phishing mail to a target rehearsal object according to the task execution mode.

[0088] The sending rate detection module 16 is configured to detect a sending rate of the phishing mail in the current sending task execution process by the master control management service.

[0089] The second judgment module 17 is configured to judge whether the sending rate is greater than a preset rate threshold.

[0090] The sending rate adjustment module 18 is configured to create a new agent node in the preset node group if the sending rate is not greater than the preset rate threshold, and send the phishing mail to be sent by using the new agent node.

[0091] The specific working process of each module can refer to the corresponding content disclosed in the foregoing embodiments, and will not be described here.

[0092] It can be seen that in the embodiment of the present application, first, the Open API interface preset is called through the target business system to create a sending task for each phishing email, and it is judged whether the scheduled sending time has been reached. If the scheduled sending time has been reached, the Open API interface is used to distribute the sending task to the pre-created master management service to determine the distribution strategy of the sending task, and the sending task is distributed to multiple agent nodes in the preset node group according to the distribution strategy. Then, the agent nodes in the preset node group are used to analyze the received sending task to obtain the task execution mode of the sending task, and the phishing email is sent to the target object according to the task execution mode. Then, the master management service is used to detect the sending rate of the phishing email in the sending task execution process, and it is judged whether the sending rate is greater than the preset rate threshold. If the sending rate is not greater than the preset rate threshold, a new agent node is created in the preset node group, and the new agent node is used to send the phishing email to be sent. In the embodiment of the present application, the Open API interface preset is called to create the sending task of each phishing email, and the sending task is sent to the pre-created master management service. The task is distributed to multiple agent nodes in the node group according to the distribution strategy of the sending task, and the phishing email is practiced through multiple agent nodes. In the practice process, it is judged whether the current sending rate is greater than the preset rate threshold. If yes, a new agent node is created, so as to realize the expansion of the node group, that is, the dynamic sending efficiency adjustment. With the increase of the agent nodes, the sending efficiency can be improved, the email can be sent out in time, the user (that is, the target object) can receive the email without delay, so as to achieve good phishing email practice effect, and the method is suitable for SaaS multi-tenant phishing email practice scene.

[0093] In some specific embodiments, the interface calling module 11 can specifically include:

[0094] The interface calling unit is configured to call the Open API interface preset through the phishing engine to create a sending task for each phishing email. The sending task includes the phishing email, a task ID, a task type, and a task execution mode.

[0095] In some specific embodiments, the task distribution module 13 can specifically include:

[0096] The first judgment unit is configured to judge whether the distribution strategy is a directional distribution strategy.

[0097] The first node determination unit is configured to determine an agent node in an idle state from the preset node group if the distribution strategy is a non-directional distribution strategy.

[0098] The first task distribution unit is configured to distribute the sending task to an agent node in an idle state.

[0099] In some embodiments, the task issuing module 13 can specifically include:

[0100] The second judging unit is configured to judge whether the distribution strategy is a directional distribution strategy.

[0101] The second task distribution unit is configured to distribute the sending task to multiple agent nodes in a specific node group if the distribution strategy is a directional distribution strategy.

[0102] In some embodiments, the task issuing module 13 can specifically include:

[0103] The third judging unit is configured to judge whether the distribution strategy is a directional distribution strategy.

[0104] The querying unit is configured to query an agent state table through the master control management service to obtain all online agent nodes in a preset node group and obtain an agent list if the distribution strategy is a non-directional distribution strategy.

[0105] The first calculating unit is configured to calculate the agent list by using a consistent hashing algorithm to obtain a consistent hashing ring.

[0106] The second calculating unit is configured to calculate a hash value based on a task ID of the sending task.

[0107] The second node determining unit is configured to determine a corresponding target agent node from the consistent hashing ring based on the hash value.

[0108] The detecting unit is configured to detect whether the target agent node is in an idle state.

[0109] The task issuing unit is configured to issue the corresponding sending task to the target agent node if the target agent node is in an idle state.

[0110] In some embodiments, the parsing module 14 can specifically include:

[0111] The task parsing unit is configured to parse the sending task received by each agent node in the preset node group to obtain a task type and a task execution mode of the sending task.

[0112] The fourth judging unit is configured to judge whether the task type is a phishing email drill type.

[0113] The acquisition unit is configured to acquire a plug-in path corresponding to the phishing email rehearsal type if the task type is the phishing email rehearsal type, and acquire a phishing email rehearsal plug-in from a configuration file of the corresponding agent node according to the plug-in path.

[0114] Correspondingly, the mail sending module 15 can specifically include:

[0115] The plug-in calling unit is configured to call the phishing email rehearsal plug-in to send the phishing email to a target rehearsal object according to the task execution mode.

[0116] In some specific embodiments, the sender rate adjusting device can further include:

[0117] The capacity reduction unit is configured to reduce the number of agent nodes in the preset node group to reduce the capacity of the preset node group if the sender rate is greater than the preset rate threshold.

[0118] Further, the embodiment of the present application further discloses an electronic device, Figure 5 is an electronic device 20 structure diagram shown according to an exemplary embodiment, the content in the figure cannot be considered as any limitation on the use range of the present application.

[0119] Figure 5 A structure schematic diagram of an electronic device 20 provided by the embodiment of the present application. The electronic device 20 can specifically include at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25 and a communication bus 26. The memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21 to realize the related steps in the sender rate adjusting method disclosed in any of the preceding embodiments. In addition, the electronic device 20 in the embodiment can be an electronic computer.

[0120] In the embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol followed by the communication interface 24 can be any communication protocol applicable to the technical solution of the present application, which is not limited here; the input / output interface 25 is used to obtain external input data or output data to the outside, and the specific interface type can be selected according to the specific application needs, which is not limited here.

[0121] In addition, the memory 22 as a carrier for resource storage can be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc., and the resources stored thereon can include an operating system 221, a computer program 222, etc., and the storage mode can be temporary storage or permanent storage.

[0122] The operating system 221 is used to manage and control the various hardware devices and computer programs 222 on the electronic device 20, which can be Windows Server, Netware, Unix, Linux, etc. The computer programs 222 can further include computer programs capable of performing other specific tasks in addition to the computer programs capable of performing the outgoing rate adjustment method disclosed by any of the preceding embodiments executed by the electronic device 20.

[0123] Further, the present application also discloses a computer readable storage medium for storing a computer program; wherein the computer program is executed by a processor to implement the outgoing rate adjustment method disclosed above. The specific steps of the method can refer to the corresponding content disclosed in the preceding embodiments, which will not be repeated here.

[0124] Further, the embodiments of the present application also disclose a computer program product comprising computer programs / instructions, which are executed by a processor to implement the steps of the outgoing rate adjustment method disclosed above.

[0125] The embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts of each embodiment can be referred to each other. For the device disclosed by the embodiments, since it corresponds to the method disclosed by the embodiments, the description is relatively simple, and the related parts can refer to the method part.

[0126] The skilled person can further realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized by electronic hardware, computer software or a combination of both. In order to clearly show the interchangeability of hardware and software, the components and steps of each example have been described in the above description. Whether the functions are realized by hardware or software depends on the specific application and design constraints of the technical solution. The skilled person can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0127] The steps of the method or algorithm described in combination with the embodiments disclosed herein can be directly implemented by hardware, software modules executed by a processor, or a combination of both. The software modules can be placed in random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art.

[0128] Finally, it needs to be pointed out that in this article, the relationship terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between the entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0129] The above provides a detailed introduction to the sender rate adjustment method, device, equipment and storage medium provided by the present application. The principles and implementation modes of the present application are described in this article by applying specific examples. The above example is only used to help understand the method and core idea of the present application; at the same time, for those skilled in the art, according to the idea of the present application, the specific implementation mode and application range will be changed; in view of the above, the content of the specification should not be understood as a limitation of the present application.

Claims

1. A method of adjusting a transmission rate, characterized by, The method comprises the following steps: calling a preset Open API interface of a target business system to create a sending task for each phishing email and determining whether the scheduled sending time has arrived; if the scheduled sending time has arrived, issuing each sending task to a pre-created master management service through the Open API interface to determine a distribution strategy of the sending task and distributing the sending task to multiple agent nodes in a preset node group according to the distribution strategy; analyzing the received sending task by the agent nodes in the preset node group to obtain a task execution mode of the sending task and sending the phishing email to a target test object according to the task execution mode; detecting the sending rate of the phishing email in the sending task execution process by the master management service and determining whether the sending rate is greater than a preset rate threshold, if not, creating a new agent node in the preset node group and sending the phishing email to be sent by the new agent node.

2. The sender rate adjustment method of claim 1, wherein, The method comprises the following steps: calling a preset Open API interface by a phishing engine to create a sending task for each phishing email; the sending task contains the phishing email, task ID, task type and task execution mode.

3. The sender rate adjustment method of claim 1, wherein, The method comprises the following steps: determining whether the distribution strategy is a directional distribution strategy; if the distribution strategy is a non-directional distribution strategy, determining an agent node in an idle state from the preset node group and distributing the sending task to the agent node in the idle state.

4. The sender rate adjustment method of claim 1, wherein, The method comprises the following steps: determining whether the distribution strategy is a directional distribution strategy; if the distribution strategy is a directional distribution strategy, distributing the sending task to multiple agent nodes in a specific node group.

5. The sender rate adjustment method of claim 2, wherein, The method comprises the following steps: determining whether the distribution strategy is a directional distribution strategy; if the distribution strategy is a non-directional distribution strategy, querying an agent state table by the master management service to obtain all online agent nodes in the preset node group to obtain an agent list and calculating the agent list by a consistent hash algorithm to obtain a consistent hash ring; calculating a hash value based on the task ID of the sending task and determining a corresponding target agent node from the consistent hash ring based on the hash value; detecting whether the target agent node is in an idle state; if the target agent node is in an idle state, issuing the corresponding sending task to the target agent node.

6. The sender rate adjustment method of claim 2, wherein, The agent nodes in the preset node group analyze the received mail sending tasks to obtain task execution modes of the mail sending tasks, and send the phishing emails to target rehearsal objects according to the task execution modes, including: The agent nodes in the preset node group analyze the received mail sending tasks to obtain task execution modes of the mail sending tasks, and send the phishing emails to target rehearsal objects according to the task execution modes, including: The agent nodes in the preset node group analyze the received mail sending tasks to obtain task execution modes of the mail sending tasks, and send the phishing emails to target rehearsal objects according to the task execution modes, including:

7. The sender rate regulating method according to any one of claims 1 to 6, characterized by, Also including: If the sending rate is greater than the preset rate threshold, the number of agent nodes in the preset node group is reduced to scale down the preset node group.

8. A dispatch rate adjustment apparatus, characterized by, Including: The interface calling module is configured to call a preset Open API interface through a target business system to create a mail sending task for each phishing email; The first judgment module is configured to judge whether the current time has reached a scheduled sending time; The task issuing module is configured to issue each mail sending task to a pre-created master management service through the Open API interface if the current time has reached the scheduled sending time, to determine a distribution strategy of the mail sending tasks, and distribute the mail sending tasks to a plurality of agent nodes in a preset node group according to the distribution strategy; The analysis module is configured to analyze the received mail sending tasks through the agent nodes in the preset node group to obtain task execution modes of the mail sending tasks; The email sending module is configured to send the phishing emails to target rehearsal objects according to the task execution modes; The sending rate detection module is configured to detect a sending rate of the phishing emails in a current mail sending task execution process through the master management service; The second judgment module is configured to judge whether the sending rate is greater than a preset rate threshold; The sending rate adjustment module is configured to create a new agent node in the preset node group if the sending rate is not greater than the preset rate threshold, and use the new agent node to send the phishing emails to be sent.

9. An electronic device, comprising: A processor and a memory are included; when the processor executes a computer program saved in the memory, the sending rate adjustment method of any one of claims 1 to 7 is realized.

10. A computer-readable storage medium, characterized in that, A computer program is stored; when the computer program is executed by a processor, the sending rate adjustment method of any one of claims 1 to 7 is realized.

Images