Encryption of Existing Historical Data
Batch encrypt existing unencrypted historical plaintext data in the database to enable unified ciphertext storage for all legacy data. For newly added data, implement incremental encryption using either an Application Plugin or a Proxy. By combining these two approaches, all data is stored in ciphertext format, thereby eliminating the risk of data leakage associated with legacy plaintext data and ensuring the security and compliance of all business data.
Procedure
- When the field key configuration is in editable mode (as shown in Figure 1), click Save in the upper-middle corner to confirm the changes.
- Click Encrypt in the Operation column on the right side of the field to perform the encryption operation, as shown in Figure 2.
- After encryption is complete, you can connect to the database using a third-party tool (e.g., Navicat or DBeaver) to view the encrypted data, as shown in Figure 3.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot


