Asset Database

Constraint Application

Special note regarding whether to enable SSL: Due to current operational constraints, enabling SSL is only supported for MySQL version 8.4, and the MySQL database must be configured for certificate-based authentication bypass.

Asset Database Management Home Page

Upon entering the Asset Database Management Module, you will be directed to the Asset Database Management Home Page, as shown in Figure 1.

Figure 1 Management home page 1

The current data source details display the attributes of the highlighted database. Select Edit at the bottom to edit the attributes of the currently selected database.

Above the database icon are various operational functions, including:

• Filter Toolbar: Used for quickly querying databases that are managed by the Database Encryption System.
• Manage databases using an icon-based interface, as shown in Figure 2. This approach is suitable when there are few databases to manage – it is visually appealing and easy to use; for example, it is appropriate for scenarios involving fewer than 10 databases.
  Figure 2 Management home page 2
  
• List-based database management, as shown in Figure 3, is suitable when there are a large number of databases to be managed—for example, when there are more than 10 databases.
  Figure 3 Management home page 3
  

Add New Asset Database

1. Logging In to the Database Encryption System using the system administrator (sysadmin) account.
2. Click on Asset Database in the left-side navigation tree.
3. In the right-hand pane, click the Add Data Source icon, as shown in Figure 4.
   Figure 4 Adding a data source
   

4. In the pop-up interface, select the database type, as shown in Figure 5.
   Figure 5 Selecting the database type
   

   When using the Proxy Pattern for encryption, certain databases (e.g., Oracle) rely heavily on their specific database version. If you plan to use the Proxy Pattern for database encryption, we recommend carefully reviewing the Support and Compatibility List chapter.

5. After selecting the database type, proceed to the Database Configuration Interface, as shown in Figure 6 (this example uses MySQL as the database). The parameters required vary slightly depending on the database type. The descriptions of the data source configuration parameters are provided in Table 1.
   Figure 6 Configuration information
   

   Table 1 Data source configuration parameter description

   Parameter	Description
   Data Source Name	You can customize the data source name (it cannot contain special characters). The name length shall not exceed 25 characters. It is recommended to assign a meaningful business name to the data source for easier subsequent use. For example: CRM system database.
   Connection Type	This parameter is displayed when the Data Source Type is set to Oracle. There are two options for data source connection type: Service Name: Service_Name – please consult your database administrator. Instance Name: Instance_name; please consult your data administrator to obtain the corresponding instance name, IP address, and port number.
   Service Name	This parameter is displayed when the Data Source Type is set to Oracle and the Connection Type is set to Service Name. For specific service names, please consult your database administrator.
   IP/Domain Name	Enter the IP address or domain name of the database. IP address: Supports both IPv4 and IPv6 formats.
   Port Number	Database port. For example: MySQL port 3306.
   Database Name	Enter the name of the database to connect to. When the Data Source Type is set to Oracle, this parameter is not displayed.
   Username	Enter the username required to connect to the database.
   Password	Enter the password required to connect to the database.
   Database version	Click Version Check to generate automatically. NOTE: Note: When using the proxy mode for encryption, certain databases (e.g., Oracle) rely heavily on specific database versions.
   Character encoding	Supported character encodings. When the Data Source Type is set to MySQL, PostgreSQL, or MS SQL Server, you can select one of the following character encodings: UTF8 GBK When the Data Source Type is set to Oracle, you can select one of the following character encodings: AL32UTF8 ZHS16GBK When the Data Source Type is set to DB2, you can select one of the following character encodings: Unicode UCS-2 UTF16 UTF8

6. Enter the required configuration information, then click Confirm to save (it is recommended to use the Test function to verify the settings before saving).

Searching the Asset Database

The Asset Database Management homepage features a database search function; when the number of databases is large, this search functionality is particularly useful.

As shown in Figure 7, users can perform searches based on the following attributes; the data source name and IP address support fuzzy queries.

• Data Source Name
• IP address
• type of database

Figure 7 Searching the database

Editing the Asset Database

1. Select the database you wish to edit; hover the mouse over the database icon, then click the Preview icon, as shown in Figure 8.
   Figure 8 Selecting the current database
   

2. Select Edit at the bottom of the Data Source Details list to edit the properties of this database; see Figure 9 for details.
   Figure 9 Editing the database
   

Deleting an Asset Database

In some cases, it may be necessary to delete a specific Asset Database. Deleting an Asset Database will affect any projects that have already referenced it.

1. Logging In to the Database Encryption System using the system administrator (sysadmin) account.
2. Select Asset Database from the left navigation tree.
3. Select the database you wish to delete; hover the mouse over the target database, then click Delete to remove the database, as shown in Figure 10.
   Figure 10 Deleting the data source
   

• Data loss: Encryption/decryption or data masking operations depend on specific data source configurations. If the data source is edited or deleted during these operations, it may prevent the relevant data from being correctly decrypted or restored, leading to data loss.

• System failure: Rule configuration, encryption/decryption, and data masking operations are typically tightly integrated with other parts of the system. Editing or deleting a data source while these operations are in progress may cause a system failure, disrupting the normal operation of the system.

• Security risk: Encryption/decryption and data masking operations involve the processing of sensitive data. If data in the source is edited or deleted during these operations, it may lead to security vulnerabilities, exposing sensitive data to potential risks.