Help Center/ DataArts Studio/ FAQs/ DataArts Security/ Why Isn't Data Masked Based on a Specified Rule After a Data Masking Task Is Executed?

Updated on 2025-02-20 GMT+08:00

View PDF

Why Isn't Data Masked Based on a Specified Rule After a Data Masking Task Is Executed?

Possible Causes

Static masking tasks depend on sensitive data discovery tasks. If the statuses of sensitive data fields were not changed to Valid on the Sensitive Data Distribution page, the system considers that there is no sensitive field, so does not mask data based on a rule.

Solution

Before creating a static masking task, you must create a sensitive data discovery task. After sensitive fields are discovered, change the statuses of the sensitive fields to Valid on the Sensitive Data Distribution page.

Parent topic: DataArts Security

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

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.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot