Creating a Database Data Masking Task
Create a data masking task for a database to mask sensitive information identified in the database.
Prerequisites
- DSC has been allowed to access the database assets.
- Database assets have been added.
- Sensitive data has been identified. For details, see Creating a Task.
Procedure
- Log in to the management console.
- Click in the upper left corner of the management console and select a region or project.
- In the navigation pane on the left, click and choose .
- In the navigation pane, choose Data Masking.
- On the Database Masking tab page, click to enable the database data masking.
- Click Create Task and configure required parameters. Table 1 describes the parameters.
Figure 1 Configuring a data masking task
Table 1 Parameter description Parameter
Description
Task Name
You can customize the name of a masking rule.
The rule name must meet the following requirements:- Contain 1 to 255 characters.
- Consist of letters, digits, underscores (_), and hyphens (-).
Select Data Source
Select a data source. Value options are SQLServer, MySQL, or PostgreSQL.
Data Source
NOTE:If no cloud databases are available, click Add Database to add cloud database assets. For details, see Adding a Database.
Database Instance: Select the database instance where the data to be anonymized is located.
Database: Select the name of the database where the data to be anonymized is located.
Schema: This parameter is displayed only when SQLServer or PostgreSQL is selected for Data Source.
Table Name: Select the name of the database table where the data to be anonymized is located.
Data Type: If you select the check box, data in this column is copied to the target database.
The target Data Type and Risk Level of the data are also displayed.
- Click Next.
Figure 2 Configuring a masking algorithm
- Select the data columns you want to mask.
- Select a masking algorithm. For details about masking algorithms, see Configuring a Data Masking Rule.
- Click Next.
Figure 3 Configuring data masking period
Select and set the execution period of a masking task.
- Manual: Manually enable a masking task and execute it based on masking rules.
- Hourly: Execute a data masking task every several hours.
Example: If the masking task needs to be executed every two hours, set this parameter to 02:00.
- Daily: Execute a data masking task at a specified time every day.
Example: If the masking task needs to be executed at 12:00 every day, set this parameter to 12:00:00.
- Weekly: Execute a data masking task at a specified time every week.
Example: If the masking task needs to be executed at 12:00 every Monday, set this parameter to 12:00:00 every Monday.
- Monthly: Execute a data masking task at a specified time on a specified day every month.
Example: If the masking task needs to be executed at 12:00 on the 12th day of each month, set this parameter to 12:00:00 12th day of every month.
If you want to execute a data masking task on the 31st day of each month, the system automatically executes the task on the last day of every month.
- Click Next.
Figure 4 Configuring a target data type
- Select a database instance and database name, and enter the database table name.
If the entered data table name already exists, the system updates the data table in the target database.
If the entered data table name does not exist, the system automatically creates a data table with the same name in the target database.
Do not fill in an existing service data table. Otherwise, services may be affected.
- Set the column name of the target data type.
By default, the system generates a name that is the same as the name of the data source column. You can retain the default name or change it as required.
- Select a database instance and database name, and enter the database table name.
- Click Finish.
Follow-up Procedure
After a database data masking task is created, execute the task. For details, see Executing a Database Data Masking Task.
Feedback
Was this page helpful?
Provide feedbackThank 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