This topic describes the methods for authorizing Data Security Center (DSC) to access different types of data assets.
You can use the following methods to authorize DSC to access different types of data assets: one-click authorization and username and password-based authorization.
- One-click authorization allows you to authorize DSC to access a data asset with one click in the DSC console. You do not need to enter the username and password that are used to access the data asset. During the authorization process, DSC automatically generates a read-only account for the data asset. You cannot use the account to perform de-identification tasks.
- Username and password-based authorization allows you to authorize DSC to access a data asset by entering the username and password that are used to access the data asset. After you authorize DSC to access a data asset, DSC can detect, de-identify, and audit the sensitive data in the data asset. You can de-identify the detected sensitive data based on your business requirements.
|Type of data asset||One-click authorization||Username and password-based authorization|
|ApsaraDB RDS for SQL Server||Supported||Supported|
|ApsaraDB RDS for PostgreSQL||Supported||Supported|
|ApsaraDB RDS for PPAS||Supported||Supported|
|ApsaraDB RDS for MariaDB TX||Supported||Supported|
|Distributed Relational Database Service (DRDS)||Supported||Supported|
|AnalyticDB for MySQL||Not supported||Supported|
|AnalyticDB for PostgreSQL||Not supported||Supported|
|Object Storage Service (OSS)||Supported||Supported|
|PolarDB for MySQL||Not supported||Supported|
|PolarDB for PostgreSQL||Not supported||Supported|
|Self-managed MySQL databases hosted on Elastic Compute Service (ECS) instances||Not supported||Supported|
|ApsaraDB OceanBase for MySQL||Not supported||Supported|
|ApsaraDB OceanBase for Oracle||Not supported||Supported|
|ApsaraDB for MongoDB||Not supported||Supported|