CloudDM 4.8.0 adds GreptimeDB as a DataSource
Skip to main content

Data masking overview

Enterprise databases often contain sensitive information such as personal identifiers, bank card numbers, and phone numbers. Unnecessary access to this data during development, testing, or operations can expose personal information and create compliance risks.

CloudDM applies masking rules as it returns query results. The database keeps the original values. Accounts that lack permission to view unmasked data see the values produced by the rules.

CloudDM checks the rule scope and account permissions before returning a masked phone number.

Benefits​

  • Preserve stored values. Configure masking in CloudDM while keeping the original business data in the database.
  • Mask query results as they return. Databases continue to store and process the original values.
  • Control masking by environment and resource. Apply rules to selected environments and database objects.
  • Control unmasked access by account. Resource permissions determine who can see the original values.
  • Reduce exposure. Limit unnecessary access in development, testing, operations, and analysis.

Common use cases​

  • Production troubleshooting. Hide personal details unrelated to the problem.
  • Development and testing. Reduce exposure to original values when verifying behavior against production-like data.
  • Reporting. Hide sensitive customer details in query results and exports.
  • Temporary access. Grant unmasked access to selected resources for a limited period when needed.

How it works​

  • Masking rules define match conditions and how CloudDM transforms matching values.
  • Rule scope defines the environments and database objects covered by the rules.
  • Environment settings determine which set of security rules applies.
  • Resource permissions determine who can see unmasked values.

Configure data masking​

  1. In Data Access > Security Rules, create or select a security rule.
  2. In its details, choose Desensitization rules and enable the masking rules you need.
  3. Use scope and Set up to configure resources and parameters.
  4. Open Environment and assign the security rule to the target environment.
  5. In Data Query, verify masking with an account that lacks permission to see unmasked data.
caution

Use test queries that reflect your business data. Check the DataSource, environment, rule scope, and account permissions when comparing results.