Method and device for storing attack data of Internet of Things based on distributed storage system

By adopting distributed storage systems and clustering processing technology in IoT devices, the scalability and security problems of traditional centralized storage systems when storing and querying IoT attack data are solved, and efficient storage and management are achieved, improving Data reliability and user management convenience.

CN118708594BActive Publication Date: 2024-11-22WUDING SECURITY TECH (WUHAN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411123334.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-15
Publication Date
2024-11-22
Estimated Expiration
2044-08-15

AI Technical Summary

Technical Problem

Traditional centralized data storage systems face challenges of scalability, reliability and security when processing large-scale, distributed IoT data, especially how to efficiently store and protect attacked data when attacked becomes a key issue.

Method used

Using the IoT attack data storage method based on a distributed storage system, the IoT device attack data storage method is used to query and store attacked digital evidence based on the IP address and device type of the IoT device, and efficient storage and query of data is achieved, and Improve storage efficiency by clustering and merging data with similarity above the threshold.

Benefits of technology

It improves the storage and query efficiency of IoT attack data, enhances the storage efficiency of storage nodes, and provides convenience for users to manage merge events, ensuring the security and reliability of data.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118708594B_ABST
    Figure CN118708594B_ABST
Patent Text Reader

Abstract

The present invention proposes an IoT attack data storage method based on a distributed storage system. The distributed storage system includes at least one database and multiple storage nodes. The distributed storage system receives collected device information of an IoT device and attacked digital evidence, queries a database for whether a record of the IoT device already exists according to the IP address and device type of the IoT device, the database includes a main table storing device information of the IoT device and a secondary table storing a storage location of the attacked digital evidence, if a record of the IoT device already exists, queries the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, stores the collected attacked digital evidence of the IoT device in the storage location, if the record of the IoT device does not exist, adds a new record to the main table storing device information of the IoT device and the secondary table storing the storage location of the attacked digital evidence according to the IP address and device type of the IoT device.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of data storage of Internet of Things devices, and in particular to a method and device for storing attack data of Internet of Things based on a distributed storage system. Background Art

[0002] IoT technology connects billions of devices, from smart homes to industrial automation, and involves all aspects of daily life. As IoT devices become more popular, they also become targets of cyber attacks. At the same time, IoT devices face various cyber attacks, including but not limited to malware, denial of service attacks (DoS), man-in-the-middle attacks (MITM), etc. These attacks may lead to data leakage, service interruption, or device damage.

[0003] Traditional centralized data storage systems face challenges in scalability, reliability, and security when processing large-scale, distributed IoT data. Especially when attacked, how to efficiently store and protect attack data becomes a key issue. Summary of the invention

[0004] The main purpose of the present invention is to propose an IoT attack data storage method based on a distributed storage system, aiming to solve the problem of how to improve the attack data storage efficiency of IoT devices.

[0005] A method for storing attack data of the Internet of Things based on a distributed storage system, characterized in that the distributed storage system includes at least one database and multiple storage nodes, and includes the following steps:

[0006] S1, the distributed storage system receives the collected device information of the IoT device and the digital evidence of the attack, wherein the device attributes in the device information include the IP address, device type, manufacturer, hardware features and software features of the IoT device; the data type of the digital evidence of the attack includes one or more of log files, network traffic data, system configuration and status information, malware samples, intrusion traces, abnormal behavior patterns and physical evidence;

[0007] S2, according to the IP address and device type of the IoT device, query whether a record of the IoT device already exists in the database, wherein the database includes a main table storing device information of the IoT device and a secondary table storing the storage location of the attacked digital evidence;

[0008] S3, if there is a record of the IoT device, query the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and store the collected attacked digital evidence of the IoT device in the storage location;

[0009] S4: If there is no record of the IoT device, a new record is added to the main table storing the device information of the IoT device and the sub-table storing the storage location of the attacked digital evidence according to the IP address and device type of the IoT device.

[0010] There are multiple IoT devices, and the hardware characteristics include one or more of the CPU model, memory size, and storage capacity of the IoT devices.

[0011] The software features include one or more of the operating system type and version of the IoT device and installed applications.

[0012] The S2 queries whether a record of the IoT device already exists in the database according to the IP address and device type of the IoT device, wherein the database includes a main table storing device information of the IoT device and a sub-table storing the storage location of the attacked digital evidence, specifically including:

[0013] S21, constructing a master table for storing device information of IoT devices and a slave table for storing the storage location of the attacked digital evidence; the fields of the master table include device ID, IP address of IoT devices, device type, manufacturer, hardware features, and software features; the fields of the slave table include device ID, data type and storage location of the attacked digital evidence;

[0014] S22, querying whether a record of the IoT device already exists in the database according to the IP address and device type of the IoT device, and recording the query event in the system log.

[0015] If the record of the IoT device already exists, the S3 queries the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and stores the collected attacked digital evidence of the IoT device in the storage location, specifically including:

[0016] S31, if there is already a record of the IoT device, continue to compare the manufacturer, hardware features and software features of the IoT device with the existing record of the IoT device to see if they are the same; if they are the same, query the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and store the collected attacked digital evidence of the IoT device in the storage location;

[0017] S32: If different, go to step S4.

[0018] If there is no record of the IoT device in S4, then according to the IP address and device type of the IoT device, a new record is added to the main table storing the device information of the IoT device and the sub-table storing the storage location of the attacked digital evidence, specifically including:

[0019] S41, adding a new record to the main table storing device information of the IoT device according to the IP address, device type, manufacturer, hardware features, and software features of the IoT device;

[0020] S42, the storage node allocates a storage location for the attacked digital evidence of the IoT device, and adds a new record to the slave table of the storage location of the digital evidence.

[0021] Also includes:

[0022] S51, the storage node clusters the data type of the attacked digital evidence to obtain one or more clusters;

[0023] S52, in each cluster, calculating the similarity of all attacked digital evidences, merging the attacked digital evidences with similarity higher than a threshold and retaining only one copy;

[0024] S53, updating the storage location of the merged attacked digital evidence in the slave table, and adding a merge mark to the record in the slave table.

[0025] The present invention also proposes an IoT attack data storage device based on a distributed storage system, characterized in that the distributed storage system includes at least one database and multiple storage nodes, including:

[0026] The distributed storage system receives the collected device information of the IoT device and the digital evidence of the attack, wherein the device attributes in the device information include the IP address, device type, manufacturer, hardware features and software features of the IoT device; the data type of the digital evidence of the attack includes one or more of log files, network traffic data, system configuration and status information, malware samples, intrusion traces, abnormal behavior patterns and physical evidence;

[0027] A query module, used to query whether a record of the IoT device already exists in a database according to the IP address and device type of the IoT device, wherein the database includes a main table storing device information of the IoT device and a sub-table storing a storage location of the attacked digital evidence;

[0028] If a record of the IoT device already exists, query the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and store the collected attacked digital evidence of the IoT device in the storage location;

[0029] If there is no record of the IoT device, a new record is added to the main table storing the device information of the IoT device and the slave table storing the storage location of the attacked digital evidence according to the IP address and device type of the IoT device.

[0030] The present invention also proposes an IoT attack data storage device based on a distributed storage system, comprising a processor and a memory, wherein the memory stores computer program code, and is characterized in that the steps of the method described are implemented when the computer program code is executed by the processor.

[0031] The present invention also provides a computer-readable storage medium having computer program code stored thereon, characterized in that the steps of the method described are implemented when the computer program code is executed.

[0032] The beneficial effects of the present invention include: (1) when storing data, the device information of the IoT device and the storage of the attacked digital evidence are decoupled and recorded in a database. When storing, the IP address and device type are used as indexes, so that the records of specific IoT devices can be quickly located, thereby improving the efficiency of IoT attack data storage and query; (2) the storage node clusters according to the data type of the attacked digital evidence, merges the attacked digital evidence with a similarity higher than a threshold and retains only one copy, and updates the storage location of the merged attacked digital evidence in the slave table, and adds a merge mark to the record in the slave table, which can effectively improve the storage efficiency of the storage node and provide convenience for users to manage merge events. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 The present invention is a flow chart of the method. DETAILED DESCRIPTION

[0034] The present invention proposes an IoT attack data storage method based on a distributed storage system, characterized in that the distributed storage system includes at least one database and multiple storage nodes, and includes the following steps:

[0035] S1, the distributed storage system receives the collected device information of the IoT device and the digital evidence of the attack, wherein the device attributes in the device information include the IP address, device type, manufacturer, hardware features and software features of the IoT device; the data type of the digital evidence of the attack includes one or more of log files, network traffic data, system configuration and status information, malware samples, intrusion traces, abnormal behavior patterns and physical evidence;

[0036] The data types of the digital evidence being attacked are specifically: Log files: Operation logs generated by IoT devices, which record the activities and system events of the device and can show unauthorized access or abnormal behavior. Network traffic data: Communication data packets in the network can be intercepted and analyzed to determine whether there are suspicious traffic patterns or attack behaviors. System configuration and status information: The status and configuration information of the device, such as firmware version, open ports, running services, etc., can provide clues to the attack. Malware samples: If the IoT device is infected with malware, the malware samples can be used as direct evidence of the attack. Intrusion traces: Files, modified settings or other traces left by the attacker in the system can be used as evidence of the intrusion. Abnormal behavior patterns: Patterns exhibited by the device that are inconsistent with normal behavior, such as an abnormal increase in data transmission, may also be signs of an attack. Physical evidence: In some cases, physical evidence related to the IoT device may also need to be considered, such as damaged hardware.

[0037] S2, according to the IP address and device type of the IoT device, query whether a record of the IoT device already exists in the database, wherein the database includes a main table storing device information of the IoT device and a secondary table storing the storage location of the attacked digital evidence;

[0038] S3, if there is a record of the IoT device, query the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and store the collected attacked digital evidence of the IoT device in the storage location;

[0039] S4: If there is no record of the IoT device, a new record is added to the main table storing the device information of the IoT device and the sub-table storing the storage location of the attacked digital evidence according to the IP address and device type of the IoT device.

[0040] There are multiple IoT devices, and the hardware characteristics include one or more of the CPU model, memory size, and storage capacity of the IoT devices.

[0041] The software features include one or more of the operating system type and version of the IoT device and installed applications.

[0042] The S2 queries whether a record of the IoT device already exists in the database according to the IP address and device type of the IoT device, wherein the database includes a main table storing device information of the IoT device and a sub-table storing the storage location of the attacked digital evidence, specifically including:

[0043] S21, constructing a master table for storing device information of IoT devices and a slave table for storing the storage location of the attacked digital evidence; the fields of the master table include device ID, IP address of IoT devices, device type, manufacturer, hardware features, and software features; the fields of the slave table include device ID, data type and storage location of the attacked digital evidence;

[0044] S22, querying whether a record of the IoT device already exists in the database according to the IP address and device type of the IoT device, and recording the query event in the system log.

[0045] It can also include users querying system logs and migrating digital evidence of attacks on frequently queried IoT devices to one or more storage nodes with the best read and write performance.

[0046] The user is a system administrator or a network security engineer;

[0047] If the record of the IoT device already exists, the S3 queries the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and stores the collected attacked digital evidence of the IoT device in the storage location, specifically including:

[0048] S31, if there is already a record of the IoT device, continue to compare the manufacturer, hardware features and software features of the IoT device with the existing record of the IoT device to see if they are the same; if they are the same, query the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and store the collected attacked digital evidence of the IoT device in the storage location;

[0049] S32: If different, go to step S4.

[0050] If there is no record of the IoT device in S4, then according to the IP address and device type of the IoT device, a new record is added to the main table storing the device information of the IoT device and the sub-table storing the storage location of the attacked digital evidence, specifically including:

[0051] S41, adding a new record to the main table storing device information of the IoT device according to the IP address, device type, manufacturer, hardware features, and software features of the IoT device;

[0052] S42, the storage node allocates a storage location for the attacked digital evidence of the IoT device, and adds a new record to the slave table of the storage location of the digital evidence.

[0053] Also includes:

[0054] S51, the storage node clusters the data type of the attacked digital evidence to obtain one or more clusters;

[0055] S52, in each cluster, calculate the similarity of all attacked digital evidences, merge the attacked digital evidences with similarity higher than a threshold and retain only one copy; the attacked digital evidences that are not retained can be moved to the storage node specified by the distributed storage system.

[0056] S53, updating the storage location of the merged attacked digital evidence in the slave table, and adding a merge mark to the record in the slave table.

[0057] By adding the merge tag, the system administrator or network security engineer can query the merged attacked digital evidence through the merge tag when needed, and review the merged attacked digital evidence. For the attacked digital evidence that should not be merged, the merge operation can be undone and the attacked digital evidence can be restored to the original storage node, avoiding serious losses caused by incorrect merging.

[0058] The present invention also proposes an IoT attack data storage device based on a distributed storage system, characterized in that the distributed storage system includes at least one database and multiple storage nodes, including:

[0059] The distributed storage system receives the collected device information of the IoT device and the digital evidence of the attack, wherein the device attributes in the device information include the IP address, device type, manufacturer, hardware features and software features of the IoT device; the data type of the digital evidence of the attack includes one or more of log files, network traffic data, system configuration and status information, malware samples, intrusion traces, abnormal behavior patterns and physical evidence;

[0060] A query module, used to query whether a record of the IoT device already exists in a database according to the IP address and device type of the IoT device, wherein the database includes a main table storing device information of the IoT device and a sub-table storing a storage location of the attacked digital evidence;

[0061] If a record of the IoT device already exists, query the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and store the collected attacked digital evidence of the IoT device in the storage location;

[0062] If there is no record of the IoT device, a new record is added to the main table storing the device information of the IoT device and the slave table storing the storage location of the attacked digital evidence according to the IP address and device type of the IoT device.

[0063] The present invention also proposes an IoT attack data storage device based on a distributed storage system, comprising a processor and a memory, wherein the memory stores computer program code, and is characterized in that the steps of the method described are implemented when the computer program code is executed by the processor.

[0064] The present invention also provides a computer-readable storage medium having computer program code stored thereon, characterized in that the steps of the method described are implemented when the computer program code is executed.

[0065] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation modes, which are merely illustrative rather than restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.

Claims

1. A method for storing IoT attack data based on a distributed storage system, characterized in that: The distributed storage system includes at least one database and multiple storage nodes, and includes the following steps: S1, the distributed storage system receives the collected device information of the IoT device and the digital evidence of the attack, wherein the device attributes in the device information include the IP address, device type, manufacturer, hardware features and software features of the IoT device; the data type of the digital evidence of the attack includes one or more of log files, network traffic data, system configuration and status information, malware samples, intrusion traces, abnormal behavior patterns and physical evidence; S2, according to the IP address and device type of the IoT device, query whether a record of the IoT device already exists in the database, wherein the database includes a main table storing device information of the IoT device and a secondary table storing the storage location of the attacked digital evidence; S3, if there is a record of the IoT device, query the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and store the collected attacked digital evidence of the IoT device in the storage location; S4, if there is no record of the IoT device, then according to the IP address and device type of the IoT device, add a new record to the main table storing the device information of the IoT device and the secondary table storing the storage location of the attacked digital evidence; The fields of the main table include device ID, IP address of IoT device, device type, manufacturer, hardware features, and software features; The fields of the slave table include device ID, data type and storage location of the attacked digital evidence; If there is no record of the IoT device in S4, then according to the IP address and device type of the IoT device, a new record is added to the main table storing the device information of the IoT device and the sub-table storing the storage location of the attacked digital evidence, specifically including: S41, adding a new record to the main table storing device information of the IoT device according to the IP address, device type, manufacturer, hardware features, and software features of the IoT device; S42, the storage node allocates a storage location for the attacked digital evidence of the IoT device, and adds a new record to the slave table of the storage location of the digital evidence.

2. The method according to claim 1, characterized in that There are multiple IoT devices, and the hardware characteristics include one or more of the CPU model, memory size, and storage capacity of the IoT devices.

3. The method according to claim 2, characterized in that The software features include one or more of the operating system type and version of the IoT device and installed applications.

4. The method according to claim 1, characterized in that The S2 queries whether a record of the IoT device already exists in the database according to the IP address and device type of the IoT device, wherein the database includes a main table storing device information of the IoT device and a sub-table storing the storage location of the attacked digital evidence, specifically including: S21, constructing a master table for storing device information of IoT devices and a slave table for storing storage locations of attacked digital evidence; S22, querying whether a record of the IoT device already exists in the database according to the IP address and device type of the IoT device, and recording the query in the system log.

5. The method according to claim 1, characterized in that If the record of the IoT device already exists, the S3 queries the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and stores the collected attacked digital evidence of the IoT device in the storage location, specifically including: S31, if there is already a record of the IoT device, continue to compare the manufacturer, hardware features and software features of the IoT device with the existing record of the IoT device to see if they are the same; if they are the same, query the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and store the collected attacked digital evidence of the IoT device in the storage location; S32: If different, go to step S4.

6. The method according to claim 1, characterized in that Also includes: S51, the storage node clusters the data type of the attacked digital evidence to obtain one or more clusters; S52, in each cluster, calculating the similarity of all attacked digital evidences, merging the attacked digital evidences with similarity higher than a threshold and retaining only one copy; S53, updating the storage location of the merged attacked digital evidence in the slave table, and adding a merge mark to the record in the slave table.

7. An IoT attack data storage device based on a distributed storage system, characterized in that: The distributed storage system includes at least one database and multiple storage nodes, including: The distributed storage system receives the collected device information of the IoT device and the digital evidence of the attack, wherein the device attributes in the device information include the IP address, device type, manufacturer, hardware features and software features of the IoT device; the data type of the digital evidence of the attack includes one or more of log files, network traffic data, system configuration and status information, malware samples, intrusion traces, abnormal behavior patterns and physical evidence; A query module, used to query whether a record of the IoT device already exists in a database according to the IP address and device type of the IoT device, wherein the database includes a main table storing device information of the IoT device and a sub-table storing a storage location of the attacked digital evidence; If a record of the IoT device already exists, query the storage location of the attacked digital evidence corresponding to the existing record of the IoT device, and store the collected attacked digital evidence of the IoT device in the storage location; If there is no record of the IoT device, then add a new record to the main table storing the device information of the IoT device and the secondary table storing the storage location of the attacked digital evidence according to the IP address and device type of the IoT device; The fields of the main table include device ID, IP address of IoT device, device type, manufacturer, hardware features, and software features; The fields of the slave table include device ID, data type and storage location of the attacked digital evidence; If there is no record of the IoT device, then according to the IP address and device type of the IoT device, a new record is added to the main table storing the device information of the IoT device and the secondary table storing the storage location of the attacked digital evidence, specifically including: Add a new record to the main table storing device information of the IoT device based on the IP address, device type, manufacturer, hardware features, and software features of the IoT device; The storage node allocates a storage location for the attacked digital evidence of the IoT device, and adds a new record to the slave table of the storage location of the digital evidence.

8. An IoT attack data storage device based on a distributed storage system, comprising a processor and a memory, wherein the memory stores computer program code, characterized in that: When the computer program code is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program code stored thereon, characterized in that: When the computer program code is executed, the steps of the method according to any one of claims 1 to 6 are implemented.