Database Autonomy Service (DAS) provides the security audit feature to automatically identify risks, such as high-risk SQL statements, SQL injection attacks, and new request sources. This topic describes how to perform security audit in the SQL Explorer and Audit module.
Prerequisites
- The database instance that you want to manage is connected to DAS and is in the Accessed state.
- DAS Professional Edition is enabled for the database instance. For more information, see Purchase DAS Professional Edition.
- The security audit feature is available for the following types of databases:
- ApsaraDB RDS for MySQL High-availability Edition and Enterprise Edition
- PolarDB for MySQL Single Node Edition, Archive Database Edition, and Cluster Edition
- The security audit feature is available in the following regions: China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Guangzhou), China (Heyuan), China (Ulanqab), China (Hong Kong), Singapore (Singapore), Malaysia (Kuala Lumpur), and Indonesia (Jakarta).
Storage duration
Audit data generated in real time by using the security audit feature can be stored for up to 30 days.