Feature | Description |
Access control | PolarDB provides multiple permission control and access control methods, such as IP address whitelists, security groups, and SQL firewalls, to ensure security. For more information about the access control for PolarDB for MySQL, see Configure a whitelist. |
Data security | PolarDB provides the Transparent Data Encryption (TDE) feature to encrypt and decrypt data files in real time. Data is encrypted before it is written to a disk and is decrypted when it is read from a disk to the memory. For more information about TDE for PolarDB for MySQL, see Configure TDE. |
Data transmission encryption | PolarDB provides the Secure Sockets Layer (SSL) feature to improve data transmission security. SSL is used to encrypt network connections at the transport layer. This improves the security and integrity of the data that is transmitted. For more information about SSL for PolarDB for MySQL, see Configure SSL encryption. |
Mask sensitive data | PolarDB for MySQL supports Dynamic data masking. If you want to authorize third parties to generate reports, analyze data, perform development and test activities, or perform other database-related operations, you may need to obtain the latest customer data from databases in the production environment in real time. To avoid disclosing personal information, data must be masked before it is provided to third parties. PolarDB uses PolarProxy to provide the dynamic data masking feature for masking sensitive data. When your application initiates a data query request, PolarDB masks the sensitive data that is queried before PolarDB returns the data to the application. To achieve this, you need to specify the database account, the database name, and the table or column that requires data masking before the data is queried. This way, you can obtain the real-time data that is masked by using the dynamic data masking feature. This ensures secure data access. |
Always-confidential | PolarDB provides the always-confidential feature, which can prevent database or application services from accessing user data in plaintext. This prevents data and account leakage on the cloud, and prevents R&D and O&M personnel from stealing the data. For more information about the always-confidential feature for PolarDB for MySQL, see Overview. |
Security audit | PolarDB provides the SQL Explorer and Audit feature. The feature is developed based on the full request feature and the security audit feature. The feature is also integrated with the following features: search, SQL Explorer, security audit, and traffic playback and stress test. The feature helps you obtain information about the SQL statements that are executed. You can use the information to troubleshoot various performance issues, identify the sources of high risks, and check whether you need to upgrade your PolarDB cluster. For more information, see SQL Insight and Stress Testing (New Version). For more information about security audit for PolarDB for MySQL, see SQL Explorer and Audit. |
Elastic Compute Service (ECS)
Container Compute Service (ACS)
