Configure a Database Audit instance

更新时间:
复制 MD 格式

After you purchase and enable a Database Audit instance, you can manage it in the Database Audit console. This topic describes how to configure a whitelist, manage storage capacity, upgrade specifications, and renew your instance.

Prerequisites

You have enabled a Database Audit instance. For more information, see Enable a Database Audit instance.

Procedure

  1. Log on to the Alibaba Cloud Security DBAudit console.

  2. In the navigation pane on the left, click C100 Instances.

  3. On the C100 Instances page, view information about your enabled Database Audit instances and configure them.

    You can perform the following actions on a Database Audit instance:

    • Configure a network whitelist

      To enable access from the public network, turn on the public network access switch for the instance. This switch is Off by default. After you enable public network access, click Configure Whitelist to specify which IP addresses can access the instance over the public network.

      Warning

      If you modify other configurations while enabling or disabling public network access, auditing may fail.

    • Upgrade instance specifications

      In the Edition section, click Upgrade. On the Modify Specifications page, select your desired edition and log storage capacity. Then, select the Database Audit Service Agreement checkbox, click Buy Now, and complete the payment.

    • Manage storage space

      The Storage Information section shows the percentage of the total storage capacity used by audit logs and session logs. When you purchase a Database Audit instance, it includes a specific amount of complimentary storage capacity. For example, a Professional Edition 3 instance comes with 500 GB. If you need more storage space, you can click Increase Capacity in the Storage Information section to purchase additional log storage space.

      Warning

      When your storage space is full, new audit logs and session logs cannot be written to Log Service. You cannot view new audit logs, session logs, or the detailed data of alert logs that are generated based on statistical rules. Increase your log storage capacity promptly after you receive a storage threshold alert.

      Database Audit supports clearing storage space, adjusting the retention period, and backing up logs to OSS. Click Configure in the Storage Information section to perform the following actions as needed:

      • Clear storage space

        Warning

        After you clear the storage space, you can no longer query the cleared data. Perform this action with caution.

        This action frees up used storage space. To delete all log data stored in the Database Audit instance, including audit logs and session logs, click Clear next to Used Storage.

      • Adjust the retention period

        Warning

        Use caution when you modify the retention period. If data is stored longer than the specified period, it is automatically deleted.

        The default retention period is 185 days. Base the retention period on industry regulations, such as MLPS requirements, as well as your business needs, security requirements, and storage costs. The supported retention period ranges from 30 to 185 days. To change it, click Modify next to Retention Period. The change takes effect immediately.

      • Back up log data to OSS

        OSS allows you to set custom lifecycle rules for long-term data storage. If you need long-term storage for audit logs and session logs, you can click OSS Backup. This takes you to the Log Service console, where you can create a shipping task to send your logs to OSS. For more information, see Create an OSS shipping task (old version).

    • Renew a Database Audit instance

      In the Expiration Time section, click Renew. On the Renew page, select your desired subscription duration, select the Database Audit Service Agreement checkbox, and then click Buy Now and complete the payment.

      Important

      After a Database Audit instance expires, auditing stops for the associated databases. The instance is released 7 days after its expiration. To avoid service disruption, renew your instance before it expires.