A method based on distributed sensitive data desensitization, encryption, decryption and auditing

Abstract

The application discloses a method based on distributed sensitive data desensitization, encryption, decryption and auditing, which realizes desensitization, encryption and decryption of sensitive data from aspects of architecture, key technology use and the like; realizes desensitization, encryption and decryption of sensitive data on the premise that the running efficiency of an existing application system is not greatly influenced; and does not have any influence on the use of non-decrypted data. Through a method of two keys, sensitive data is desensitized and encrypted synchronously and efficiently; through a method of two keys, decryption data only needs to be simply analyzed and modified in an SQL part of an existing application system source code, so that decryption of the data is completed; through authorization and limitation of a decryption condition, a workflow of application and approval of an encrypted data manager by a decrypter or a decryption device is realized; control of the data decryption is realized; and at the same time of the data decryption, decrypted data log records are distributedly generated and used for decrypted data analysis and auditing.

Description

Technical Field

[0001] This invention relates to the desensitization, encryption, decryption, and auditing of sensitive data, particularly a method for the desensitization, encryption, decryption, and auditing of sensitive data based on a distributed approach. Background Technology

[0002] Due to historical reasons, existing application systems often require or excessively use sensitive data. Application-level data masking techniques are insufficient to prevent large-scale data theft from the backend; furthermore, application-level masking necessitates complex and precise modifications to the source code. By implementing database-level data masking, distributed database encryption / decryption storage, and log auditing, the use of existing sensitive data can be protected to the greatest extent possible, ensuring data security. Simultaneously, it minimizes modifications to the source code of existing application systems.

[0003] SQL-based databases already possess triggering and data encryption mechanisms. However, for a long time, a complete and effective technical roadmap and methodology for applying these mechanisms has yet to be developed. This is mainly due to the excessive and cumbersome modifications required to existing application systems. Furthermore, the SELECT mechanism faces numerous complex technical bottlenecks in data decryption and auditing. Currently, many technologies tend to achieve data anonymization through techniques such as data stream interception and sandboxing; however, a feasible technical roadmap for encryption and decryption has not yet been established. Summary of the Invention

[0004] To address the above problems, the purpose of this invention is to provide a simple, secure, and efficient method for encrypting and decrypting sensitive data; this method employs the following technical solution:

[0005] By utilizing the trigger mechanism of relational application databases and distributed encrypted databases, unencrypted data is transferred to the distributed encrypted database for encryption based on the actual situation of the de-identified data in the application system's database, thereby de-identifying the data in the relational application database.

[0006] During encryption, the table > row > column information of sensitive data in the relational application database is used. The row dynamic ID is used as one key, and the other key is stored in a file using a distributed encryption database. The relevant table > row > column data is encrypted by concatenating the two keys in a simple or complex manner and using an encryption algorithm.

[0007] When encrypting data, the table > row > column, data owner, data ownership device, and row dynamic ID information corresponding to the encrypted data will be stored in the corresponding table > row > column of the distributed encrypted database at the same time as the encrypted data using plaintext or irreversible encryption methods.

[0008] When decrypting data, the two keys are matched with the corresponding encrypted information to decrypt the data;

[0009] During data decryption, the number of decryption attempts within a certain time range is limited by the number of records of the data owner and data-owning device / each decryption attempt, thereby achieving default decryption for the data owner and data-owning device.

[0010] When data decryption exceeds the limit, the data decryptor sends a decryption request to the encrypted data manager's mobile terminal or PC via SMS or App. The encrypted data manager, based on the decryption requester or requesting device, the decryption field or field group, comprehensively determines the number of records / decryption per time, the number of decryption attempts within a certain time range, and time control conditions; approves the data decryption requester and requesting device; before approving the data decryption request, the decryption data is marked as awaiting authorization.

[0011] During data decryption, data decryption applications and approvals are implemented for non-data rights holders and data rights devices.

[0012] After the data decryption application is approved, the applicant will receive a notification via SMS and App; and then authorizes the decryption process.

[0013] During data decryption, the decryption table > row > field, decryptor, decryption field, decryption authorizer, authorization method and time are simultaneously recorded in the distributed encrypted database for data analysis and auditing.

[0014] During decryption, a database session mechanism is used to achieve complex control over the number of data entries decrypted each time. Detailed Implementation

[0015] This invention provides a simple, secure, and efficient method for encrypting and decrypting sensitive data; the method employs the following technical solution:

[0016] 1. Utilize the trigger mechanisms of relational application databases and distributed encrypted databases such as Oracle, MySQL, SQL Server, DB2, DM, and Kingbase to transfer unencrypted data to the distributed database for encryption based on the actual situation of the data to be anonymized, thereby achieving data anonymization in the application database.

[0017] 2. During encryption, the sensitive data table > row > column information of the application database is used. The row dynamic ID is used as one key, and the distributed database stores another key in the form of a file. The two keys are concatenated in a simple or complex way, and the encryption algorithm is used to encrypt the relevant table > row > column data.

[0018] 3. When encrypting data, the information such as the table > row > column corresponding to the encrypted data, the data owner, data device, and row dynamic ID, etc., are stored in the corresponding table > row > column of the distributed encrypted database at the same time using plaintext or irreversible encryption methods.

[0019] 4. When decrypting data, two keys are used to match the corresponding encrypted information to decrypt the data.

[0020] 5. During data decryption, the default decryption of the data owner and data device is achieved by limiting the number of decryption entries / each time and the number of decryption attempts within a certain time range.

[0021] 6. When decrypting data, if the default decryption authorization limit is exceeded, the data decryptor sends a decryption request to the encrypted data administrator's mobile terminal or PC via SMS, App, etc. The encrypted data administrator, based on the decryption requester or requesting device, the decryption field or field group, comprehensively determines the number of decryption entries / each time, the number of decryption attempts within a certain time range, time control conditions, etc.; approves the data decryption requester and the requesting device; before approving the data decryption request, the decryption data is marked as awaiting authorization.

[0022] 7. When decrypting data, for non-data rights holders and data rights devices, an authorized decryption method is used to realize the data decryption application and decryption approval.

[0023] 8. After the data decryption application is approved, the applicant will receive a notification via SMS, APP, etc., and then authorize the decryption.

[0024] 9. During data decryption, the decryption table > row > field, decryptor, decryption field, decryption authorizer, authorization method, and time are simultaneously recorded in the distributed database for data analysis and auditing.

[0025] 10. During decryption, a database session mechanism is used to implement complex control over the number of data entries decrypted each time.

Claims

1. A method for processing distributed sensitive data, characterized in that, By utilizing the trigger mechanism of relational application databases and distributed encrypted databases, unencrypted data is transferred to the distributed encrypted database for encryption based on the actual situation of the de-identified data in the application system's database, thereby de-identifying the data in the relational application database. During encryption, the table > row > column information of sensitive data in the relational application database is used. The row dynamic ID is used as one key, and the distributed encryption database stores the other key in a file. The two keys are concatenated in a simple or complex manner, and the encryption algorithm is used to encrypt the relevant table > row > column data. When encrypting data, the table > row > column, data owner, data ownership device, and row dynamic ID information corresponding to the encrypted data will be stored in the corresponding table > row > column of the distributed encrypted database at the same time as the encrypted data using plaintext or irreversible encryption methods. When decrypting data, the two keys are matched with the corresponding encrypted information to decrypt the data; During data decryption, the number of decryption attempts within a certain time frame is limited by restricting the number of records decrypted each time for the data owner and data-granting device, thereby achieving default decryption for the data owner and data-granting device. When data decryption exceeds the limit, the data decryptor sends a decryption request to the encrypted data manager's mobile terminal or PC via SMS or App. The encrypted data manager, based on the decryption requester or requesting device, the decryption field or field group, comprehensively determines the number of data to be decrypted each time, the number of decryptions within a certain time range, and time control conditions; approves the data decryption requester and requesting device; before approving the data decryption request, the decrypted data is marked as awaiting authorization. During data decryption, data decryption applications and approvals are implemented for non-data rights holders and data rights devices. After the data decryption application is approved, the applicant will receive a notification via SMS and App; and then authorizes the decryption process. During data decryption, the decryption table > row > column, decryptor, decryption field or field group, decryption authorizer, authorization method and time are simultaneously recorded in the distributed encrypted database for data analysis and auditing. During decryption, a database session mechanism is used to achieve complex control over the number of data entries decrypted each time.