To provide higher-quality database audit services, Alibaba Cloud no longer supports the purchase of new DataBase Audit A100 instances. To purchase a DataBase Audit instance, you must purchase a C100 or D100 instance. If you are using an A100 instance, this topic introduces the A100 product and its billing methods, and provides a quick start guide and links to the user guide and FAQ.
If you still need to purchase a new DataBase Audit A100 instance, join the DingTalk group (ID: 44519396) and contact a product technical expert. You can still renew and upgrade existing A100 instances in the DataBase Audit console. For more information, see Manage DataBase Audit instances.
For information about how to purchase a DataBase Audit C100 or D100 instance, see Purchase a DataBase Audit instance (New purchases discontinued).
Product introduction
The DataBase Audit A100 instance is a professional, proactive, and real-time audit product that monitors database security. The A100 instance uses an effective database audit method to record and generate alerts for risky database activities, such as database vulnerability attacks, SQL injection, and risky operations. You can use the system monitoring engine to customize audit policies, such as rules that define sensitive data and statements to exclude from audits. The A100 instance effectively assesses potential database risks and monitors the access behavior of database users in real time.
Supported database types
Database classification | Database | Version |
Alibaba Cloud cloud-native databases | RDS for MySQL | 5.5, 5.6, 5.7, 8.0 |
PolarDB for MySQL | All versions | |
PolarDB for PostgreSQL | All versions | |
PolarDB for Oracle | All versions | |
PolarDB-X (formerly DRDS) | All versions | |
RDS for SQL Server | 2008 R2, 2012, 2016, 2017 | |
RDS for PostgreSQL | All versions | |
RDS for MariaDB | All versions | |
OceanBase MySQL mode | All versions | |
OceanBase Oracle mode | All versions | |
AnalyticDB for MySQL | All versions | |
AnalyticDB for PostgreSQL | All versions | |
MongoDB Important Only Premium Enhanced Edition 10 instances support this database type. | 3.x | |
Self-managed databases | Oracle | 8i, 9i, 10g, 11g, 12c |
MySQL | 4.0, 4.1, 5.0 to 5.7, 8.0 | |
SQL Server | 2000, 2005, 2008, 2012, 2014, 2016, 2017 | |
Sybase | 12, 15 | |
DB2 | 8.0, 8.1, 8.2, 9.1, 9.5, 9.7, 10.1 | |
SAP HANA | 1.0, 2.0 | |
Shentong Database (Oscar) | All versions | |
Dameng (DM) | All versions | |
PostgreSQL | All versions | |
MongoDB Important Only Premium Enhanced Edition 10 instances support this database type. | 3.x | |
KingBase | All versions | |
GBase | 8, 8T | |
Percona | All versions | |
MariaDB | All versions |
Supported associated applications
Application | Supported versions |
Tomcat | Tomcat 5.5, 6.0, 7.0, 8.0 Note For Tomcat 5.5, JRE 1.6 or later must be installed. |
JBoss | JBoss 4, 5 Note For JBoss 4, JRE 1.6 or later must be installed. |
WebLogic | WebLogic 10, 11 |
WebSphere | WebSphere 6.1, 7, 8 Note For WebSphere 6.1, JDK 1.6 or later must be installed. |
Billing methods
A100 is available in four editions: Professional, Premium, Premium Enhanced, and Enterprise. The following table compares the performance and price of each edition.
Edition | Performance metrics | Number of databases | Price |
Professional Edition |
Note Can typically store three years of audit data. | Supports auditing 3 database instances |
|
Premium Edition |
Note Can typically store three years of audit data. | Supports auditing 5 database instances |
|
Premium Enhanced Edition |
Note Can typically store three years of audit data. | Supports auditing 10 database instances |
|
Enterprise Edition |
| Supports auditing 25 database instances |
|
Select the DataBase Audit edition based on the number of database instances you need. A database instance is metered by Database IP + Database port number.
If a single database IP address has multiple database ports, the number of database instances required is equal to the number of ports. One database IP address and one database port count as one database instance. One database IP address and N database ports count as N database instances.
For example, a user has two database assets: IP 1 and IP 2. IP 1 provides services through one database port, which counts as one database instance. IP 2 provides services through three database ports, which counts as three database instances. In total, four database instances are required. You must select a DataBase Audit edition that supports four or more database instances. In this case, select the Premium Edition, which supports five database instances.
Quick start
After you purchase a DataBase Audit A100 instance, you can log on to the DataBase Audit system to add your database. Then, you can deploy the Agent on your database server to enable the audit service for your database. The following flow shows how to use a DataBase Audit A100 instance:
Task | Description |
After you purchase the DataBase Audit instance, you must enable it before you can log on to the DataBase Audit system and use the audit service. | |
After you enable the DataBase Audit instance, you can adjust its security group and access control policies for public and internal networks. Note When you first use the service, keep the default settings. You can adjust them after you are familiar with the service. | |
After you log on to the DataBase Audit system, you can configure database access and query audit results. | |
Add information about the database instance you want to audit to the DataBase Audit system. | |
After you add the database instance in the DataBase Audit system, you must deploy the Agent on the database server. This allows the DataBase Audit service to collect and audit the access traffic of the database. | |
After you add the database instance and deploy the Agent, you can view the audited statements and statistics in the DataBase Audit system. |
User guide access
Feature module | User guide link |
Manage DataBase Audit instances | |
Manage databases | |
Audit query and alert configuration | |
FAQ access
What permissions can I grant to a RAM user for DataBase Audit?
Does deleting the Agent in CentOS mean deleting the /usr/local/rmagent directory?
Do I need to select the local loopback interface when I install the Agent?
Do I need to consider the database type when I select a DataBase Audit edition?
How do I configure the DataBase Audit service after I purchase it?
How do I verify that the DataBase Audit service is configured correctly?
Does the DataBase Audit service support viewing administrator operation logs?