Different compute engines support different data masking methods and security algorithms. Use this reference to choose compatible algorithms across engines.
|
Compute engine |
Data masking method |
Supported security algorithms |
|
MaxCompute |
Security policy's algorithm package and the database's built-in function |
|
|
Hive |
Security policy algorithms and database built-in functions |
|
|
AnalyticDB for PostgreSQL |
Built-in Database Functions |
The following encryption algorithms are not supported: Gaussian, sha256, sha384, sha512, salted sha256, salted sha384, salted sha512, and salted md5. |
|
Hologres |
Built-in database function |
The following encryption algorithms are not supported: Gaussian, sha256, sha384, sha512, salted sha256, salted sha384, salted sha512, and salted md5. |
|
StarRing ArgoDB |
Built-in Database Functions |
The following encryption algorithms are not supported: Gaussian, sha256, sha384, sha512, salted sha256, salted sha384, salted sha512, and salted md5. |
-
UDF (User-Defined Function) masking uses a security UDF installation package. It supports flexible masking techniques but requires installation within the relevant project. DB (Database) masking uses the compute engine's built-in functions and works immediately without installation, but may not support all masking algorithms.
-
If your tenant uses multiple compute engines, such as MaxCompute and Hologres, select masking algorithms that all engines support to avoid masking failures.