Micro honeypot deployment system, method and device, computer equipment and storage medium
By working together with the honeypot scheduling center and probe units, malicious URLs are generated and attack user information is collected. Attack identifiers are generated and honeypot status is updated. This solves the problem that honeypot technology cannot collect attack user information, and enables the capture and analysis of attack behavior, thereby enhancing network security protection.
Patent Information
- Application Number
- CN202411035112.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-31
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2044-07-31
AI Technical Summary
Existing honeypot technology cannot effectively collect information such as the real IP address of the attacking user, and the attacking user will not continue to pay attention after discovering the honeypot, making it impossible to judge the attack status of the real business system.
Malicious URLs are generated through the honeypot scheduling center. Combined with the probe unit to monitor the business system, the identity information and attack behavior of the attacking user are collected, an attack identifier is generated, and the honeypot status is updated based on the query content of the identifier to lure or silence the attacker, thereby capturing and analyzing the attacking user information.
It enables the capture of attacking users' behavior without affecting normal user operations, enhancing the security protection capabilities of real business systems and enabling the identification and recording of attacking users' identities and behaviors.
Smart Images

Figure CN118921206A_ABST
Abstract
Description
Technical Field
[0001] This specification relates to the field of information security technology, in particular to micro-honeypot deployment systems, methods, devices, computer equipment and storage media. Background Art
[0002] With the development of Internet technology, network attack technology has also developed, posing a certain threat to network information security and affecting Internet information security.
[0003] Among the commonly used network attack identification methods, honeypot technology, as a new security tool, has certain advantages in attack detection and analysis. Its essence is to deploy a virtual environment on computers and other devices to simulate one or more vulnerable hosts to lure attacking users to attack. At present, honeypots are independent of real business systems. After the attacking users realize that their attack targets are honeypots instead of real business systems, they will not continue to pay attention to the honeypots. Therefore, they cannot further obtain information about the attacking users, nor can they judge the attack status of the real business systems. And because the attacking users usually use multi-layer proxies, the existing honeypot technology cannot effectively collect the real IP and other information of the attacking users. Summary of the invention
[0004] In order to solve the problem that the attacking user information cannot be obtained in the above-mentioned prior art, the embodiments of this specification provide a micro-honeypot deployment system, method, apparatus, computer equipment and storage medium.
[0005] An embodiment of the present specification provides a micro-honeypot deployment system, which includes: a micro-honeypot scheduling center, which is used to generate different malicious URLs according to different vulnerabilities of different technical architectures; send the malicious URLs to the probe unit for monitoring; receive the identity information of the attacking user, the attacked business system and the honeypot corresponding to the attacked application vulnerability collected by each probe in the probe unit, and generate an attack identifier of the attacking user; query the content corresponding to the attack identifier according to the attack identifier; and send the content to the attacking user as a response result.
[0006] According to one aspect of the embodiments of the present specification, the micro-honeypot scheduling center is further used to count the attack frequency of the attacking user within a preset period based on the monitoring results collected by the probe; determine whether the attack frequency of the attacking user exceeds the preset number of times; if so, update the working state of the honeypot corresponding to the attacked vulnerability to a lure state; if not, update the working state of the honeypot corresponding to the attacked vulnerability to a silent state; update the working state of the honeypot to the content to obtain the updated content; and send the updated content to the attacking user as a response result.
[0007] According to one aspect of the embodiments of this specification, the system further includes: a display module, which is used to display the registration information and attack frequency of the attacking user.
[0008] The embodiments of the present specification provide a micro-honeypot deployment method, which is applied to a micro-honeypot deployment system, including: generating different malicious URLs according to different vulnerabilities of different technical architectures; sending the malicious URLs to the probe unit, which monitors various applications of the business system to collect registration information of the attacking user and request information of the attacking user; generating an attack identifier of the attacking user according to the registration information of the attacking user, the attacked business system, and the honeypot corresponding to the attacked application vulnerability in the request information of the attacking user; querying content corresponding to the attack identifier according to the attack identifier; and sending the content to the attacking user as a response result.
[0009] According to one aspect of an embodiment of the present specification, generating the attack identifier of the attacking user includes: determining the identity identifier of the attacking user based on the registration information of the attacking user; forming a three-dimensional attack identifier based on the identity identifier of the attacking user, the identifier of the attacked business system and the identifier of the honeypot, and the three-dimensional attack identifier is the attack identifier of the attacking user.
[0010] According to one aspect of an embodiment of the present specification, querying the content corresponding to the attack identifier based on the attack identifier includes: querying the vulnerability status code corresponding to the attack identifier from the scheduling center database based on the attack identifier; querying the content corresponding to the vulnerability status code from the scheduling center database based on the vulnerability status code.
[0011] According to one aspect of the embodiments of the present specification, the method further includes: based on the monitoring results, counting the attack frequency of the attacking user within a preset period; determining whether the attack frequency of the attacking user exceeds a preset number of times; if so, updating the working state of the honeypot corresponding to the attacked vulnerability to a lure state; if not, updating the working state of the honeypot corresponding to the attacked vulnerability to a silent state; updating the working state of the honeypot to the content to obtain the updated content; and sending the updated content as a response result to the attacking user.
[0012] According to one aspect of an embodiment of this specification, when multiple business systems share at least one user information, the method further includes: if any one of the multiple business systems identifies an attacking user, setting access rights of the attacking user in all other business systems.
[0013] The embodiments of this specification also provide a micro-honeypot deployment device, which includes: a URL generation unit, which is used to generate different malicious URLs according to different vulnerabilities of different technical architectures; a monitoring result acquisition unit, which is used to send the malicious URL to the probe unit, and the probe unit monitors various applications of the business system to collect the registration information of the attacking user and the request information of the attacking user; an attack identifier generation unit, which is used to generate an attack identifier of the attacking user according to the registration information of the attacking user, the attacked business system and the honeypot corresponding to the attacked application vulnerability in the request information of the attacking user; a content determination unit, which is used to query the content corresponding to the attack identifier according to the attack identifier; and a sending unit, which is used to send the content to the attacking user as a response result.
[0014] An embodiment of the present specification provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the method is implemented when the processor executes the computer program.
[0015] The embodiments of the present specification also provide a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the method is implemented when the computer program is executed by a processor.
[0016] This manual implements the deployment and scheduling capabilities of micro honeypots without affecting normal user use, and can capture the attack behavior of attacking users. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0018] Figure 1 The figure shows a schematic diagram of a micro honeypot deployment system according to an embodiment of the present specification;
[0019] Figure 2 It is a flowchart of a micro honeypot deployment method according to an embodiment of this specification;
[0020] Figure 3 The figure is a flow chart of a method for generating an attack identifier of an attacking user according to an embodiment of the present specification;
[0021] Figure 4 The figure is a flow chart of a method for querying content according to an embodiment of the present specification;
[0022] Figure 5The figure shows a flow chart of a method for updating corresponding results according to an embodiment of the present specification;
[0023] Figure 6 The figure shows a schematic diagram of the structure of a micro honeypot deployment device according to an embodiment of the present specification;
[0024] Figure 7 The figure shows a specific structural diagram of the micro honeypot deployment device according to the embodiment of this specification;
[0025] Figure 8 The figure shows a schematic diagram of the structure of a computer device according to an embodiment of the present specification.
[0026] Description of the accompanying symbols:
[0027] 100. Micro honeypot dispatch center;
[0028] 200, probe unit;
[0029] 601. URL generation unit;
[0030] 602. Monitoring result obtaining unit;
[0031] 603, attack identification generating unit;
[0032] 6031, identity identification module;
[0033] 604, content determination unit;
[0034] 6041. Vulnerability status code determination module;
[0035] 605, sending unit;
[0036] 802. Computer equipment;
[0037] 804, processor;
[0038] 806. Memory;
[0039] 808, driving mechanism;
[0040] 810, input / output module;
[0041] 812. Input device;
[0042] 814. Output device;
[0043] 816. Presentation equipment;
[0044] 818. Graphical user interface;
[0045] 820, network interface;
[0046] 823, communication link;
[0047] 824. Communication bus. DETAILED DESCRIPTION
[0048] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.
[0049] It should be noted that the terms "first", "second", etc. in the description and claims of this specification and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of this specification described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.
[0050] This specification provides method operation steps as described in the embodiments or flow charts, but more or fewer operation steps may be included based on routine or non-creative work. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the system or device product is executed in practice, it can be executed in the order of the method shown in the embodiments or the drawings or in parallel.
[0051] It should be noted that the micro-honeypot deployment system and method of this specification can be used in the computer field as well as in the financial technology field. This specification does not limit the application field of the micro-honeypot deployment system and method.
[0052] Figure 1 FIG. 1 is a schematic diagram of a micro honeypot deployment system according to an embodiment of the present specification. The system includes: a micro honeypot scheduling center 100 and a probe unit 200 .
[0053] In the embodiment of the present specification, the micro honeypot dispatch center 100 is used to generate different malicious URLs according to different vulnerabilities of different technical architectures. The malicious URLs are sent to the probe unit 200 for monitoring; the identity information of the attacking user, the attacked business system and the honeypot corresponding to the attacked application vulnerability collected by each probe in the probe unit 200 are received, and the attack identifier of the attacking user is generated; according to the attack identifier, the content corresponding to the attack identifier is queried; and the content is sent to the attacking user as a response result.
[0054] In the embodiment of the present specification, the micro honeypot dispatch center 100 includes multiple honeypots. Among them, the honeypot is an active defense technology running in the Internet computer system. Specifically, the honeypot is a decoy system containing vulnerabilities. The honeypot can capture and analyze attack behaviors, understand the tools and methods used by the attacking user, infer the intention and motivation of the attacking user, and enhance the security protection capability of the actual business system, so as to better protect the real system.
[0055] In the embodiment of the present specification, the probe unit 200 includes a plurality of probes. Each probe is deployed on each application in each business system. The malicious URL generated by the micro honeypot scheduling center 100 is dynamically registered on the probe. Specifically, each business system is deployed with a probe, and a probe can monitor multiple URLs, and one URL corresponds to a honeypot (or vulnerability).
[0056] In the field of network security, a probe (Agent) generally refers to a software component or program used to perform a specific security task. The probe can be deployed at different locations in the network to monitor, collect and analyze data, and execute security policies. In an embodiment of the present specification, the probe is used to receive a monitoring request sent by a micro-honeypot scheduling center, wherein the monitoring request includes a malicious URL path. Therefore, the probe is mainly used to register the URL path in the monitoring request sent by the micro-honeypot scheduling center to the probe's filter (Filter). A filter is a software component used to process a data stream, typically used for data verification, data conversion, data compression, or processing network communications. In Web development, a filter is part of the Java Servlet specification, which can intercept client requests and server responses, and process, filter, and convert them to improve the ease of use, security, and scalability of Web applications.
[0057] Furthermore, the probe can work in conjunction with the honeypot / vulnerability in the business system. For example, the probe can monitor the status of the honeypot and collect the attack data captured by the honeypot, and then send this data to the micro-honeypot scheduling center for analysis. Specifically, according to the monitoring request sent by the micro-honeypot scheduling center, the malicious URL path in the monitoring request is registered in the filter in the probe, and then the user access situation is collected. When an attack request is obtained from the collected user access situation, the registration information and identity information of the attacking user who issued the attack request is determined; the registration information and identity information of the attacking user are sent to the micro-honeypot scheduling center. In this specification, the probe has no impact on the business, and can enable the security team to understand the security status of the network in real time. Honeypots and probes can jointly build a more comprehensive and effective security protection system.
[0058] In the embodiment of this specification, the probe unit 200 first creates a serversocket to monitor the malicious URL sent by the micro-honeypot scheduling center 100, and registers the malicious URL in the probe's filter to collect the access information of the attacking user. After the request is monitored, the data content of the monitoring request is parsed and the updated malicious URL list is taken out. Further, the ServletContext object is obtained and a FilterRegistration.Dynamic object is created to configure a new mapping relationship to realize the dynamic registration of malicious URLs.
[0059] In an embodiment of the present specification, the micro-honeypot scheduling center is further used to count the attack frequency of the attacking user within a preset period based on the monitoring results collected by the probe; determine whether the attack frequency of the attacking user exceeds the preset number of times; if so, update the working state of the honeypot corresponding to the attacked vulnerability to a lure state; if not, update the working state of the honeypot corresponding to the attacked vulnerability to a silent state; update the working state of the honeypot to the content to obtain the updated content; and send the updated content to the attacking user as a response result.
[0060] In some embodiments of the present specification, the system further includes: a display module 300 (not shown), which is used to display the registration information and attack frequency of the attacking user; for example, the registration information and attack frequency are displayed on a display screen or a client interface.
[0061] Figure 2 The above is a flowchart of a micro honeypot deployment method according to an embodiment of this specification, which specifically includes the following steps:
[0062] Step 201, generating different malicious URLs according to different vulnerabilities of different technical architectures.
[0063] In some embodiments of this specification, different business systems have different technical architectures, different technical frameworks have different vulnerabilities, and different vulnerabilities have different attack behaviors after being identified. For example, business system A is a business system developed based on PHP, and business system B is a business system built based on Java language. The vulnerabilities of different business systems are quite different. In this specification, the micro-honeypot scheduling center generates different malicious URLs according to the technical architecture types of different business systems, and each malicious URL will be registered to the probe agent later.
[0064] Step 202: Send the malicious URL to the probe unit, which monitors various applications of the business system and collects the registration information of the attacking user and the request information of the attacking user.
[0065] In this step, the micro-honeypot scheduling center sends the malicious URL path to the probe unit and registers the malicious URL path to the filter of the probes of different business systems to collect the access status of the attacking user in real time.
[0066] In the embodiments of this specification, after the attacking user logs in to the business system on the Internet, he will perform operations such as packet capture, scanning, and vulnerability detection on the business system. Among them, the attacking user initiates different requests to the business system to perform operations such as vulnerability detection. In the process of initiating requests and performing operations, the attacking user will trigger the honeypot in the business system. That is, the request initiated by the attacking user will be captured by the filter in the business system. Specifically, after the honeypot detects that the attacking user has initiated a request, it will collect the attacking user's registration information, request information, etc. according to the attacking user's behavior.
[0067] Step 203: Generate an attack identifier of the attacking user according to the registration information of the attacking user, the attacked business system, and the honeypot corresponding to the attacked application vulnerability in the request information of the attacking user.
[0068] In the embodiment of this specification, this step will capture the request sent by the attacking user in real time and parse the request, so as to obtain the registration information of the attacking user, the business system attacked by the attacking user, and the honeypot corresponding to the application vulnerability attacked by the attacking user. Among them, the registration information of the attacking user includes but is not limited to: the IP of the attacking user and the user-agent of the attacking user. Furthermore, according to the jwt, sessionid and other information in the request sent by the attacking user, the registration information and other data of the attacking user in the current business system are queried.
[0069] The identity information, account number and other registration information of the attacker are sent back to the micro honeypot dispatch center together with the attacker's request data, and the micro honeypot dispatch center waits for the return result. Furthermore, the URL, body, header and other information of the attacker's current request are sent to the micro honeypot dispatch center together with the attacker's registration information for processing.
[0070] In the embodiments of this specification, the business system where the probe that collects the request data of the attacking user is located is determined to be the business system attacked by the attacking user, or the attacked business system. Further, a three-dimensional identifier related to the attacking user is generated based on the registration information of the attacking user, the attacked business system, and the honeypot corresponding to the attacked application. Among them, the attacked business system has a unique corresponding number, and the honeypot corresponding to the vulnerability of the attacked application has its unique corresponding identifier. Combined with the user identity and IP-related information in the user registration information, the three-dimensional identifier of the attacking user is combined, and the three-dimensional attack identifier is the attack identifier.
[0071] Step 204: query the content corresponding to the attack identifier according to the attack identifier. Query the table corresponding to the attack identifier from the database of the micro-honeypot scheduling center according to the attack identifier. Query the return content corresponding to the attack identifier from the table.
[0072] Step 205: Send the content as a response result to the attacking user. Feedback the content in step 204 to the attacking user. This specification realizes the effective collection of the cookie information and attack traffic of the attacking user.
[0073] In this specification, listeners are registered on the honeypot and are used to monitor and respond to specific events. Usually, requests initiated by users go through the listener before reaching the servlet, and then calling specific business logic code. Therefore, by creating a listener instance, dynamically add and delete the monitored URL, and send this information to the microservice scheduling center together with the current request, wait for the return information from the microservice scheduling center, and then return it to the front end. The function of sending information from the probe module to the scheduling module is realized.
[0074] In the embodiment of this specification, a second listener for monitoring a specific URL can be created. When a specific URL request arrives, the key carried in the request is first verified. After the key verification is passed, the URL list carried in the request is saved to realize the function of the micro honeypot scheduling center dynamically updating the URL to be monitored to the probe.
[0075] Furthermore, the first listener is used as a field inside the second listener. After the second listener is instantiated, the first listener is instantiated synchronously. The second listener passes the saved URL list to the first listener object, and the first listener object dynamically adds or deletes the listening URL. This nested listener method forms a functional closed loop, which not only enables the dispatch center to dynamically push the malicious URL list, but also realizes the function of transmitting the identity information of the attacking user and the malicious request to the dispatch center.
[0076] Figure 3 The flowchart of a method for generating an attack identifier of an attacking user according to an embodiment of the present specification is shown, which specifically includes the following steps:
[0077] Step 301, determine the identity of the attacking user according to the registration information of the attacking user. In the embodiment of this specification, different honeypot deployment methods are used for different attacking users, and different attacking user identification ids are used. Specifically, a unique identity is assigned to the attacking user according to the registration IP, registration ID, etc. in the registration information of the attacking user.
[0078] Step 302: A three-dimensional attack identifier is formed according to the identity identifier of the attacking user, the identifier of the attacked business system and the identifier of the honeypot. The three-dimensional attack identifier is the attack identifier of the attacking user.
[0079] In the embodiments of the present specification, each honeypot has a unique identifier, and each business system connected to the honeypot will also assign a unique index identifier to the honeypot. Thus, based on the unique identifier and unique index identifier of the honeypot, a two-dimensional array is formed that can uniquely identify the status of each micro-honeypot in each business system.
[0080] Furthermore, because the business system usually has different honeypot deployment methods for different attacking users, it is necessary to formulate identifications related to the attacking users for different attacking users. In some embodiments of this specification, a corresponding identification can be formulated for the attacking user based on the identity information of the attacking user. Thus, based on the two-dimensional data, combined with the identity identification of the attacking user, a three-dimensional identification related to the attacking user can be formed.
[0081] In this specification, the two-dimensional identifier, the three-dimensional identifier and the content to be returned by the micro honeypot dispatch center can be combined into a Key-Value format, where the two-dimensional identifier and the three-dimensional identifier are used as the key and the value is the content to be returned. The content in the Key-Value format can be stored in the database of the micro honeypot dispatch center for subsequent query of the vulnerability status code processing according to the attack identifier.
[0082] In the embodiment of the present specification, the three-dimensional attack identification can be as follows: {system identification::honeypot id::attack user id}, {AQCSSS::mg00001::09770111}.
[0083] Figure 4 The flowchart of a method for querying content in an embodiment of this specification is shown, which specifically includes the following steps:
[0084] Step 401: According to the attack identifier, query the vulnerability status code corresponding to the attack identifier from the scheduling center database.
[0085] In the embodiment of the present specification, the type of vulnerability attacked by the attacking user can be determined according to the attack identifier of the attacking user, wherein different types of vulnerabilities have different vulnerability status codes.
[0086] Therefore, this manual classifies the types of honeypots according to the attacking behavior of the attacking user. For example, the first category is various backup and configuration file honeypots, such as / backup / 1.zip or back.zip. The second category is historical vulnerability poc verification and fingerprint recognition honeypots, such as / actuator (spring actuator sensitive information leakage vulnerability or / sys / ui / extend / theme / default / style / icon.css (Lanling OA verification poc), etc. The third category is simulated webshell type honeypots, such as / evil.jsp or / cmd.php. Each type of honeypot corresponds to a different vulnerability status code, and the mapping relationship between the honeypot and the vulnerability status code is specifically stored in the database of the micro-honeypot scheduling center. According to the attack identifier, the vulnerability status code corresponding to the attack identifier can be queried from the scheduling center database.
[0087] According to the attack identifier of the attacking user, the vulnerability identification code corresponding to the current honeypot is queried from the micro-honeypot scheduling center database to further determine the working mode corresponding to the current honeypot, wherein the working mode includes a silent mode or a lure mode.
[0088] For example, the corresponding vulnerability identification code may be a vulnerability status code such as 200, 404 or 500, etc., which is found from the dispatch center database according to the attack identification of the attacking user.
[0089] Step 402: According to the vulnerability status code, the content corresponding to the vulnerability status code is queried from the dispatch center database. In this step, the dispatch center database also stores the return content corresponding to the vulnerability status code. According to the vulnerability transition code determined in step 401, different return contents are queried and sent to the business system. The business system then feeds back the response result to the attacking user.
[0090] In the embodiments of this specification, the mapping relationship between the vulnerability status code and the content is also pre-set. Among them, the vulnerability status code 200 indicates a successful response; the vulnerability status code 404 or 500 indicates that the response result cannot be found, or there is no response result. When the honeypot is in silent mode, it returns a 404 or 500 response message, which will not attract the attention of the attacking user. When the honeypot is in the lure mode, it is the real honeypot function. In the lure mode, the honeypot returns relevant information about the existence of the corresponding vulnerability, inducing the attacking user to further waste time here. In the lure mode, this specification retains the identity data and attack traffic data of the attacking user collected by each business system.
[0091] Figure 5 The flowchart of a method for updating a response result according to an embodiment of the present specification is shown, which specifically includes the following steps:
[0092] Step 501: According to the monitoring result, the attack frequency of the attacking user within a preset period is counted.
[0093] This step counts the attack frequency within a preset period, which can be counting the number of times the business system has been attacked by attacking users in the past period of time; or it can be pre-setting a sliding time window and counting the number of times a certain business system has been attacked by users in each sliding time window.
[0094] Step 502, determining whether the attack frequency of the attacking user exceeds a preset number.
[0095] Step 503: If yes, update the working state of the honeypot corresponding to the attacked vulnerability to the luring state.
[0096] In this step, when the attack frequency exceeds the preset number, it means that the security of the business system currently attacked by the attacking user is relatively low and the danger urgency is relatively high, so the working state of the honeypot is set to the lure state.
[0097] Step 504: If not, the working state of the honeypot corresponding to the attacked vulnerability is updated to a silent state. In this step, when the attack frequency does not exceed the preset number of times, it means that the security of the business system currently attacked by the attacking user is relatively not low, and the danger urgency is not high, so the working state of the honeypot is set to a silent state.
[0098] Step 505, update the working state of the honeypot to the content to obtain updated content. In this step, the working state of the honeypot is determined according to the frequency of the honeypot being attacked within a preset period. And its working state is updated as part of the content, thereby obtaining updated content.
[0099] Step 506: Send the updated content as a response result to the attacking user. Thus, the updated content is fed back to the attacking user in a timely or real-time manner.
[0100] like Figure 6 The figure shows a schematic diagram of the structure of a micro honeypot deployment device according to an embodiment of the present specification. The figure describes the basic structure of the micro honeypot deployment device, wherein the functional units and modules can be implemented in software, or a general chip or a specific chip can be used to implement the micro honeypot deployment. The device specifically includes:
[0101] URL generation unit 601, used to generate different malicious URLs according to different vulnerabilities of different technical architectures;
[0102] The monitoring result acquisition unit 602 is used to send the malicious URL to the probe unit for monitoring, and obtain the monitoring results collected by the probe from each business system, wherein the monitoring results include the registration information of the attacking user and the request information of the attacking user;
[0103] The attack identifier generating unit 603 is used to generate an attack identifier of the attack user according to the registration information of the attack user, the attacked business system in the request information of the attack user, and the honeypot corresponding to the attacked application vulnerability in the request information of the attack user;
[0104] A content determination unit 604, configured to query content corresponding to the attack identifier according to the attack identifier;
[0105] The sending unit 605 is used to send the content as a response result to the attacking user.
[0106] As an example of this specification, please refer to Figure 7 The figure is a schematic diagram of the specific structure of the micro-honeypot deployment device according to this embodiment.
[0107] As an embodiment of this specification, the attack identifier generating unit 603 further includes:
[0108] The identity identification determination module 6031 is used to determine the identity identification of the attacking user according to the registration information of the attacking user.
[0109] As an embodiment of this specification, the content determination unit 604 further includes:
[0110] The vulnerability status code determination module 6041 is used to query the vulnerability status code corresponding to the attack identifier from the scheduling center database according to the attack identifier.
[0111] like Figure 8As shown, it is a schematic diagram of a computer device provided by an embodiment of this specification. The micro honeypot deployment method described in this specification can be executed by the computer device. The computer device 802 may include one or more processors 804, such as one or more central processing units (CPUs), and each processing unit may implement one or more hardware threads. The computer device 802 may also include any memory 806, which is used to store any kind of information such as code, settings, data, etc. Non-limiting, for example, the memory 806 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory can use any technology to store information. Further, any memory can provide volatile or non-volatile retention of information. Further, any memory can represent a fixed or removable component of the computer device 802. In one case, when the processor 804 executes an associated instruction stored in any memory or a combination of memories, the computer device 802 can perform any operation of the associated instruction. The computer device 802 also includes one or more drive mechanisms 808 for interacting with any memory, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.
[0112] The computer device 802 may also include an input / output module 810 (I / O) for receiving various inputs (via input devices 812) and for providing various outputs (via output devices 814). A specific output mechanism may include a presentation device 816 and an associated graphical user interface (GUI) 818. In other embodiments, the input / output module 810 (I / O), input device 812, and output device 814 may not be included, and the computer device 802 may be used as a computer device in a network. The computer device 802 may also include one or more network interfaces 820 for exchanging data with other devices via one or more communication links 823. One or more communication buses 824 couple the components described above together.
[0113] The communication link 823 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 823 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.
[0114] Corresponds to Figures 1 to 5 The method in the embodiment of the present specification also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are executed.
[0115] The embodiment of the present specification also provides a computer-readable instruction, wherein when the processor executes the instruction, the program therein causes the processor to execute the following Figures 1 to 5 The method shown.
[0116] The embodiments of the present specification also provide a computer program product, including at least one instruction or at least one program, wherein the at least one instruction or the at least one program is loaded and executed by a processor to implement the following Figures 1 to 5 The method shown.
[0117] It should be understood that in the various embodiments of this specification, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this specification.
[0118] It should also be understood that in the embodiments of this specification, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this specification generally indicates that the associated objects before and after are in an "or" relationship.
[0119] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in this specification can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this specification.
[0120] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0121] In the several embodiments provided in this specification, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.
[0122] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of this specification.
[0123] In addition, each functional unit in each embodiment of this specification may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0124] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this specification is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of this specification. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.
[0125] Specific embodiments are used in this specification to illustrate the principles and implementation methods of this specification. The description of the above embodiments is only used to help understand the methods and core ideas of this specification. At the same time, for those skilled in the art, according to the ideas of this specification, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on this specification.
Claims
1. A micro honeypot deployment system, characterized in that: The system comprises: The micro honeypot dispatch center is used to generate different malicious URLs according to different vulnerabilities of different technical architectures; send the malicious URLs to the probe unit for monitoring; receive the identity information of the attacking user, the attacked business system and the honeypot corresponding to the attacked application vulnerability collected by each probe in the probe unit, and generate an attack identifier of the attacking user; query the content corresponding to the attack identifier according to the attack identifier; send the content as a response result to the attacking user; A probe unit, wherein the probe unit includes a plurality of probes, wherein each probe is respectively deployed in each application in each business system, and the URL is dynamically registered on the probe, and the probe is used to receive a monitoring request sent by the micro honeypot scheduling center, wherein the monitoring request includes a malicious URL path; according to the monitoring request, the malicious URL path is registered to a filter in the probe, and user access conditions are collected; when an attack request is obtained from the collected user access conditions, the registration information and identity information of the attacking user who issued the attack request is determined; and the registration information and identity information of the attacking user are sent to the micro honeypot scheduling center.
2. The micro-honeypot deployment system according to claim 1, characterized in that: The micro honeypot scheduling center is further used to count the attack frequency of the attacking user within a preset period according to the monitoring results collected by the probe; determine whether the attack frequency of the attacking user exceeds the preset number of times; if so, update the working state of the honeypot corresponding to the attacked vulnerability to the luring state; if not, update the working state of the honeypot corresponding to the attacked vulnerability to the silent state; update the working state of the honeypot to the content to obtain the updated content; The updated content is sent to the attacking user as a response result.
3. The micro honeypot deployment system according to claim 2, characterized in that: The system further includes: a display module, which is used to display the registration information and attack frequency of the attacking user.
4. A micro honeypot deployment method, characterized in that: The method is applied to the micro honeypot deployment system according to any one of claims 1 to 3, comprising: Generate different malicious URLs based on different vulnerabilities of different technical architectures; The malicious URL is sent to the probe unit, which monitors various applications of the business system and collects the registration information of the attacking user and the request information of the attacking user; Generate an attack identifier of the attacking user according to the registration information of the attacking user, the attacked business system and the honeypot corresponding to the attacked application vulnerability in the request information of the attacking user; According to the attack identifier, query the content corresponding to the attack identifier; The content is sent to the attacking user as a response result.
5. The micro honeypot deployment method according to claim 4, characterized in that: Generating the attack identifier of the attacking user includes: Determine the identity of the attacking user based on the registration information of the attacking user; A three-dimensional attack identifier is formed according to the identity identifier of the attacking user, the identifier of the attacked business system and the identifier of the honeypot. The three-dimensional attack identifier is the attack identifier of the attacking user.
6. The micro honeypot deployment method according to claim 5, characterized in that: According to the attack identifier, querying the content corresponding to the attack identifier includes: According to the attack identifier, querying the vulnerability status code corresponding to the attack identifier from the dispatch center database; According to the vulnerability status code, content corresponding to the vulnerability status code is queried from a dispatch center database.
7. The micro honeypot deployment method according to claim 6, characterized in that: The method further comprises: According to the monitoring results, the attack frequency of the attacking user within the preset period is counted; Determine whether the attack frequency of the attacking user exceeds the preset number; If so, the working state of the honeypot corresponding to the attacked vulnerability is updated to the luring state; If not, the working state of the honeypot corresponding to the attacked vulnerability is updated to silent state; Updating the working status of the honeypot into the content to obtain updated content; The updated content is sent to the attacking user as a response result.
8. The micro honeypot deployment method according to claim 7, characterized in that: When multiple business systems share at least one user information, the method further includes: If any one of the multiple business systems identifies an attacking user, access rights of the attacking user are set in all other business systems.
9. A micro honeypot deployment device, characterized in that: The device comprises: A URL generation unit, used to generate different malicious URLs according to different vulnerabilities of different technical architectures; A monitoring result acquisition unit is used to send the malicious URL to the probe unit, and the probe unit monitors various applications of the business system to collect the registration information of the attacking user and the request information of the attacking user; An attack identifier generating unit, used to generate an attack identifier of the attacking user according to the registration information of the attacking user, the attacked business system and the honeypot corresponding to the attacked application vulnerability in the request information of the attacking user; a content determination unit, configured to query content corresponding to the attack identifier according to the attack identifier; The sending unit is used to send the content as a response result to the attacking user.
10. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 4 to 8 is implemented.
11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 4 to 8 is implemented.
12. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 4 to 8 is implemented.
Citation Information
Patent Citations
Network attack processing method and device
CN113676449A
Honeytoken tracker
US11057429B1
Efficient implementation of honeypot devices to detect wide-scale network attacks
US11233823B1
Intelligent-interaction honeypot for IoT devices
US20190081980A1
