A method for destroying encrypted data

Abstract

The present invention relates to the technical field of encrypted data processing, and in particular to a method for destroying encrypted data, comprising: dividing user data, and setting corresponding retained information stamps in each divided user data, each retained information stamp sending retained information at a preset period; determining a corresponding check code according to the retained information, and setting a number of check information stamps in the check code for sending check information at a preset period; making a password correspond to the check code, each check information stamp sending check information in response to the password; the retained information stamp sending corresponding retained information in response to the corresponding check information; and storing data by setting a retained data signal for periodic sending, and deleting the data corresponding to the signal when no response is generated, thereby effectively improving the responsiveness of deleting data and effectively avoiding the behavior of reading data from the outside, thereby effectively improving the timeliness of deleting sensitive data.

Description

Technical Field

[0001] The present invention relates to the technical field of encrypted data processing, and in particular to a method for destroying encrypted data. Background Art

[0002] In the era of digital economy, with the widespread application of technologies such as the Internet of Things, blockchain, and cloud computing, the role of data has become increasingly prominent and has become a vital element in social life. The vast majority of data is generated during user use. Users' personal sensitive information is authorized to personal information processors, such as websites or apps. During the collection and analysis process, third parties may also be required to participate in personal information processing. There is a risk of personal information and privacy being leaked throughout the process. The state has promulgated laws and regulations such as the "Data Security Law" and the "Personal Information Protection Law" to regulate data processing activities, requiring necessary measures to ensure data security, including encrypted storage of data, and requiring sensitive data to be destroyed or anonymized after the life cycle is completed.

[0003] In practice, sensitive data of the same customer may be stored in multiple storage locations (databases, file storage, backups, etc.), or in the systems of multiple parties involved in the processing process. When the customer terminates the service or explicitly requests the service provider to delete personal information, all data should be deleted or anonymized in accordance with regulatory requirements. The traditional approach requires traversing all data storage locations and operation links to find and delete or anonymize all personal information involved. The operation process is very cumbersome and it is likely that some data will be deleted in a timely manner or omitted. The cost is high, the possibility of error is high, and there are compliance risks.

[0004] Chinese Patent Authorization Announcement No.: CN116561809B discloses a method for destroying confidential media based on point cloud identification, which relates to the field of image data processing technology; the destruction method mainly includes: collecting confidential media feature data and converting the collection results into point cloud data and preprocessing; using point cloud processing algorithms to extract attribute features in point cloud data, and judging whether the confidential media contains sensitive information based on the attribute features; encrypting and marking the confidential media containing sensitive information; physically destroying the confidential media; judging whether the confidential media fragments contain complete sensitive information, and if so, further destroying the confidential media fragments. The technical solution of this invention first judges whether the confidential media contains sensitive information before destruction, marks the confidential media part containing sensitive information to focus on, and encrypts the corresponding confidential media. While ensuring the security of confidential media information, the efficiency of the destruction process is improved.

[0005] Chinese Patent Authorization Announcement No.: CN116521661B discloses a user data destruction method, device, electronic device and computer-readable medium. A specific implementation of the method includes: dividing data sending information corresponding to the same data type into the same data sending information group to obtain a first data sending information group set; for each first data sending information group: determining the data processing channel information of the corresponding data type to obtain each user data group of the corresponding data type as a first user data group set; performing block query processing on each first data sending information in the first data sending information group to obtain a sending user data group set; for each sending user data group, in response to determining that the corresponding first data sending information meets the preset data destruction condition, destroying the sending user data group stored in the user data application end. This implementation improves the processing efficiency of data sending information when destroying user data and reduces the congestion of data sending information.

[0006] However, the above method has the following problems:

[0007] When dealing with large volumes of data, it is difficult to effectively prevent the data from being transmitted, which results in an inability to quickly delete sensitive data. Summary of the invention

[0008] To this end, the present invention provides a method for destroying encrypted data to overcome the problem in the prior art that it is difficult to effectively and quickly delete data when facing large data or distributed stored data, resulting in the leakage of sensitive data.

[0009] To achieve the above object, the present invention provides a method for destroying encrypted data, comprising:

[0010] Segment the user data, and set a corresponding retention information stamp in each segmented user data, each retention information stamp sends retention information at a preset period;

[0011] Determine a corresponding check code according to the retained information, and set a number of check information stamps for sending check information according to the preset period in the check code;

[0012] The password is matched with the verification code, and each verification information stamp responds to the password and sends the verification information;

[0013] The retained information stamp responds to the corresponding verification information and sends the corresponding retained information;

[0014] In response to the stop of verification information, the corresponding verification information stamp is formatted;

[0015] In response to the stop message of the retained information, the corresponding user data is formatted.

[0016] Furthermore, the process of setting up encrypted data includes:

[0017] Respond to data storage requests and store corresponding user data;

[0018] Compiling the user data to form a corresponding verification code;

[0019] Segmenting the user data and forming a plurality of segmented data marked by check codes;

[0020] storing the segmented data respectively, and setting the verification code as a reading key of the corresponding segmented data;

[0021] splitting the verification code and inserting the password into a corresponding read key basis to form a read key;

[0022] The user data, the verification code and the read key are stored separately.

[0023] Further, when the verification information stamp reads the secret key, it responds to the password corresponding to the verification information stamp and releases the verification code corresponding to the read secret key and the corresponding verification information;

[0024] The information stamp is retained to respond to the verification information, and according to the verification code corresponding to the verification information, the segmented data corresponding to the verification code is released.

[0025] Furthermore, the step of segmenting the user data includes:

[0026] Generate a check code corresponding to the user data;

[0027] Set up several storage spaces with the same space;

[0028] Divide the user data equally according to the amount of storage space to form segmented data, and divide the check code equally to form a segmented check code;

[0029] The segmentation data and the segmentation verification code are stored in corresponding storage spaces.

[0030] Furthermore, the process of setting the verification code as a reading key of the corresponding segmented data includes:

[0031] Setting the check code at the front of the segmented data;

[0032] generating a read initiator corresponding to the check code;

[0033] Set the initiator to read the corresponding segmented data when the initiator reads the checksum completely.

[0034] Furthermore, the process of formatting the corresponding verification information stamp also includes:

[0035] Inserting random characters at random positions in the verification information stamp to form a garbled information stamp;

[0036] Wherein, when the preset period is reached, if the garbled information stamp is formed in any verification code, the verification information corresponding to the verification code stops being reported.

[0037] Furthermore, the process of formatting the corresponding user data also includes:

[0038] Inserting the deletion code into the front end of the user data and forming a plurality of busy codes corresponding to the user data;

[0039] In response to the erasure code and each busy code, identifying the space occupied by the user data as busy empty data;

[0040] The space occupied by the busy empty data is formatted sequentially in the next preset cycle.

[0041] Further, when forming the busy space data, it is set accordingly according to the storage mode of the user data;

[0042] Wherein, if the user data includes a directory, the busy space data occupies the corresponding directory;

[0043] If the user data includes a disk, the busy space data occupies the corresponding disk space.

[0044] Furthermore, the destruction method of the present application also includes:

[0045] When reading the user data, the integrity of the check code is verified, and check code complete information or check code missing information is formed;

[0046] In response to the complete information of the verification code, a data retention instruction is sent and the next preset cycle is entered;

[0047] In response to the verification code missing information, a data deletion instruction is sent;

[0048] In response to the data deletion instruction, the sending of the verification information and the retained information is stopped.

[0049] Furthermore, the data destruction method also includes a relief mechanism, including:

[0050] Setting preset relief periods;

[0051] The data destruction method stops running within a preset relief period.

[0052] Compared with the prior art, the beneficial effect of the present invention lies in that a periodically transmitted retention data signal is set to preserve data, and when no response is generated, the data corresponding to the transmitted signal is deleted. While effectively improving the responsiveness of deleting data, it effectively avoids the behavior of reading data from the outside, thereby effectively improving the timeliness of deleting sensitive data.

[0053] Furthermore, by setting up several levels of storage, user data, verification information and passwords are stored separately, and corresponding mapping relationships are set in each level. While effectively improving data security, the independent relationships between the levels are used to verify each other, which effectively improves the robustness of the data destruction process and improves data security. At the same time, the response chain for deleting data is reduced, thereby further improving the timeliness of deleting sensitive data.

[0054] Furthermore, by inserting a meaningless character into user data, verification information or password, the integrity of the data is destroyed, which effectively prevents the data from being intercepted and read, and effectively improves the data deletion rate, thereby further improving the timeliness of sensitive data deletion.

[0055] The core point of the present invention is to manage the key and ensure that the sensitive data cannot be restored after the key is destroyed, so as to achieve the purpose of data anonymization and meet the compliance requirements. The deletion action is fast, the workload is small, and the processing difficulty is small. And it can ensure that the relevant data is immediately and comprehensively processed in a protective manner.

[0056] Taking the AES algorithm as an example, AES-256 provides the highest security. First, a random encryption key and salt value that meet the length and complexity requirements are generated for each user. The personal information processor (service provider) stores and manages the key and salt value in a unified manner. When storing user sensitive data, it is necessary to first obtain the user's corresponding key and salt value, encrypt the sensitive data, and then store it in the database.

[0057] When the user service cycle ends, the user's corresponding key and salt value are destroyed to achieve the purpose of anonymizing all sensitive data. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 A flow chart of the method for destroying encrypted data according to the present invention;

[0059] Figure 2 A flow chart for setting encrypted data for the present invention;

[0060] Figure 3 A flowchart of data segmentation of the present invention;

[0061] Figure 4A flowchart of user data deletion of the present invention;

[0062] Figure 5 It is a timing diagram of the process of an embodiment of the present invention. DETAILED DESCRIPTION

[0063] In order to make the objects and advantages of the present invention more clearly understood, the present invention is further described below in conjunction with embodiments; it should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0064] The preferred embodiments of the present invention are described below with reference to the accompanying drawings. It should be understood by those skilled in the art that these embodiments are only used to explain the technical principles of the present invention and are not intended to limit the protection scope of the present invention.

[0065] It should be noted that, in the description of the present invention, terms such as "up", "down", "left", "right", "inside" and "outside" indicating directions or positional relationships are based on the directions or positional relationships shown in the drawings. This is merely for the convenience of description and does not indicate or imply that the device or element must have a specific orientation, be constructed and operated in a specific orientation. Therefore, it cannot be understood as a limitation on the present invention.

[0066] In addition, it should be noted that in the description of the present invention, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For those skilled in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0067] In today's digital age, data security is a very important issue that cannot be ignored. In order to protect sensitive data from being maliciously stolen or tampered with, encryption algorithms were born. Encryption algorithms convert and process raw data into unreadable content to prevent unauthorized people from reading and understanding it, thereby ensuring the security and confidentiality of data.

[0068] Encryption algorithms can be divided into three categories: symmetric encryption algorithms, asymmetric encryption algorithms, and hash algorithms. Symmetric encryption algorithms refer to encryption algorithms that use the same key for encryption and decryption. Common symmetric encryption algorithms include DES (Data Encryption Standard), AES (Advanced Encryption Standard), 3DES (Triple Data Encryption Standard), etc. Asymmetric encryption is also called public key encryption, which uses a pair of keys: a public key for encryption and a private key for decryption. The public key can be distributed freely, allowing anyone to encrypt data, but only the private key holder can decrypt and access the original information. The main asymmetric encryption algorithms include RSA (Rivest-Shamir-Adleman) algorithm, ECC (Elliptic Curve Cryptography) algorithm, etc.; the hash algorithm is also called the secure hash algorithm, message digest algorithm, and hash algorithm. It is an algorithm that outputs input data of any length as fixed-length data. It can realize functions such as data signing and data integrity verification. The main hash algorithms include MD5 (Message Digest Algorithm 5) algorithm, SHA1 (Secure Hash Algorithm 1) algorithm, SHA2 (Secure Hash Algorithm 2) algorithm, etc.

[0069] The national secret algorithm is a cryptographic algorithm standard issued by the State Cryptography Administration of China, which aims to ensure national information security. These algorithms include SM1, SM2, SM3, SM4, SM7, SM9 and Zu Chongzhi Cryptography Algorithm (ZUC), which are widely used in finance, e-government and security. Among them, SM1 is a symmetric encryption algorithm that uses the same key for encryption and decryption. It is mainly used for encryption protection of small amounts of data, such as smart IC cards and smart password keys. SM2 is an asymmetric encryption algorithm based on the ECC elliptic curve, including functions such as digital signatures, key exchange and public key encryption, and is suitable for e-commerce, Internet finance and other fields. SM3 is a hash algorithm used to generate message digests, while SM4 is a symmetric encryption algorithm used for packet data encryption of wireless LAN products.

[0070] The promotion of national cryptographic algorithms will help reduce reliance on external cryptographic products and improve the country's information security level. After years of development and improvement, these algorithms have become China's independently developed cryptographic algorithm standards and have been widely used in various industries. The security, efficiency, flexibility and standardization of national cryptographic algorithms have been recognized by the country and the industry.

[0071] The core point of the present invention is to manage the key and ensure that the sensitive data cannot be restored after the key is destroyed, so as to achieve the purpose of data anonymization and meet the compliance requirements. The deletion action is fast, the workload is small, and the processing difficulty is small. And it can ensure that the relevant data is immediately and comprehensively processed in a protective manner.

[0072] Taking the AES algorithm as an example, AES-256 provides the highest security. First, a random encryption key and salt value that meet the length and complexity requirements are generated for each user. The personal information processor (service provider) stores and manages the key and salt value in a unified manner. When storing user sensitive data, it is necessary to first obtain the user's corresponding key and salt value, encrypt the sensitive data, and then store it in the database.

[0073] When the user service cycle ends, the user's corresponding key and salt value are destroyed to achieve the purpose of anonymizing all sensitive data.

[0074] In practice, we can choose the applicable encryption algorithm and method according to the actual situation.

[0075] The specific processing flow is as follows:

[0076] 1. Choose key server storage or hardware device storage based on sensitivity and security level requirements.

[0077] 2. According to the data classification and grading requirements, select an encryption algorithm for user personal data. Personal sensitive data must use AES-256 or an encryption algorithm with encryption strength not less than this algorithm. For systems required by the state, a national encryption algorithm with corresponding strength should be selected.

[0078] 3. The encryption algorithm key and calculation offset (or salt value) are strictly managed and stored as encryption keys. The length and complexity of the key and salt value should meet the encryption level requirements.

[0079] 4. Based on the number of employers’ personal information processors, employers’ personal information sharers and employers’ personal information processor entrustors participating in the data processing process, the encryption key (and / or salt value) can be split into multiple parts as needed and kept separately by each party in the data processing chain.

[0080] 5. It may be considered that the personal data owner should keep part of the key and salt value.

[0081] 6. In normal personal information processing activities, the keys kept by all parties need to participate in the data encryption and decryption process.

[0082] 7. When a user stops the service or explicitly requests the service provider to clear personal information, all personal information processors involved in data processing need to delete the personal information involved in the system. By deleting the relevant key or salt value, it can be ensured that the encrypted data cannot be decrypted. It is assumed here that the encryption algorithm is strong enough and the data has met the anonymization requirements.

[0083] 8. In the case where multiple processors / sharers / delegators in the data processing link keep part of the key or salt value respectively, the destruction of the key part by any party may make the encrypted data unrecoverable, thereby achieving the purpose of anonymization and meeting compliance requirements.

[0084] 9. When the user keeps part of the key or salt value by himself, by deleting this part of the key, the encrypted data can be made unrecoverable, thus achieving personal data deletion and protection.

[0085] 10. When using hardware devices such as encryption chips or ukey hardware to store keys, the keys can be destroyed directly by securely overwriting the hardware memory, physically cleaning the chip storage, or directly physically destroying it.

[0086] According to the technology described in this application, the following requirements can be achieved:

[0087] High efficiency: Rapid data processing is achieved through centralized destruction of keys.

[0088] Integrity: Ensure that all sensitive data related to users can be anonymized.

[0089] Simple operation: Simplifies the operational process of data destruction and reduces operational complexity.

[0090] Low cost: Only one key needs to be processed to handle all affected personal information.

[0091] Comply with regulatory requirements: meet the relevant provisions of the Data Security Law and the Personal Information Protection Law.

[0092] See also Figure 1 As shown, it is a flow chart of the data destruction method of encrypted data of the present invention, including:

[0093] Step Ss1, dividing the user data, and setting a corresponding retained information stamp in each divided user data, each retained information stamp sends retained information at a preset period;

[0094] Step Ss2, determining the corresponding verification code according to the retained information, and setting a number of verification information stamps for sending verification information at a preset period in the verification code;

[0095] Step Ss3, matching the password with the verification code, and each verification information stamp responds to the password to send verification information;

[0096] Step Ss4, the retained information stamp responds to the corresponding verification information and sends the corresponding retained information;

[0097] Step Ss5, responding to the stop of verification information transmission, formatting the corresponding verification information stamp;

[0098] Step Ss6, in response to the stop of the message of the retained information, the corresponding user data is formatted.

[0099] In particular, the above steps may also be:

[0100] Step Ss3, matching the password with the verification code, and each verification information stamp responds to the password to send verification information;

[0101] Step Ss4, in response to the stop of the verification information, formatting the corresponding verification information stamp;

[0102] Step Ss5, the retained information stamp responds to the corresponding verification information and sends the corresponding retained information;

[0103] Step Ss6, in response to the stop of the message of the retained information, the corresponding user data is formatted.

[0104] It can be understood that in the above scheme, since the actions of verifying information and retaining information belong to different judgment paths, the sending of the verification information and the retention information can be performed simultaneously.

[0105] By setting a periodically transmitted retained data signal, the data is preserved. When no response is generated, the data corresponding to the signal is deleted. This effectively improves the responsiveness of deleting data and effectively avoids the behavior of reading data from the outside, thereby effectively improving the timeliness of deleting sensitive data.

[0106] In implementation, the preset period can be set arbitrarily, but should be aligned with the period of data call as much as possible, such as:

[0107] If certain data is called once a month, the preset period should be set to 1 month;

[0108] If a certain data is called 3 times a day, the preset period should be set to 1 day or 8 hours;

[0109] If a certain data is called for 1 day every 2 days, the preset period should be set to 3 days;

[0110] It should be understood that different preset periods should be set for different situations, and aligning the periods of the data call period is beneficial to protecting the security of user data.

[0111] See also Figure 2 As shown, it is a flow chart of setting encrypted data in the present invention, including:

[0112] Step Sj1, responding to a data storage request and storing corresponding user data;

[0113] Step Sj2, compile the user data to form a corresponding check code;

[0114] Step Sj3, dividing the user data into several divided data marked by check codes;

[0115] Step Sj4, storing the segmented data respectively, and setting the verification code as the reading key of the corresponding segmented data;

[0116] Step Sj5, split the check code and insert the password into the corresponding read key basis to form the read key;

[0117] Step Sj6, storing the user data, verification code and read key separately.

[0118] In implementation, the process of setting the check code as the reading key corresponding to the segmented data can be to divide the check code into several segments according to the number of bits of the check code and the number of segmented data, and set each segment of the check code as the reading key basis. For example, if a certain data is divided into 4 segmented data (A, B, C, D) and a 64-bit (structured as aabbccdd, where each letter occupies 8 bits) check code, then the segmented data A is matched with the check code aa, the segmented data B is matched with the check code bb, the segmented data C is matched with the check code cc, and the segmented data D is matched with the check code dd, and aa, bb, cc, dd are recorded as the reading key basis of the corresponding segmented data;

[0119] The password of the data is ff. When generating the read key, insert ff into the corresponding read key base to generate the read key, that is:

[0120] The read key for split data A is ffaa, the read key for split data B is ffbb, the read key for split data C is ffcc, and the read key for split data D is ffdd;

[0121] After the above process is completed, if the split data A needs to be read, the read key ffaa needs to be verified before the split data can be read.

[0122] Specifically, when the verification information stamp reads the secret key, it responds to the password corresponding to the verification information stamp and releases the verification code corresponding to the read secret key and the corresponding verification information;

[0123] The information stamp is retained to respond to the verification information, and according to the verification code corresponding to the verification information, the segmented data corresponding to the verification code is released.

[0124] See also Figure 3As shown, it is a flow chart of data segmentation of the present invention, including:

[0125] Generate a check code corresponding to the user data;

[0126] Set up several storage spaces with the same space;

[0127] Divide the user data equally according to the amount of storage space to form segmented data, and divide the check code equally to form a segmented check code;

[0128] The segmentation data and the segmentation check code are stored in the corresponding storage space.

[0129] Specifically, the process of setting the check code as the reading key of the corresponding segmented data includes:

[0130] Set the checksum at the beginning of the segmented data;

[0131] generating a read initiator corresponding to the check code;

[0132] Set the initiator to read the corresponding segmented data when the initiator reads the checksum completely.

[0133] By setting up several levels of storage, user data, verification information and passwords are stored separately, and corresponding mapping relationships are set in each level. While effectively improving data security, the independent relationships between levels are used for mutual verification, which effectively improves the robustness of the data destruction process and improves data security. At the same time, it reduces the response chain for deleting data, thereby further improving the timeliness of sensitive data deletion.

[0134] In implementation, for a single user data, it may occupy several aligned spaces in a disk with a disk aligned space of 2k. On this basis, the “front end” represents the part read earlier in each aligned space;

[0135] Likewise, in blockchain, the “front end” refers to the part of the blockchain where the directory comes first.

[0136] Disk alignment usually refers to ensuring that the starting position of the partition and the starting position of the file system's logical cluster are aligned with the physical sector size of the hard disk (usually 4KB, or 4096 bytes) when creating a partition on a hard disk or solid-state drive. This alignment can improve the read and write performance of the disk, especially for hard disks using Advanced Format technology, which increases the size of each sector from the traditional 512 bytes to 4096 bytes.

[0137] The purpose of disk alignment is to ensure that data read and write operations can be aligned with the physical sector boundaries of the hard disk to avoid cross-sector read and write, which can reduce the number of disk read and write times, improve performance, and extend the service life of the hard disk. For disks whose physical sector size is inconsistent with the logical sector size, partition 4K alignment can give full play to the disk's read and write performance.

[0138] In practice, 4K alignment can be achieved through some partitioning tools. Disk alignment space means that when creating a partition, the starting position of the partition is aligned to an integer multiple of the hard disk physical sector size. This can improve disk performance and reduce unnecessary read and write operations.

[0139] The "partitioning" of blockchain usually refers to sharding, a technology used to improve the scalability of blockchain. The core idea of ​​sharding is to divide the entire blockchain network into multiple smaller, more manageable parts, each of which is called a shard. The main purpose of sharding is to improve the scalability and processing power of blockchain. By dividing the network into multiple shards, each shard can process transactions and smart contracts independently, thereby increasing the throughput of the entire network.

[0140] In a sharded blockchain, not all nodes need to process all transactions for the entire network. Each node only needs to maintain information related to its shard. In this way, each shard can have its own validator network and mine blocks using the Proof of Work (PoW) algorithm, or by staking or voting.

[0141] Sharding technology can significantly improve the performance of blockchain because it allows the network to increase throughput linearly as the number of nodes increases. By utilizing sharding technology, the entire blockchain can process and store transactions more efficiently, thereby improving overall performance.

[0142] See also Figure 4 As shown, it is a flowchart of user data deletion of the present invention, including:

[0143] Inserting random characters at random positions in the verification information stamp to form a garbled information stamp;

[0144] Among them, when the preset period is reached, if a garbled information stamp is formed in any verification code, the verification information corresponding to the verification code stops being reported.

[0145] Inserting the deletion code into the front end of the user data and forming a number of busy codes corresponding to the user data;

[0146] In response to the deletion code and each busy code, the space occupied by the user data is identified as busy empty data;

[0147] The space occupied by busy empty data is formatted sequentially at the next preset cycle.

[0148] In implementation, when setting busy empty data:

[0149] Step 1: Insert a specific deletion code at the front end of the user data (file) to form a mark indicating that the file has been deleted;

[0150] Step 2: The system generates busy codes corresponding to the user data, which temporarily occupy the file's space to prevent other data from overwriting it immediately;

[0151] Step 3: The system responds to the deletion code and the busy code and identifies the space occupied by the file as busy empty data;

[0152] Step 4: In the next preset cycle, the system formats the space occupied by these busy empty data in sequence, completely releasing the space for new data to use.

[0153] Specifically, when forming busy space data, it is set accordingly according to the storage method of user data;

[0154] Wherein, if the user data includes directories, the busy empty data occupies the corresponding directories;

[0155] If the user data includes a disk, the busy empty data occupies the corresponding disk space.

[0156] Specifically, the steps of data deletion also include:

[0157] When reading user data, the integrity of the check code is verified, and the check code complete information or check code missing information is formed;

[0158] In response to the complete information of the verification code, a data retention instruction is sent and the next preset cycle is entered;

[0159] In response to the verification code missing information, a data deletion instruction is sent;

[0160] In response to the data deletion instruction, the verification information and the transmission of the retained information are stopped.

[0161] In implementation, if the system receives a packet containing a complete response checksum:

[0162] Step 1: The system detects that the response check code in the data packet is complete and correct;

[0163] Step 2: The system sends a data retention instruction to the data storage unit based on the integrity of the verification code;

[0164] Step 3: The system marks the data as "retained" and transfers it to the preset storage cycle queue;

[0165] Step 4: The system enters the next preset cycle and prepares to process new data packets.

[0166] If the system receives a packet with a missing response checksum:

[0167] Step 1: The system detects that the response check code is missing in the data packet;

[0168] Step 2: The system sends a data deletion instruction to the data storage unit according to the absence of the verification code;

[0169] Step 3: The system performs a data deletion operation to ensure that the information in the data packet is completely cleared;

[0170] Step 4: The system records the data deletion operation and updates the data management log.

[0171] If the system receives a data deletion instruction:

[0172] Step 1: The system recognizes the data deletion instruction;

[0173] Step 2: The system stops all ongoing verification information processing, including verification of the response verification code;

[0174] Step 3: The system stops sending all retained information, including the sending of data retention instructions;

[0175] Step 4: The system confirms that the data deletion operation is complete and updates the system status to ensure that no new data retention instructions are sent.

[0176] Furthermore, by inserting a meaningless character into user data, verification information or password, the integrity of the data is destroyed, which effectively prevents the data from being intercepted and read, and effectively improves the data deletion rate, thereby further improving the timeliness of sensitive data deletion.

[0177] In particular, when data is deleted, in addition to this solution, the data should be repeatedly erased to avoid recovery, such as:

[0178] Data overwrite: Data overwrite technology achieves the purpose of clearing data by writing non-sensitive data to the storage location where sensitive data was previously stored. This method repeatedly writes a specific pattern (such as all zeros or all ones) or random data to overwrite the original data, ensuring that it cannot be recovered.

[0179] Multiple overwrites: For particularly sensitive data, multiple overwrites are usually required, and the common practice is to perform 3 or 7 writes. The 3-overwrite method includes the first overwrite with fixed characters, the second overwrite with the complement of the fixed characters, and the third overwrite with random characters. The 7-overwrite method is more complicated, including multiple overwrites of fixed characters and their complements, as well as overwrites of random characters.

[0180] The common steps of the three-overwrite method are as follows:

[0181] First overwrite: Overwrite the entire data storage area with a fixed character (usually 0 or 1). For example, if 0 is used, all data bits will be overwritten with 0.

[0182] Second overwrite: Overwrite with the complement of the fixed character used in the first overwrite. If 0 was used the first time, 1 is used this time, and vice versa.

[0183] The third overwrite: Overwrite with randomly generated characters. This overwrite is not a fixed pattern, but random, which increases the difficulty of data recovery.

[0184] The 7-overwrite method is more complex and thorough than the 3-overwrite method, including:

[0185] First overwrite: Use fixed characters (such as 0) to overwrite the entire data storage area.

[0186] Second overwrite: overwrite with the complement of a fixed character (such as 1).

[0187] The third overwrite: overwrite again with a fixed character (such as 0).

[0188] Fourth overwrite: Overwrite with random characters.

[0189] Fifth overwrite: overwrite again using the complement of the fixed character (such as 1).

[0190] Sixth overwrite: Overwrite with random characters again.

[0191] Seventh overwrite: The last overwrite is performed using a fixed character (such as 0).

[0192] The 7-overwrite method greatly increases the difficulty of data recovery by repeatedly alternating between fixed characters, their complements, and random characters.

[0193] In implementation, the choice of overwrite strategy depends on the sensitivity of the data and the security standards that need to be met. For extremely sensitive data, a more complex overwrite strategy may be required to ensure data security.

[0194] Random Overwrite:

[0195] Random data overwrite repeatedly writes randomly generated binary data in data blocks, further improving the security of data deletion.

[0196] IEEE 2883 Standard:

[0197] The IEEE 2883 standard defines three categories for various storage media: clearing, sanitizing, and destroying. Clearing methods use logical techniques to prevent simple, non-invasive data recovery attempts; sanitizing methods use logical and physical techniques to completely erase all stored data; and destroying methods use irreversible physical techniques to render the storage device completely unusable.

[0198] Specifically, the data destruction method also includes a relief mechanism, including:

[0199] Setting preset relief periods;

[0200] The data destruction method ceases to operate within the preset relief period.

[0201] Generally, the relief period should be set against the preset period, such as:

[0202] For a preset period of 3 days, the relief period can be set to 12 hours;

[0203] For a preset period of 1 day, the relief period can be set to 2 hours;

[0204] Optionally, the relief period can be set to 0, but when it is set to 0, the user data will be destroyed when a single key read fails.

[0205] In the simplest case, only one personal information processor keeps the key and no salt value is used:

[0206] When storing user sensitive information, the following examples are available:

[0207] Name Contact Number Certificate Number Zhang San 19999999999 88877799992233666X

[0208] Request an encryption key from the database. If the key does not exist, a randomly generated key is generated (using the AES 256-bit key algorithm as an example):

[0209] ID Key (randomly generated) 1 3F91B8F54C5A8E5C7F7F09AF2927C9B33F91B8F54C5A8E5C7F7F09AF2927C9B3

[0210] Use key encryption to store sensitive data:

[0211] Name ciphertext Phone ciphertext Document number ciphertext 6Cpo0XifFVyb6SxwQ / CXEw== sP0XOX / ciJuKplEw0 / xUWg== wqlF6fk86P+pQMfgNpR / jx6MFWy3gtRpJOGMP7EE3hE=

[0212] When a user stores sensitive information, the program will query the key database to see if a key corresponding to the user ID has been generated. If so, the program will return the key. If not, the program will request the key center to generate a key corresponding to the user ID and store it in the user key database. The sensitive data will be encrypted and stored using the returned key.

[0213] For example, in online banking system, transaction information is encrypted. A user conducts a transaction in an online banking system and enters sensitive personal information, such as account number and password.

[0214] 1. After the user submits the transaction information, the system first checks the key database corresponding to the user ID to see if there is a valid encryption key;

[0215] 2. If a key corresponding to the user ID already exists in the key database, the system directly returns the key;

[0216] 3. If there is no key corresponding to the user ID in the key database, the system sends a request to the key center to generate a new encryption key;

[0217] 4. After the key center generates the key, it stores it in the user key database and returns it to the online banking system;

[0218] 5. The online banking system uses the returned key to encrypt the user's sensitive transaction information and then stores the encrypted data in the database.

[0219] Patient data protection in health management systems, where users enter personal health data such as medical records and test results.

[0220] 1. After the user submits personal health data, the system first checks the key database corresponding to the user ID to see if there is a valid encryption key.

[0221] 2. If a key corresponding to the user ID already exists in the key database, the system directly returns the key.

[0222] 3. If there is no key corresponding to the user ID in the key database, the system sends a request to the key center to generate a new encryption key.

[0223] 4. After the key center generates the key, it stores it in the user key database and returns it to the health management system.

[0224] 5. The health management system uses the returned key to encrypt the user's sensitive health data, and then stores the encrypted data securely in the database.

[0225] When users store sensitive information, the system ensures the security of the data by querying and using keys. In this way, even if the data is illegally accessed, unauthorized third parties cannot read the original data.

[0226] When the service cycle ends, you only need to destroy the user ID key corresponding to the user key library to ensure that sensitive data in all businesses cannot be recovered and meet the compliance requirements of deletion or anonymization.

[0227] It is understandable that the above embodiments are merely examples, and no exact encrypted data or encrypted information is stored in any database.

[0228] So far, the technical solutions of the present invention have been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present invention is obviously not limited to these specific embodiments. Without departing from the principle of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will fall within the protection scope of the present invention.

[0229] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for destroying encrypted data, characterized in that: include: Segment the user data, and set a corresponding retention information stamp in each segmented user data, each retention information stamp sends retention information at a preset period; Determine a corresponding check code according to the retained information, and set a number of check information stamps for sending check information according to the preset period in the check code; The password is matched with the verification code, and each verification information stamp responds to the password and sends the verification information; The retained information stamp responds to the corresponding retained information sent by the corresponding verification information; In response to the stop of verification information, the corresponding verification information stamp is formatted; In response to the stop of the message of the retained information, the corresponding user data is formatted; The process of setting up encrypted data includes: Respond to data storage requests and store corresponding user data; Compiling the user data to form a corresponding verification code; Segmenting the user data and forming a plurality of segmented data marked by check codes; storing the segmented data respectively, and setting the verification code as a reading key basis of the corresponding segmented data; splitting the verification code and inserting the password into a corresponding read key basis to form a read key; storing the user data, the verification code and the read key respectively; When the verification information stamp reads the secret key, it responds to the password corresponding to the verification information stamp and releases the verification code corresponding to the read secret key and the corresponding verification information; The information stamp is retained to respond to the verification information, and according to the verification code corresponding to the verification information, the segmented data corresponding to the verification code is released.

2. The method for destroying encrypted data according to claim 1, characterized in that: The steps of segmenting user data include: Generate a checksum corresponding to the user data; set up several storage spaces with the same space; Divide the user data equally according to the amount of storage space to form segmented data, and divide the check code equally to form a segmented check code; The segmentation data and the segmentation verification code are stored in corresponding storage spaces.

3. The method for destroying encrypted data according to claim 2, characterized in that: The process of setting the verification code as a reading key of the corresponding segmented data includes: Setting the check code at the front of the segmented data; generating a read initiator corresponding to the check code; Set the initiator to read the corresponding segmented data when the initiator reads the checksum completely.

4. The method for destroying encrypted data according to claim 1, characterized in that: The process of formatting the corresponding verification information stamp also includes: Inserting random characters at random positions in the verification information stamp to form a garbled information stamp; Wherein, when the preset period is reached, if the garbled information stamp is formed in any verification code, the verification information corresponding to the verification code stops being reported.

5. The method for destroying encrypted data according to claim 4, characterized in that: The process of formatting the corresponding user data also includes: Inserting the deletion code into the front end of the user data and forming a plurality of busy codes corresponding to the user data; In response to the erasure code and each busy code, identifying the space occupied by the user data as busy empty data; The space occupied by the busy empty data is formatted sequentially in the next preset cycle.

6. The method for destroying encrypted data according to claim 5, characterized in that: When forming the busy space data, the data is set accordingly according to the storage mode of the user data; Wherein, if the user data includes a directory, the busy space data occupies the corresponding directory; If the user data includes a disk, the busy space data occupies the corresponding disk space.

7. The method for destroying encrypted data according to claim 1, characterized in that: Also includes: When reading the user data, the integrity of the check code is verified, and check code complete information or check code missing information is formed; In response to the complete information of the verification code, a data retention instruction is sent and the next preset cycle is entered; In response to the verification code missing information, a data deletion instruction is sent; In response to the data deletion instruction, the sending of the verification information and the retained information is stopped.

8. The method for destroying encrypted data according to any one of claims 3, 6 or 7, characterized in that: It also includes relief mechanisms, including: Setting preset relief periods; The data destruction method stops running within a preset relief period.

Images