This topic describes the release notes for the features, identification templates, and documentation of Data Security Center (DSC).
Features
March 2025
Feature | Category | Description | Release date | References |
Column encryption | Feature iteration |
| 2025.03.31 | |
Data auditing | Feature iteration | The architecture of custom audit alert rules is optimized. | 2025.03.26 | |
Column encryption | Feature iteration | Encryption algorithms are updated.
| 2025.03.19 |
February 2025
Feature | Category | Description | Release date | References |
Column encryption | Feature iteration | PostgreSQL 16 is supported. | 2025.02.28 |
January 2025
Feature | Category | Description | Release date | References |
Data auditing | Feature iteration | Sensitive features related to security event alerts are displayed based on the integration of data auditing and data identification capabilities. | 2025.01.15 |
2024
Feature | Category | Description | Release date | References |
Data detection and response | Feature iteration | The database leak detection feature is supported. The feature checks database information, such as endpoints, ports, and accounts, in authorized Object Storage Service (OSS) buckets. This helps identify whether database accounts and database instances are leaked. If leaks are detected, DSC tracks and generates alerts for access to the database instances that use the leaked database accounts or the database accounts in self-managed intelligence and threat intelligence. | 2024.12.11 | |
Column encryption | Feature iteration | The column encryption feature is supported for PolarDB for MySQL. | 2024.12.04 | |
Asset authorization | Feature iteration | DSC can be authorized to access the data assets in Simple Log Service (SLS). | 2024.11.05 | |
Sensitive data identification | Feature iteration | Data assets in Simple Log Service (SLS) can be scanned to identify sensitive data. | 2024.11.05 | |
Column encryption | Feature iteration | The feature is billed based on value-added features. | 2024.10.30 | |
Data detection and response: OSS scenarios (AccessKey pair leaks) | Feature iteration | Access traceability graphs are provided to allow you to view access paths to Object Storage Service (OSS) objects in a visualized manner and analyze the complex data access relationships in OSS. This helps you monitor and analyze the access behavior of OSS objects. | 2024.09.24 | |
Column encryption | New | The column encryption feature is provided to encrypt identified sensitive data columns in tables of ApsaraDB RDS databases. This prevents unauthorized personnel from accessing plaintext sensitive column data by using cloud platform software or database connection tools. Data in databases is available but invisible. | 2024.09.20 | |
Multi-account management | Feature iteration | Member management by level is supported. A delegated administrator account can use RAM users to manage members by level based on the resource directory path of a folder in a resource directory. | 2024.09.12 | |
Data auditing and audit alerting | Feature iteration | The DSC console is optimized to merge the configurations of auditing modes and audit alert rules | 2024.09.09 | |
Log management | Feature iteration | The DSC console is optimized to manage log analysis and log storage under log management. | 2024.09.09 | |
System settings | New |
| 2024.08.30 | |
DSC Free Edition | New feature | DSC Free Edition is officially released, which provides baseline check and data classification capabilities. | 2024.08.21 | |
System settings | New feature |
| 2024.07.31 | |
Data security posture | Feature iteration | Audit rules can be configured to report audit alerts. | 2024.07.31 | |
Data auditing | New feature |
| 2024.07.31 | |
Data detection and response | New feature | The feature is provided to check the AccessKey pairs of Alibaba Cloud accounts or Resource Access Management (RAM) users in the source code on GitHub and in authorized Object Storage Service (OSS) buckets. This helps identify whether AccessKey pairs are leaked. If AccessKey pair leaks are detected, DSC tracks risk access to buckets and objects by using leaked AccessKey pairs or AccessKey pairs in self-managed intelligence and generates alerts for the AccessKey pairs. | 2024.07.31 | |
Supported regions | Feature iteration | China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Hangzhou), China (Shanghai), China (Shenzhen), and China (Chengdu) are supported. | 2024.07.11 | |
Multi-account management | New feature | Cloud-native data assets of different accounts can be aggregated and managed in a centralized manner by using the resource directory. | 2024.04.30 | |
Sensitive data identification | Feature iteration | The supported identification features, identification models, and identification templates are updated to match the support status at the China site (aliyun.com). | 2024.04.29 | |
Sensitive data identification | Feature iteration | New identification rules are added to identify sensitive data such as Hong Kong Special Administrative Region (HKSAR) passport ID, number of Exit-Entry Permit for Traveling to Hong Kong (China) and Macao (China), Alipay nickname, Alipay account number, policy number, Mybank ID, Sesame ID, and Sesame points. | 2024.04.29 |
2023
Feature | Category | Description | Release date | References |
Sensitive data identification | Feature iteration | The tagging feature is added to display common sensitive information tags, such as personal information and sensitive personal information, based on the classification results of industry-specific templates. | 2023.03.10 |
2022
Feature | Category | Description | Release date | References |
Asset center | Feature iteration |
| 2022.11.01 |
2021
Feature | Category | Description | Release date | References |
Watermark extraction | Feature iteration | The watermark feature is launched. You can add hidden watermarks to databases. If data leaks occur, you can use DSC to trace the source. | 2021.05.11 | |
Sensitive data identification | Feature iteration | Sensitive data identification for ApsaraDB RDS for PPAS and ApsaraDB RDS for MariaDB is supported | 2021.01.19 | |
Sensitive data identification | Feature iteration | Capabilities to identify sensitive information, such as Linux-Passwd files, Linux-Shadow files, URL links, and names (English), are added. | 2021.01.13 | |
Asset authorization | Feature iteration | Automatic authorization is supported after you import multiple passwords at a time. | 2021.01.05 |
2020
Feature | Category | Description | Release date | References |
Data masking | Feature iteration | Data masking for ApsaraDB RDS for PostgreSQL is supported. | 2020.12.17 | |
Sensitive data identification | Feature iteration | Sensitive data identification for AnalyticDB for MySQL and AnalyticDB for PostgreSQL is supported. | 2020.12.15 | |
Data masking | Feature iteration | Data masking for PolarDB for Xscale (PolarDB-X) is supported. | 2020.12.15 | |
Data masking | Feature iteration | The data masking source and destination can be the same database. | 2020.11.25 | |
Data masking | Feature iteration |
| 2020.11.18 | |
Sensitive data identification | Feature iteration | Sensitive data identification and data auditing for ApsaraDB RDS for PostgreSQL are supported. | 2020.11.18 | |
Sensitive data identification | Feature iteration | Sensitive data identification rules can be configured to match sensitive information based on database field names and regular expressions. | 2020.10.28 | |
Sensitive data identification | Feature iteration | Sensitive data identification and data auditing for ApsaraDB for OceanBase are supported. | 2020.09.08 | |
Sensitive data identification | Feature iteration | The optical character recognition (OCR) technology is supported to identify sensitive information in images. | 2020.07.16 | |
Data masking | Feature iteration | Data masking for OSS objects is supported. | 2020.01.20 | |
Sensitive data identification | Feature iteration | Sensitive data identification for self-managed databases is supported. | ||
Data masking | Feature iteration | Data identification, data auditing, and data masking for PolarDB and PolarDB for Xscale are supported. | 2020.01.18 | |
Sensitive data identification | Feature iteration |
2019
Feature | Category | Description | Release date | References |
Data masking | Feature iteration | The data masking feature is improved.
| 2019.12.26 | |
Sensitive data identification | Feature iteration | The asset status and sensitive data identification results can be displayed in a list and exported. | 2019.11.21 | |
Purchase | Feature iteration | The pay-as-you-go billing method is supported. Specific billing units are changed. | 2019.10.17 | |
SDDP | Feature iteration | SDDP is available for commercial use. | 2019.07.04 | |
Data masking | New feature | The static data masking feature is released. | 2019.06.27 |
2018
Feature | Category | Description | Release date | References |
SDDP | New feature | The public preview of SDDP is released. | 2018.09.01 |
Identification templates
DSC provides identification templates to help identify sensitive data. Custom identification templates can be configured to classify sensitive data based on the requirements of different industries. DSC can identify sensitive data based on the identification template that you specify. This ensures data security compliance. For more information about the built-in identification templates provided by DSC, see Supported industry-specific classification templates.
2024
Template name | New record | Release date |
Common identification template | Six identification features and five identification models are added. | 2024.07 |
Data classification template for the financial industry | One identification feature is added. One identification model is updated. | 2024.06 |
Data classification template for the Internet industry | One identification feature is added. One identification model is updated. | |
Common identification template | One identification feature and one identification model are added. | 2024.05 |
Data classification template for the financial industry | Five identification features and five identification models are added. | |
Common identification template | Six identification features and six identification models are added. | 2024.04 |
Data classification template for the financial industry | Six identification features and three identification models are added. | |
Common identification template | Seventeen identification features and sixteen identification models are added. | 2024.03 |
Data classification template for the financial industry | Thirteen identification features and six identification models are added. | |
Common identification template | Four identification features and four identification models are added. | 2024.02 |
Common identification template | Four identification features and four identification models are added. | 2024.01 |
2023
Template name | New record | Release date |
Common identification template | Nine identification features and five identification models are added. | 2023.12 |
Common identification template | Thirty-five identification features and 21 identification models are added. | 2023.11 |
Data classification template for the Internet of Vehicles (IoV) industry | Twenty-three identification features and 23 identification models are added. | |
Data classification template for the Internet industry | Two identification features and two identification models are added. | |
Common identification template | Eight identification features and six identification models are added. | 2023.10 |
Common identification template | One hundred and twenty-four identification models are added. | Before October 2023 |
Data classification template for the IoV industry | One hundred and thirty-five identification models are added. | |
Data classification template for the electricity industry | Sixty-four identification models are added. | |
Data classification template for the Internet industry | Fifty-four identification models are added. | |
Data classification template for the financial industry | Three hundred and thirty-one identification models are added. |