You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement support for dynamic data masking at the column level to enhance data security and privacy.
Note: This feature might be offered as an Enterprise Edition feature, similar to Snowflake.
Background
Dynamic data masking is a security feature that helps protect sensitive data by automatically masking certain data fields to ensure that unauthorized users cannot access sensitive information. It allows for customizable masking rules, based on user roles or other criteria, without requiring any changes to the underlying data or applications.
Feature Request
Add support for dynamic data masking at the column level, similar to the functionality provided by BigQuery and Snowflake Enterprise Edition. This would allow users to define masking policies for specific columns in a dataset, based on user roles, permissions, or other criteria.
Summary
Implement support for dynamic data masking at the column level to enhance data security and privacy.
Note: This feature might be offered as an Enterprise Edition feature, similar to Snowflake.
Background
Dynamic data masking is a security feature that helps protect sensitive data by automatically masking certain data fields to ensure that unauthorized users cannot access sensitive information. It allows for customizable masking rules, based on user roles or other criteria, without requiring any changes to the underlying data or applications.
Feature Request
Add support for dynamic data masking at the column level, similar to the functionality provided by BigQuery and Snowflake Enterprise Edition. This would allow users to define masking policies for specific columns in a dataset, based on user roles, permissions, or other criteria.
References
1. BigQuery: dynamic data masking
2.Snowflake: Using Dynamic Data Masking (ENTERPRISE EDITION FEATURE)
The text was updated successfully, but these errors were encountered: