Data encryption and access control can significantly reduce security risks. However, it is still necessary to record the actions of users with privileges to prevent login information leaks or the abuse of access permissions. The audit feature strengthens an enterprise's ability to meet data security and compliance requirements, and is the primary tool for tracking user activities.
Audit overview
In OceanBase AI Database, the database audit feature audits specific events by using a series of filters. Filters can screen events based on dimensions such as account, event type, and event attributes, and determine whether to audit the filtered events. After configuring filters, you must apply them to users for the filters to take effect. The relationship between filters and users is one-to-many: one filter can be applied to multiple users, but each user can have only one filter. You can also set a default filter, which applies to all users who do not have a filter specified.
You can specify the types of requests to be audited by using filters, such as login/logout requests, DML statements, and CMD statements. The requests are recorded in audit files on the local disk or in object storage, and the records are rotated, cleaned, and compressed according to specified policies.
Audit procedure
The audit procedure consists of the following steps: enabling security audit, setting and viewing audit rules, viewing audit records, and disabling security audit. When enabling security audit, you need to specify the audit scope and note the usage restrictions, and then create and configure filters for data filtering. Setting and viewing audit rules involves specifying the log policy, format, data masking, output path, archiving, cleaning, and compression. Audit records can be viewed through logs. When disabling security audit, you must clear the filter configurations and delete the filters.