A method, system and storage medium for secure transmission of asset data

Abstract

The present application relates to a method, system and storage medium for secure transmission of asset data, which belongs to the field of data transmission. The method includes obtaining asset data transmitted from an output node to a receiving node; encrypting the asset data based on a preset encryption algorithm to obtain ciphertext; assigning permissions to the receiving node; the permissions include read-only permissions and read-write permissions; if the permissions of the receiving node are read-write permissions, decrypting the ciphertext based on a preset decryption algorithm to obtain the asset data, and sending the asset data to the receiving node. The security of asset data during data transmission is effectively guaranteed by encryption, thereby reducing the risk of asset data being intercepted and leaked during data transmission; in addition, the central control host effectively guarantees the secure transmission of asset data by assigning permissions to the receiving node after encryption.

Description

Technical Field

[0001] The present application relates to the field of data transmission, and in particular to a method, system and storage medium for secure transmission of asset data. Background Art

[0002] Data assets refer to data resources that can bring future economic benefits to enterprises, including text, images, and documents. Enterprises can use data assets to provide better products and services while reducing costs and controlling risks.

[0003] Currently, the way data assets are transmitted in an enterprise is that security testers first export the collected data assets to files, and then the security testers transfer the files to other people through third-party software.

[0004] The inventors believe that, since data assets are important data resources in an enterprise, if security testers transfer data assets to the wrong person due to mistakes made by security testers, data asset leakage may occur. Summary of the invention

[0005] In order to effectively ensure the secure transmission of asset data, the present application provides an asset data secure transmission method, system and storage medium.

[0006] In the first aspect, the present application provides a method for securely transmitting asset data using the following technical solutions:

[0007] A method for securely transmitting asset data, comprising:

[0008] Obtain asset data transmitted from the output node to the receiving node;

[0009] Encrypt asset data based on a preset encryption algorithm to obtain ciphertext;

[0010] Allocating permissions to the receiving node; the permissions include read-only permissions and read-write permissions;

[0011] If the authority of the receiving node is read-write authority, the ciphertext is decrypted based on a preset decryption algorithm to obtain the asset data, and the asset data is sent to the receiving node.

[0012] By adopting the above technical solution, when the output node transmits asset data to the receiving node, the central control host first obtains the asset data and encrypts the asset data, which effectively ensures the security of the asset data during data transmission, thereby reducing the risk of asset data being intercepted and leaked during the data transmission process; in addition, the central control host effectively ensures the secure transmission of asset data by assigning permissions to the receiving node after encryption.

[0013] Optionally, the method further includes:

[0014] If the permission of the receiving node is read-only permission, obtain the port number of the receiving node;

[0015] Determine whether the port number is stored in a preset port authority information database;

[0016] If the port number is stored in the port authority information database, verifying the authority level of the output node;

[0017] Based on the permission level, the data transmission action is performed; the data transmission action includes sending the asset data and sending ciphertext.

[0018] By adopting the above technical solution, when the target node does not include the receiving node, the data transmission action to be performed is determined according to the authority level of the output node, thereby reducing the probability of system misjudgment. By verifying the authority level of the output node to determine whether to send asset data to the receiving node, it is beneficial to further reduce the probability of transmission errors by security testers.

[0019] Optionally, the permission level includes an important permission level and a general permission level;

[0020] The performing the data transmission action based on the permission level includes:

[0021] If the authority level is an important authority level, sending the asset data to the receiving node;

[0022] If the authority level is a normal authority level, the ciphertext is sent to the receiving node.

[0023] By adopting the above technical solution, when the authority level is the important authority level, it indicates that the asset data has been marked as safe by the security tester. At this time, the central control host sends the asset data to the receiving node; when the authority level is the ordinary authority level, the central control host sends the ciphertext to the receiving node, thereby effectively ensuring the security of the asset data after it is transmitted to the receiving node.

[0024] Optionally, after sending the ciphertext to the receiving node, the method further includes:

[0025] After receiving the decryption request signal sent by the receiving node, sending decryption confirmation information to the output node;

[0026] After obtaining the confirmation signal of the output node, the ciphertext is decrypted based on the decryption algorithm to obtain the asset data.

[0027] By adopting the above technical solution, when the authority level is the normal authority level, the receiving node needs to request decryption after receiving the ciphertext. At this time, the receiving node can only read and write asset data after confirmation by the output node, which effectively ensures the secure transmission of asset data.

[0028] Optionally, the allocating authority to the receiving node includes:

[0029] The preset receiving authority of the asset data is obtained, and authority is allocated to the receiving node based on the receiving authority.

[0030] By adopting the above technical solution, the receiving authority refers to the preset read and write authority of the output node to the receiving node. By allocating authority to the receiving node by the output node, the receiving node performs read and write operations on the asset data based on the receiving authority, which is conducive to the secure transmission of asset data.

[0031] Optionally, the allocating authority to the receiving node further includes:

[0032] Based on a preset authority allocation model, assigning authority to the receiving node;

[0033] The authority allocation model includes:

[0034] Based on a preset historical database, obtaining all historical data received by the receiving node port;

[0035] Processing the historical data based on a preset big data algorithm to obtain high-frequency data;

[0036] Calculating the similarity probability between the asset data and the high-frequency data based on a preset similarity algorithm;

[0037] assigning authority to the receiving node based on the similarity probability;

[0038] The allocating authority to the receiving node based on the authority allocation model includes:

[0039] If the similarity probability is greater than a preset probability threshold, read-write permissions are allocated to the receiving node; if the similarity probability is not greater than the probability threshold, read-only permissions are allocated to the receiving node.

[0040] By adopting the above technical solution, the authority allocation model is used to allocate authority to the receiving node. By allocating authority to the receiving node, it is determined whether to transmit the asset data to the receiving node, thereby effectively ensuring the secure transmission of the asset data.

[0041] Optionally, before acquiring all historical data received by the receiving node port based on a preset historical database, the method includes:

[0042] Determine whether the port of the receiving node has received historical data;

[0043] If no historical data has been received, the asset data is stored, the asset data is locked, and a decryption password is randomly generated;

[0044] Sending verification information to the receiving node, and sending the decryption password to the output node;

[0045] If the receiving node uploads the correct decryption password, it is determined that the receiving node has passed the verification;

[0046] sending the asset data to the receiving node;

[0047] If historical data has been received, proceed to the next step.

[0048] By adopting the above technical solution, if the port of the receiving node has not received historical data, it is impossible to assign permissions to the receiving node. By sending verification information to the receiving node and sending a decryption password to the output node, the output node can determine whether the receiving node is the correct transmission object, thereby effectively ensuring the secure transmission of asset data.

[0049] Optionally, before the receiving node uploads the correct decryption password and determines that the receiving node passes the verification, the method includes:

[0050] Determine whether the number of password uploads by the receiving node is greater than a preset number threshold;

[0051] If it is greater than, set the read-only time;

[0052] When the receiving node receives the asset data for more than the read-only time, the asset data is deleted;

[0053] If not, proceed to the next step.

[0054] By adopting the above technical solution, if the number of times the receiving node uploads the password exceeds the threshold, the security of the asset data is effectively guaranteed by setting read-only permissions and read-only time for the receiving node.

[0055] In the second aspect, the asset data security transmission system provided by the present application adopts the following technical solution:

[0056] A system for secure transmission of asset data comprises a memory and a processor, wherein the memory stores a program for secure transmission of asset data, and the processor is used to adopt the above-mentioned method for secure transmission of asset data when executing the program.

[0057] By adopting the above technical solution, the above asset data secure transmission method is generated into a computer program and stored in a memory so as to be loaded and executed by a processor. Thus, a terminal device is manufactured based on the memory and the processor for easy use.

[0058] In a third aspect, a storage medium provided by the present application adopts the following technical solution:

[0059] A storage medium stores a computer program that can be loaded by a processor and execute the above-mentioned asset data secure transmission method.

[0060] By adopting the above technical solution, the above asset data secure transmission method is generated into a computer program and stored in a computer-readable storage medium so as to be loaded and executed by a processor. The computer-readable storage medium facilitates the reading and storage of the computer program.

[0061] In summary, the present application has at least one of the following beneficial technical effects:

[0062] 1. The central control host assigns permissions to the receiving nodes through the permission allocation model, effectively ensuring that the output nodes are transmitted to the correct receiving nodes, thereby effectively ensuring the secure transmission of asset data.

[0063] 2. If the port of the receiving node has not received historical data, it is impossible to assign permissions to the receiving node. By sending verification information to the receiving node and sending the decryption password to the output node, the output node can determine whether the receiving node is the correct transmission object, thereby effectively ensuring the safe transmission of asset data.

[0064] 3. By verifying the authority level of the output node, determining whether to send asset data to the receiving node can help further reduce the probability of transmission errors by security testers. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 It is an overall flow chart of a method for securely transmitting asset data according to an embodiment of the present application.

[0066] Figure 2 It is a flow chart of a permission allocation model in a method for secure transmission of asset data in an embodiment of the present application.

[0067] Figure 3 This is a flowchart before obtaining all historical data received by a receiving node port based on a preset historical database in a method for secure transmission of asset data in an embodiment of the present application. DETAILED DESCRIPTION

[0068] The embodiment of the present application discloses a method for securely transmitting asset data.

[0069] Reference Figure 1 , a method for securely transmitting asset data includes:

[0070] S100. Obtain asset data transmitted from the output node to the receiving node.

[0071] In this embodiment, the asset data includes documents, texts, pictures, etc. Both the output node and the receiving node can be smart terminals, web pages, or apps. Specifically, the smart terminal can be a mobile phone, a computer, or a tablet.

[0072] In specific implementation, when asset data is transmitted, encrypted transmission protocols such as the HTTPS protocol ensure the encrypted transmission of asset data, that is, the asset data is encrypted during transmission from the output node to the central control host.

[0073] It should be noted that, compared to the existing method of mutual transmission of asset data through third-party software, in this embodiment, a central control host controls the transmission of asset data, thereby eliminating the need for third-party software for data transmission transfer, further effectively improving the security of asset data transmission. In this embodiment, the central control host is the server. One of the servers corresponds to multiple clients, which can be PC, mobile or web, and data sharing between clients is indirectly shared through the server.

[0074] S200: Encrypt the asset data based on a preset encryption algorithm to obtain a ciphertext.

[0075] In this embodiment, different encryption algorithms are used for different types of asset data. If the asset data is an image, the encryption algorithm uses a color image chaos encryption algorithm. The color image chaos encryption algorithm uses three variables of different dimensions in the Lorenz system to generate a scrambling matrix to scramble and encrypt the three parts of the RGB color image respectively, thereby encrypting the entire color image file. The Lorenz system is a Lorenz chaotic system. A chaotic system refers to a deterministic system with seemingly random irregular motions, and its behavior is uncertain, non-repeatable, and unpredictable.

[0076] If the asset data is text or numbers, the encryption algorithm uses the DES encryption algorithm. The DES encryption algorithm is a symmetric encryption algorithm. The DES encryption algorithm uses a specified key to intercept data according to the length of the password, divide it into data blocks, and perform complex shifting, arithmetic operations or data processing operations with the key to form an algorithm that can only decrypt data with a specific password.

[0077] If the asset data is in English letters, the Caesar encryption algorithm or the Playfair encryption algorithm is used to encrypt the asset data. The Caesar encryption algorithm refers to replacing each English letter in the original string with the next k-th letter in its alphabet. The Playfair encryption algorithm refers to an algorithm that uses a keyword grid to encrypt character pairs, that is, taking the double letters in the plaintext as a unit, converting them into double letters in the ciphertext, and using the 5×5 letter matrix formed by the key as the basis for conversion.

[0078] It should be noted that encryption of asset data continues throughout the entire asset data transmission process.

[0079] Allocating authority to the receiving node. In the first embodiment, allocating authority to the receiving node includes:

[0080] Get the preset receiving permissions for asset data and assign permissions to receiving nodes based on the receiving permissions. Permissions include read-write permissions and read-only permissions.

[0081] Receiving permissions refer to the preset read and write permissions of the output node to the receiving node. By allocating permissions from the output node to the receiving node, the receiving node performs read and write operations on the asset data based on the receiving permissions, which is conducive to the secure transmission of asset data.

[0082] Assigning permissions to the receiving node. In the second embodiment, S300, assigning permissions to the receiving node based on a preset permission assignment model; the permissions include read-write permissions and read-only permissions.

[0083] The permission allocation model is used to allocate permissions to receiving nodes.

[0084] Reference Figure 2 , the permission allocation model includes:

[0085] S310 . Based on a preset historical database, obtain all historical data received by the receiving node port.

[0086] In a specific implementation, the central control host obtains all historical data received by the port by monitoring the port.

[0087] Reference Figure 3 , before obtaining all historical data received by the receiving node port based on the preset historical database, including:

[0088] S311. Determine whether the port of the receiving node has received historical data.

[0089] If the receiving node is a new node, it may not have received historical data. In this case, the central control host cannot obtain the historical data received by the port of the receiving node.

[0090] S312: If no historical data has been received, the asset data is stored, the asset data is locked, and a decryption password is randomly generated.

[0091] If the receiving node has not received historical data, it indicates that the receiving node is a new node. At this time, the central control host stores the asset data, does not send the asset data to the receiving node for the time being, and randomly generates a decryption password for encrypting the asset data.

[0092] S313, sending the verification information to the receiving node, and sending the decryption password to the output node.

[0093] The verification information is used to verify whether the receiving node is the correct receiving node. Specifically, the receiving node needs to enter the correct decryption password to obtain the asset data after receiving the verification information. The central control host sends the decryption password to the output node. At this time, the output node needs to reconfirm the correctness of the receiving node. If the output node verifies the correctness of the receiving node, it will send the decryption password to the receiving node. At this time, the receiving node can obtain the asset data by entering the decryption password.

[0094] S314: If the receiving node uploads the correct decryption password, it is determined that the receiving node has passed the verification.

[0095] Specifically, if the receiving node uploads the correct decryption password, before determining that the receiving node has passed the verification, it includes:

[0096] S1. Determine whether the number of password uploads by the receiving node is greater than a preset number threshold.

[0097] Setting a threshold number of times is used to limit the number of times the receiving node inputs, preventing the receiving node from obtaining asset data due to accidentally entering the decryption password.

[0098] S2. If it is greater than, set the read-only time.

[0099] S3. When the receiving node receives asset data for more than the read-only time, the asset data is deleted.

[0100] S4. If not, execute step S314.

[0101] Take steps S1 to S4 as an example. If the threshold value is set to 5 times, and the receiving node has uploaded the password 6 times but still has not entered the correct decryption password, then 6 times is greater than 5 times. The central control host sets a read-only time, that is, the receiving node can read the asset data within the read-only time; if the receiving node enters the correct decryption password after uploading the password 5 times, the central control host determines that the receiving node has passed the verification and sends the asset data to the receiving node.

[0102] Reference Figure 3 , S315, sending the asset data to the receiving node.

[0103] S316: If historical data has been received, execute step S310.

[0104] If the receiving node has received historical data, permissions can be assigned to the receiving node based on the permission allocation model.

[0105] Reference Figure 2 , S320, the historical data is processed based on a preset big data algorithm to obtain high-frequency data.

[0106] The big data algorithm used in this embodiment is a big data algorithm based on the hash algorithm, which is used to extract high-frequency words. The specific process is as follows: read the asset data, perform hash calculations and determine the location where the data is stored to obtain the number of times all data appears, and finally establish an array for storing high-frequency data.

[0107] S330. Calculate the similarity probability between the asset data and the high-frequency data based on a preset similarity algorithm.

[0108] In this embodiment, the similarity algorithm uses the Tanimoto coefficient algorithm to calculate the similarity probability between asset data and high-frequency data. The Tanimoto coefficient is used to determine the similarity between two data and can be expressed as the ratio of the intersection of two sets to the union of the two sets.

[0109] S340: Allocate permissions to receiving nodes based on similarity probabilities.

[0110] If the similarity probability is greater than the probability threshold, the central control host determines that the receiving node is the correct receiving node, i.e., the target node, and assigns read and write permissions to the receiving node. At this time, the receiving node can receive the asset data sent by the central control host. If the similarity probability is not greater than the probability threshold, the central control host assigns read-only permissions to the receiving node, and the receiving node cannot receive asset data.

[0111] Since the high-frequency data obtained through the big data algorithm may be one or more groups, if the high-frequency data is multiple groups, then the similarity probability is multiple groups. At this time, there will be several groups of similarity probabilities greater than the probability threshold and several groups of similarity probabilities not greater than the probability threshold. At this time, the situation where the similarity probability is not greater than the probability threshold is not considered.

[0112] In a specific implementation, if the receiving node is a correct receiving node but has read-only permission, the permission of the receiving node can be changed through the output node so that the receiving node can receive asset data.

[0113] Based on the permission allocation model, permissions are allocated to the receiving nodes, including:

[0114] S350: If the similarity probability is greater than a preset probability threshold, assign read-write permissions to the receiving node; if the similarity probability is not greater than the probability threshold, assign read-only permissions to the receiving node.

[0115] Reference Figure 1 , S400, if the permission of the receiving node is read-write permission, decrypt the ciphertext based on a preset decryption algorithm to obtain the asset data, and send the asset data to the receiving node.

[0116] The central control host determines whether to decrypt the ciphertext by determining whether the receiving node is the target node. The decryption algorithm corresponds to the encryption algorithm of step S200. For example, when the encryption algorithm is the Caesar algorithm, the decryption algorithm is used to decrypt the Caesar algorithm.

[0117] S500: If the permission of the receiving node is read-only permission, obtain the port number of the receiving node.

[0118] If the permission of the receiving node is read-only permission, it means that it is impossible to confirm whether the receiving node is the correct receiving node at this time. At this time, the central control host obtains the port number.

[0119] S600: Determine whether a preset port authority information database stores a port number.

[0120] S700: If the port number is stored in the port authority information database, verify the authority level of the output node.

[0121] The port authority database stores several port numbers. If the port number is not in the authority information database, it indicates that the receiving node corresponding to the port number is an incorrect receiving node. At this time, the central control host does not take any action.

[0122] If the port number is located in the authority information database, the central control host verifies the authority level of the output node.

[0123] S800. Execute data transmission actions based on the permission level; the data transmission actions include sending asset data and sending ciphertext.

[0124] Specifically, the permission levels include important permission levels and ordinary permission levels;

[0125] Based on the permission level, perform data transfer actions, including:

[0126] S810. If the authority level is an important authority level, the asset data is sent to a receiving node.

[0127] The important authority level indicates that the output node has confirmed the receiving node and there is no need to confirm the receiving node again. At this time, the central control host sends the asset data to the receiving node.

[0128] It should be noted that if the authority level of the output node is the important authority level, and the authority of the receiving segment is read-only authority, the output node still needs to confirm before the asset data can be successfully transmitted to the receiving node.

[0129] S820: If the authority level is the normal authority level, send the ciphertext to the receiving node.

[0130] When the authority level is the normal authority level, the central control host sends the ciphertext to the receiving node, thereby effectively ensuring the security of the asset data after it is transmitted to the receiving node.

[0131] After sending the ciphertext to the receiving node, it includes:

[0132] S821. After receiving the decryption request signal sent by the receiving node, send decryption confirmation information to the output node.

[0133] S822. After obtaining the confirmation signal from the output node, decrypt the ciphertext based on the decryption algorithm to obtain the asset data.

[0134] When the permission level is the normal permission level, the receiving node needs to request decryption after receiving the ciphertext. At this time, the receiving node needs to confirm before it can read and write asset data, which effectively ensures the secure transmission of asset data.

[0135] In the asset data secure transmission method of this embodiment, the operations that the output node and the receiving node can perform are not limited to the following:

[0136] Team management functions, including the functions of creating new teams, inviting people, deleting people from a team, and managing the permissions of people in a team, such as whether a new team can be created or whether people can be invited to join a team;

[0137] Team members can manage folders and files within the team, including creating, copying and moving files, online browsing, editing in multiple file formats, evaluating files, uploading and downloading files, file synchronization, and managing permissions on files or folders, such as whether team members have the permission to edit and read files, and viewing file properties, such as viewing the file creator, file creation time, and modification time.

[0138] Chat function between team members, including text, picture and file transmission function, history record export and backup function, etc.;

[0139] Message notification function, including notification of team members receiving chat messages, notification of new team members joining the team, file modification notification, file evaluation notification, etc.;

[0140] Security functions include permission management for team members, permission management for asset data files, saving file editing history, safe file deletion, asset data file encryption, etc. The function of saving file editing history is used to prevent asset data files from being accidentally modified by team members, and the function of safe file deletion is used to prevent asset data files from being repaired by data repair tools.

[0141] Both output nodes and receiving nodes can use accounts that can transfer asset data as team members. Specific output nodes and receiving nodes can form teams by establishing groups, etc.

[0142] Compared with the existing asset data transmission method, that is, the asset data transmission method through third-party software, this embodiment can synchronize and collaboratively process asset data under the condition of secure transmission of asset data, which is more convenient for asset data management and is conducive to improving team work efficiency.

[0143] The implementation principle of a method for secure transmission of asset data in an embodiment of the present application is as follows: when an output node transmits asset data to a receiving node, the central control host first obtains the asset data and encrypts the asset data, effectively ensuring the security of the asset data during data transmission, thereby reducing the risk of asset data being intercepted and leaked during data transmission; in addition, the central control host determines the target node through a permission allocation model, that is, only the target node can receive asset data, effectively ensuring that the output node is transmitted to the correct receiving node, thereby effectively ensuring the secure transmission of asset data.

[0144] The embodiment of the present application also discloses a system for secure transmission of asset data.

[0145] A system for secure transmission of asset data includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, wherein when the processor executes the computer program, the method for secure transmission of asset data in the above embodiment is adopted.

[0146] Among them, the asset data security transmission system can use computer devices such as desktop computers, laptops or cloud servers, and the asset data security transmission system includes but is not limited to processors and memories. For example, the asset data security transmission system can also include input and output devices, network access devices and buses, etc.

[0147] Among them, the processor can adopt a central processing unit (CPU). Of course, according to actual usage, other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. can also be adopted. The general-purpose processor can adopt a microprocessor or any conventional processor, etc., and this application does not impose any restrictions on this.

[0148] Among them, the memory can be an internal storage unit of the terminal device, such as a hard disk or memory of the terminal device, or it can be an external storage device of the terminal device, such as a plug-in hard disk, a smart memory card (SMC), a secure digital card (SD) or a flash memory card (FC) equipped on the terminal device, and the memory can also be a combination of an internal storage unit and an external storage device of the terminal device. The memory is used to store computer programs and other programs and data required by the terminal device. The memory can also be used to temporarily store data that has been output or is to be output, and this application does not impose any restrictions on this.

[0149] Among them, through this asset data security transmission system, the asset data security transmission method in the above embodiment is stored in the memory of the asset data security transmission system, and is loaded and executed on the processor of the asset data security transmission system for easy use.

[0150] The embodiment of the present application further discloses a computer-readable storage medium, and the computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the asset data secure transmission method in the above embodiment is adopted.

[0151] Among them, the computer program can be stored in a computer-readable medium, the computer program includes computer program code, the computer program code can be in the form of source code, object code, executable file or certain middleware, etc. The computer-readable medium includes any entity or device that can carry the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the computer-readable medium includes but is not limited to the above-mentioned components.

[0152] Among them, through this computer-readable storage medium, the asset data secure transmission method in the above embodiment is stored in the computer-readable storage medium, and is loaded and executed on the processor to facilitate the storage and application of the above method.

[0153] The above are all preferred embodiments of the present application, and the protection scope of the present application is not limited thereto. Therefore, any equivalent changes made according to the structure, shape, and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method for secure transmission of asset data, characterized in that: include: Obtain asset data transmitted from the output node to the receiving node; Encrypt asset data based on a preset encryption algorithm to obtain ciphertext; Allocating authority to the receiving node; The permissions include read-only permissions and read-write permissions; If the permission of the receiving node is read-write permission, the ciphertext is decrypted based on a preset decryption algorithm to obtain the asset data, and the asset data is sent to the receiving node; The allocating authority to the receiving node further includes: Based on a preset authority allocation model, assigning authority to the receiving node; The authority allocation model includes: Based on a preset historical database, obtaining all historical data received by the receiving node port; Processing the historical data based on a preset big data algorithm to obtain high-frequency data; Calculating the similarity probability between the asset data and the high-frequency data based on a preset similarity algorithm; assigning authority to the receiving node based on the similarity probability; The allocating authority to the receiving node based on the authority allocation model includes: If the similarity probability is greater than a preset probability threshold, read-write permissions are allocated to the receiving node; if the similarity probability is not greater than the probability threshold, read-only permissions are allocated to the receiving node.

2. A method for securely transmitting asset data according to claim 1, characterized in that: The method further comprises: If the permission of the receiving node is read-only permission, obtain the port number of the receiving node; Determine whether the port number is stored in a preset port authority information database; If the port number is stored in the port authority information database, verifying the authority level of the output node; Based on the permission level, the data transmission action is performed; the data transmission action includes sending the asset data and sending ciphertext.

3. A method for securely transmitting asset data according to claim 2, characterized in that: The authority level includes an important authority level and a general authority level; The performing the data transmission action based on the permission level includes: If the authority level is an important authority level, sending the asset data to the receiving node; If the authority level is a normal authority level, the ciphertext is sent to the receiving node.

4. A method for securely transmitting asset data according to claim 3, characterized in that: After sending the ciphertext to the receiving node, the method further comprises: After receiving the decryption request signal sent by the receiving node, sending decryption confirmation information to the output node; After obtaining the confirmation signal of the output node, the ciphertext is decrypted based on the decryption algorithm to obtain the asset data.

5. The method for securely transmitting asset data according to claim 1, characterized in that: The allocating authority to the receiving node includes: The preset receiving authority of the asset data is obtained, and authority is allocated to the receiving node based on the receiving authority.

6. The method for securely transmitting asset data according to claim 1, characterized in that: Before acquiring all historical data received by the receiving node port based on the preset historical database, the method includes: Determine whether the port of the receiving node has received historical data; If no historical data has been received, the asset data is stored, the asset data is locked, and a decryption password is randomly generated; Sending verification information to the receiving node, and sending the decryption password to the output node; If the receiving node uploads the correct decryption password, it is determined that the receiving node has passed the verification; sending the asset data to the receiving node; If historical data has been received, proceed to the next step.

7. A method for securely transmitting asset data according to claim 6, characterized in that: If the receiving node uploads the correct decryption password, before determining that the receiving node has passed the verification, the method includes: Determine whether the number of password uploads by the receiving node is greater than a preset number threshold; If it is greater than, set the read-only time; When the receiving node receives the asset data for more than the read-only time, the asset data is deleted; If not, proceed to the next step.

8. An asset data security transmission system, characterized by: The invention comprises a memory and a processor, wherein the memory stores a program for securely transmitting asset data, and the processor is used for adopting any one of the methods of claims 1 to 7 when executing the program.

9. A storage medium, characterized in that: A computer program is stored which can be loaded by a processor and executes the method according to any one of claims 1 to 7.

Images