Creating a Data Masking Task for Elasticsearch
Create a data masking task for Elasticsearch to mask sensitive information in tables or columns of Elasticsearch.
This section describes how to create a data masking task for Elasticsearch.
Prerequisites
- DSC has been allowed to access the database assets.
- You have added Elasticsearh assets. For details, see Big Data Assets.
- 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 displayed page, click the Elasticsearch Data Masking tab.
- Click switch to to enable the data masking for Elasticsearch.
- Click Create Task and configure required parameters. Table 1 describes the parameters.
Figure 1 Creating an Elasticsearch data masking task - Configuring data source
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. Currently, only Elasticsearch is supported.
Data Source
NOTE:If no assets are available, Click Add to add a data source. For details, see Adding a Big Data Source.
Elasticsearch: Select the Elasticsearch instance where the data to be masked is located.
Index: Select the index where the data to be masked is located.
Type: Select the type of the data to be masked.
Field: If you select the check box, data in this column is copied to the Data Type column.
The target Data Type and Risk Level of the data are also displayed.
- Click Next.
Figure 2 Creating an Elasticsearch data masking task - Setting a masking algorithm
- Select the fields to be masked.
- Select a data masking algorithm. For details about data 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 Creating an Elasticsearch data masking task - Setting the target data
- Select an Elasticsearch instance and index, and set Type.
If the type that you entered already exists, the system updates the data of the type in the target data source.
If the type that you entered does not exist, the system automatically creates a type with the same name in the target data source.
If you want to use an existing type, do not set Type. 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 an Elasticsearch instance and index, and set Type.
- Click Finish.
Follow-up Procedure
After the Elasticsearch data masking task is created, execute the task. For details, see Executing an Elasticsearch 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