Data Masking Overview
DSC supports static data masking and dynamic data masking. You can configure masking rules for specified data assets to implement static masking or use APIs for data masking to implement dynamic data masking, ensuring that sensitive information is not disclosed. Masking Algorithms and Application Scenarios lists the data masking algorithms supported by DSC.
Static data masking: DSC enables bulk data masking based on rules (DSC built-in rules or custom rules). Static data masking is typically applied when transferring production data to non-production environments (such as development and testing) or sharing data for research purposes. You can create a data masking task on the DSC console to quickly mask sensitive data in database, OBS, and big data assets.
API-based masking: Data accessed by external systems can be masked in real time. This masking type applies to scenarios where data is queried from the external system, such as production applications, data exchange, O&M applications, and marketing. For details, see APIs for data masking.
Procedure
Data Sources Supported by Data Masking
Table 1 describes the data sources supported by static data masking. API-based dynamic masking is used to mask structured JSON data.
| Masking Type | Data Source |
|---|---|
| Data masking | SQLServer, MySQL, TDSQL, PostgreSQL, KingBase, DMDBMS, GaussDB, Oracle, DWS, and Greenplum |
| Elasticsearch masking | Elasticsearch |
| Hive masking | Hive |
| HBase masking | HBase |
| MRS masking | MRS_HIVE |
| OBS masking | OBS bucket files (text, images, and LeRobot datasets)
|
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