tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary
DocumentationTencentDB for MySQLPractical TutorialCybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL

Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL

PDF
Focus Mode
Font Size
Last updated: 2025-10-27 18:03:19
To assist enterprises in achieving cybersecurity classified protection compliance, this document describes the relationship between the database audit capabilities of TencentDB for MySQL and the related clauses of cybersecurity classified protection, to help enterprises provide targeted supporting materials.

Prerequisites

Database audit service has been enabled.

Level 3 Cybersecurity Classified Protection

(a) The database audit feature should be enabled, auditing each user and covering important user behaviors and significant security events.
This clause primarily examines the following three points:
Whether the database audit feature is enabled
1.1 Log in to the MySQL console, and choose Database Audit in the left sidebar. If Enabled is displayed under the Audit Storage Status field, it indicates that the database audit feature is enabled for instances in the specified region under the current account.

1.2 Click View Audit Logs to redirect to the Audit Log page of the corresponding instance, where you can see audit log records (audit log records should have been generated), proving the database audit feature is running normally.

Whether the audit scope covers all users
On the Audit Log page, the corresponding user account for an operation can be queried under the User Account field, supporting auditing every username.

Whether important user behaviors and significant security events are audited
By configuring post-event alarms, users can receive risk alarms based on the set audit rules and risk levels, helping them quickly locate issues and view relevant audit logs on the Audit Log page.

(b) Audit records should include the date and time of the event, user account, SQL type, SQL command details, and other information related to the audit.
On the Audit Log page, you can filter by time and search criteria to locate target audit logs. Click the download icon to download related audit logs to the local system and query the information.

(c) Audit records shall be protected to prevent unexpected deletion, modification, or overwriting.
After the database audit feature is enabled, the button for deleting audit logs is not displayed, preventing users from accidentally deleting or modifying the audit logs. Audit records will only be cleared when the database audit feature is disabled.
(d) Others: According to the Cybersecurity Law, network logs should be retained for 6 months or more.
On the Audit Log page, select a time range of six months in the time box to view the logs for the selected 6 months.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback