Linking Discovery Results to Encryption Settings
The "Link Discovery Results to Encryption Settings" feature links the results of sensitive data discovery/verification to the encryption settings for the respective fields; that is, sensitive data encryption is automatically configured based on the discovery results of sensitive data, as shown in Figure 1.
This will significantly reduce the workload associated with configuring encrypted fields one by one, while also preventing omissions or incorrect configurations.
The specific operations for the database encryption system are as follows:
- The results of a sensitive data discovery or confirmation task are saved as a version—e.g., Version A.
- Automatically map the saved discovery result version to the encryption configuration. For example: Map Version A to the encryption configuration.
Prerequisite
Sensitive data discovery and verification have been configured and executed; for detailed instructions, please refer to the Sensitive Data Discovery section.
The Discovery Results are Linked to the Encryption settings.
- Navigate to the Discovery Results page for sensitive data, as shown in Figure 2.
- Click Save; the system will display a Save Version dialog box, as shown in Figure 3; the parameter descriptions are provided in Table 1.
- Click Save. The system adds a new version, "Version A", as shown in Figure 4.
- Close this window; the system already contains the version we have saved.
- Log in to the ERP system, select Encryption Settings Management, then select Encryption Policy Settings, next select Asset Database, and finally select Batch Configuration to access the interface shown in Figure 5.
- Select a previously saved discovery result version and configure the encryption Strategy in batch. As shown in Figure 6, select the discovery task and its corresponding saved version from the Discovery Task Version dropdown menu.
- Click Batch Configuration; at this point, all confirmed and saved sensitive field results will be automatically applied to the table field encryption settings.
- Subsequently, existing historical data must also be encrypted.
There are numerous methods for handling existing historical data; depending on the specific circumstances, please refer to:
- Downloading the Plugin.
- Rule Management.
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





